- 20 May, 2015 2 commits
-
-
git://git.infradead.org/users/hesselba/linux-berlinArnd Bergmann authored
Merge "Berlin DT changes for v4.2" from Sebastian Hesselbarth: - GPLv2/X11 dual licensing - Mark Berlin DT bindings as unstable - Updated binding documentation for reworked chip/system ctrl nodes * tag 'berlin-dt-4.2-1' of git://git.infradead.org/users/hesselba/linux-berlin: Documentation: bindings: update the berlin chip and system ctrl doc Documentation: bindings: move the Berlin clock documentation Documentation: bindings: move the Berlin pinctrl documentation Documentation: bindings: move the Berlin reset documentation Documentation: bindings: update the Berlin controllers documentation Documentation: bindings: berlin: consider our dt bindings as unstable ARM: dts: berlin: relicense the BG2CD Google Chromecast dts under GPLv2/X11 ARM: dts: berlin: relicense the berlin2cd dtsi under GPLv2/X11 ARM: dts: berlin: relicense the BG2 Sony NSZ-GS7 dts under GPLv2/X11 ARM: dts: berlin: relicense the berlin2 dtsi under GPLv2/X11 ARM: dts: berlin: relicense the BG2Q Marvell DMP dts under GPLv2/X11 ARM: dts: berlin: relicense the berlin2q dtsi under GPLv2/X11
-
Arnd Bergmann authored
Merge tag 'at91-dt2' of git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91 into next/dt Merge "Second batch of DT changes for 4.2:" from Nicolas Ferre: - sama5d4: more peripherals: usarts, uarts, spi, pioD access - sama5d3: phy address for gmac - change NFC register map - regulator additions for the sd/mmc * tag 'at91-dt2' of git://git.kernel.org/pub/scm/linux/kernel/git/nferre/linux-at91: ARM: at91/dt: sama5d4 xplained: add regulators for v(q)mmc1 supplies ARM: at91/dt: sama5d3 xplained: add fixed regulator for vmmc0 ARM: at91/dt: sama5d3 xplained: add mmc0 vqmmc entry ARM: at91/dt: sama5d3 xplained: fill in mmc1 and set it to disabled ARM: at91/dt: sama5: reduce the NFC command register map ARM: at91/dt: sama5d4: update pinctrl ranges ARM: at91/dt: sama5d3 xplained: add phy address for macb0 ARM: at91/dt: sama5d4 xplained: add spi1 on j14 connector ARM: at91/dt: sama5d4: add spi1, spi2 dt nodes ARM: at91/dt: sama5d4: add uart0, uart1 dt nodes ARM: at91/dt: sama5d4: add usart0, usart1 dt nodes
-
- 19 May, 2015 9 commits
-
-
Ludovic Desroches authored
Add vcc_mmc1 fixed regulator to remove the 'no vmmc regulator found' warning when probing the mmc1 device. Signed-off-by:
Ludovic Desroches <ludovic.desroches@atmel.com> Signed-off-by:
Nicolas Ferre <nicolas.ferre@atmel.com>
-
Ben Dooks authored
Add fixed regulator for vmmc0 and attach the vmmc for it to the mmc0 node on the SAM5D3 Xplained board. This will remove the following warning from the kernel: atmel_mci f0000000.mmc: No vmmc regulator found Note, atmel_defconfig will need fixed regulator support enabled if this is to be used properly. Signed-off-by:
Ben Dooks <ben.dooks@codethink.co.uk> [use a fixed regulator instead of gpio one] Signed-off-by:
-
Ben Dooks authored
The SAM5D3 Xplained device tree is missing the vqmmc node which is tied to 3.3V on the board. Add this to avoid the kernel warning that there is no vqmmc node. atmel_mci f0000000.mmc: No vqmmc regulator found Signed-off-by:
-
Ben Dooks authored
The mmc1 channel is not populated on the SAM5D3 Xplained board, however it is enabled and therefore the driver is attaching to it. The node configuration for mmc1 is missing, so add an mmc1 node in the device tree and set its status to disabled. Also add the vmmc and the necessary slot configuration if this node were enabled to avoid the following warnings from the driver: atmel_mci f8000000.mmc: No vmmc regulator found atmel_mci f8000000.mmc: No vqmmc regulator found Signed-off-by:
-
Josh Wu authored
commit 111573cc ("mtd: atmel_nand: check NFC busy flag by HSMC_SR instead of NFC cmd regs") check NFC busy by nfc SR instead of NFC cmd regs. So we don't need to map NFC cmd registers to include NFCBUSY bit. That means we only need map 0x08000000 instead of 0x10000000 for NFC cmd regs. This patch reduce the NFC cmd regs map for sama5d3 & sama5d4. Signed-off-by:
Josh Wu <josh.wu@atmel.com> Signed-off-by:
-
Ludovic Desroches authored
Update the pinctrl ranges property to support pioD controller whose mapping is not contiguous with other pio controllers. Without this update, getting resource will fail, then pinctrl probe will fail too because there is a missing pio controller. Signed-off-by:
-
Nicolas Ferre authored
Specify the phy address on macb0 node aka GEM. Signed-off-by: -
Nicolas Ferre authored
Route SPI1 on the Arduino "in the middle" spi connector. Signed-off-by: -
Suchang Ko authored
Add sama5d4 spi1, spi2 dt nodes & pinctrl. Signed-off-by:
Suchang Ko <suchangko@samul.kr> [nicolas.ferre@atmel.com: split patch, reorder & whitespace fixes] Signed-off-by:
-
- 15 May, 2015 23 commits
-
-
Antoine Tenart authored
Now that the rework to have one sub-node per device in the chip and system controllers is done, their dedicated compatible can be removed. Signed-off-by:
Antoine Tenart <antoine.tenart@free-electrons.com> Signed-off-by:
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
-
Antoine Tenart authored
The Berlin clock documentation was part of the Marvell Berlin SoC documentation because the Berlin clock configuration was inside the chip controller. With the recent rework of the chip and system controller handling (now all sub-devices of the soc and system controller nodes are registred with simple-mfd, and each device has its own sub-node), the documentation of the Berlin clock driver can be moved to the generic clock documentation directory. Signed-off-by:
Stephen Boyd <sboyd@codeaurora.org> Signed-off-by:
-
Antoine Tenart authored
The Berlin pinctrl documentation was part of the Marvell Berlin SoC documentation because the Berlin pinctrl configuration was inside the chip and the system controllers. With the recent rework of the chip and system controller handling (now an MFD driver registers all sub-devices of the two soc and system controller nodes and each device has its own sub-node), the documentation of the Berlin pinctrl driver can be moved to the generic pinctrl documentation directory. Signed-off-by:
-
Antoine Tenart authored
The Berlin reset documentation was part of the Marvell Berlin SoC documentation because the Berlin reset configuration was inside the chip controller. With the recent rework of the chip and system controller handling (now an MFD driver registers all sub-devices of the two soc and system controller nodes and each device has its own sub-node), the documentation of the Berlin reset driver can be moved to the generic reset documentation directory. Signed-off-by:
Philipp Zabel <p.zabel@pengutronix.de> Signed-off-by:
-
Antoine Tenart authored
We're moving from a single node for multiple devices to a node with one sub-node per sub-device, registered by simple-mfd. Update the documentation to reflect the changes. Signed-off-by:
-
Antoine Tenart authored
Because the support of Marvell Berlin SoCs is still a work in progress, add a statement to explicitly consider our device tree files and bindings as unstable. Signed-off-by:
-
Antoine Tenart authored
The current GPLv2 only licensing on this dts makes it very impractical for other software components licensed under another license. In order to make it easier for them to reuse our device trees, relicense this dts under a GPLv2/X11 dual-license. Signed-off-by:
-
Antoine Tenart authored
The current GPLv2 only licensing on this dtsi makes it very impractical for other software components licensed under another license. In order to make it easier for them to reuse our device trees, relicense this dtsi under a GPLv2/X11 dual-license. Signed-off-by:
Jisheng Zhang <jszhang@marvell.com> Signed-off-by:
-
Antoine Tenart authored
The current GPLv2 only licensing on this dts makes it very impractical for other software components licensed under another license. In order to make it easier for them to reuse our device trees, relicense this dts under a GPLv2/X11 dual-license. Signed-off-by:
-
Antoine Tenart authored
The current GPLv2 only licensing on this dtsi makes it very impractical for other software components licensed under another license. In order to make it easier for them to reuse our device trees, relicense this dtsi under a GPLv2/X11 dual-license. Signed-off-by:
-
Antoine Tenart authored
The current GPLv2 only licensing on this dts makes it very impractical for other software components licensed under another license. In order to make it easier for them to reuse our device trees, relicense this dts under a GPLv2/X11 dual-license. Signed-off-by:
-
Antoine Tenart authored
The current GPLv2 only licensing on this dtsi makes it very impractical for other software components licensed under another license. In order to make it easier for them to reuse our device trees, relicense this dtsi under a GPLv2/X11 dual-license. Signed-off-by:
Alexandre Belloni <alexandre.belloni@free-electrons.com> Signed-off-by:
-
Ariel D'Alessandro authored
Add basic support for Hitex LPC4350 Evaluation Board. Board features a LPC4350 Soc, 8 MB SDRAM, 8 MB SPI Flash, USB and Ethernet. More information can be found on: http://www.hitex.com/index.php?id=3212Signed-off-by:
Ariel D'Alessandro <ariel.dalessandro@gmail.com> Signed-off-by:
Joachim Eastwood <manabian@gmail.com> Signed-off-by:
Arnd Bergmann <arnd@arndb.de>
-
Joachim Eastwood authored
Adds basic support for Embedded Artists' LPC4357 Developer's Kit. Board features a LPC4357 Soc, 32 MB SDRAM, 128 MB NAND Flash, 16 MB SPI Flash, USB and Ethernet. More information can be found on: http://www.embeddedartists.com/products/kits/lpc4357_kit.phpSigned-off-by:
-
Joachim Eastwood authored
NXP LPC18xx/43xx SoCs are very similar devices and should be able to share a common base (lpc18xx.dtsi). Diffences between the devices are put in a dtsi which is specific to that device. Signed-off-by:
-
Maxime Coquelin authored
Tested-by:
Chanwoo Choi <cw00.choi@samsung.com> Signed-off-by:
Maxime Coquelin <mcoquelin.stm32@gmail.com> Signed-off-by:
-
git://git.infradead.org/linux-mvebuArnd Bergmann authored
Merge "mvebu dt changes for v4.2 (part #1)" from Gregory CLEMENT: - A series adding support for the Compulab CM-A510 - Add alias for mdio on Armada 38x * tag 'mvebu-dt-4.2' of git://git.infradead.org/linux-mvebu: ARM: mvebu: add alias for mdio on Armada 38x ARM: dts: dove: Add Compulab SBC-A510 to Makefile ARM: dts: dove: Add proper support for Compulab CM-A510/SBC-A510 ARM: dts: dove: Remove Compulab CM-A510 from Makefile ARM: dts: dove: Add internal i2c multiplexer node
-
Arnd Bergmann authored
Merge tag 'sti-dt-for-v4.2-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mcoquelin/sti into next/dt Merge "STi DT updates for v4.2, round 2." from Maxime Coquelin: Highlights: ----------- - Add USB3 support to STiH410 & STiH418 - Add PWM support to STiH416 & STiH407 family - Add restart support to STiH416 & STiH407 family - Add PMU support to STiH416 & STiH407 family - Reorder includes in STiH407 DT files * tag 'sti-dt-for-v4.2-2' of git://git.kernel.org/pub/scm/linux/kernel/git/mcoquelin/sti: ARM: STi: DT: STih407: Re-order #include <*.dtsi> files ARM: STi: Ensure requested STi's SysCfg Controlled IRQs are enabled at boot ARM: STi: STiH407: Enable PMU IRQs ARM: STi: STiH407: Enable Cortex-A9 PMU support ARM: STi: STiH416: Enable PMU IRQs ARM: STi: STiH416: Enable Cortex-A9 PMU support ARM: STi: STiH416: Add Restart support for STiH416 ARM: STi: STiH407: Add Restart support for STiH407 ARM: STi: STiH416-b2020e: Enable PWM on the B2020 Rev-E ARM: STi: STiH416: Add DT nodes for PWM ARM: STi: STiH416: Add Pinctrl settings for PWM ARM: STi: STiH407: Add DT nodes for for PWM ARM: DT: STi: STiH418: Enable USB3 port on stih418-b2199. ARM: DT: STi: STiH418: Add miphy28lp optional oscillator clock properties ARM: DT: STi: stihxxx-b2120: Enable USB3 port on stih407-b2120 and stih410-b2120 ARM: DT: STi: STiH407: Add dwc3 usb3 DT node. ARM: DT: STi: STiH407: Update picophyreset for the usb3 controllers usb2 phy
-
Arnd Bergmann authored
Merge tag 'rpi-dt-for-armsoc-v4.2' of git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi into next/dt Merge "RaspberryPi Device Tree changes due for v4.2" from Lee Jones: * tag 'rpi-dt-for-armsoc-v4.2' of git://git.kernel.org/pub/scm/linux/kernel/git/rpi/linux-rpi: ARM: bcm2835: dt: Use 0x4 prefix for DMA bus addresses to SDRAM. ARM: bcm2835: dt: Add the mailbox to the device tree ARM: bcm2835: dt: Fix i2c0 node name ARM: bcm2835: dt: Use pinctrl header ARM: bcm2835: dt: Add header file for pinctrl constants ARM: bcm2835: dt: Add root properties for Raspberry Pi ARM: bcm2835: dt: Add vendor prefix for Raspberry Pi
-
Linus Walleij authored
The Ux500 like other Cortex-A9 SoC's has a Snoop Control Unit (SCU) and a Watchdog in the same address range as the local timers. Add these to the SoC device tree. Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
-
Arnd Bergmann authored
Merge tag 'renesas-dt-for-v4.2' of git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas into next/dt Merge "Renesas ARM Based SoC DT Updates for v4.2" from Simon Horman: * Enable DMA for HSUSB on r8a7790 and r8a7791 SoCs * Configure the HOME key as wake-up source on kzm9g board * Use generic names for device nodes on SH Mobile SoCs and boards * Add "nor-jedec" compatible value to SH Mobile boards * Add IRQC clock to r8a73a4, r8a779* SoCs * Remove MSIOF address from r8a7790 and r8a7791 SoCs * tag 'renesas-dt-for-v4.2' of git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas: (31 commits) ARM: shmobile: r8a7791: Enable DMA for HSUSB ARM: shmobile: r8a7791: add USB-DMAC device nodes ARM: shmobile: r8a7790: Enable DMA for HSUSB ARM: shmobile: r8a7790: add USB-DMAC device nodes ARM: shmobile: kzm9g dts: Configure the HOME key as wake-up source ARM: shmobile: koelsch dts: Use generic names for device nodes ARM: shmobile: lager dts: Use generic names for device nodes ARM: shmobile: bockw dts: Use generic names for device nodes ARM: shmobile: koelsch dts: Add "nor-jedec" compatible value ARM: shmobile: bockw dts: Add "nor-jedec" compatible value ARM: shmobile: lager dts: Add "nor-jedec" compatible value ARM: shmobile: bockw-reference dts: Add "nor-jedec" compatible value ARM: shmobile: henninger dts: Add "nor-jedec" compatible value ARM: shmobile: armadillo800eva dts: Use generic names for device nodes ARM: shmobile: marzen dts: Use generic names for device nodes ARM: shmobile: kzm9d dts: Use generic names for device nodes ARM: shmobile: ape6evm dts: Use generic names for device nodes ARM: shmobile: sh73a0 dtsi: Use generic names for device nodes ARM: shmobile: r8a7791 dtsi: Use generic names for device nodes ARM: shmobile: r8a7790 dtsi: Use generic names for device nodes ...
-
https://github.com/rjarzmik/linuxArnd Bergmann authored
Merge "device-tree pxa update" from Robert Jarzmik: - clocks descriptions (pxa27x, pxa3xx) - timer descriptions (pxa27x, pxa3xx) - IPs which are embedded on the SoC - keypad - udc (USB client) - power I2C These are amongst the building blocks for future pxa device-tree board description. * tag 'pxa-dt-4.2' of https://github.com/rjarzmik/linux: ARM: dts: pxa: add pxa-timer to pxa27x and pxa3xx ARM: dts: pxa: add pxa27x-keypad to pxa27x ARM: dts: pxa: add pxa27x-udc to pxa27x ARM: dts: pxa: add clocks ARM: dts: pxa: add pwri2c to pxa device-tree
-
http://github.com/broadcom/stblinuxArnd Bergmann authored
Merge "Device Tree changes" from Florian Fainelli: New devices: - Felix adds support for the Buffalo WXR-1900DHP and adds the USB led on Buffalo WZR-1750DHP - Rafal adds support for the SmartRG SR400ac, Asus RT-AC68U and RT-AC56U New peripheral support: - Brian adds Device Tree nodes for the Broadcom NAND controller found on BCM7xxx, BCM63138 and Cygnus SoCs - Brian adds Device Tree nodes for the SATA AHCI and PHY controller found on BCM7xxx - I add the Device Tree nodes and bindings documents for bringing-up secondary CPUs and timer/syscon-reboot on BCM63138 * tag 'arm-soc/for-4.2/dts' of http://github.com/broadcom/stblinux: ARM: BCM5301X: Add DT for Asus RT-AC56U ARM: BCM5301X: Add DT for Asus RT-AC68U ARM: dts: BCM63xx: Add timer and syscon-reboot nodes dt-bindings: Add documentation for the BCM63138 timer and syscon-reboot ARM: dts: brcmstb: add nodes for SATA controller and PHY ARM: dts: cygnus: Enable NAND support for Cygnus ARM: bcm63138: add NAND DT support ARM: bcm7445: add NAND to DTS ARM: BCM5301X: Add DT for SmartRG SR400ac ARM: BCM5301X: Add DT for Buffalo WXR-1900DHP ARM: BCM5301X: Add USB LED for Buffalo WZR-1750DHP ARM: dts: BCM63xx: Add SMP nodes and required properties Documentation: DT: Document SMP DT nodes and properties for BCM63138 ARM: dts: BCM63xx: Add PMB busses nodes Documentation: DT: Add Broadcom BCM63138 PMB binding
-
- 14 May, 2015 6 commits
-
-
Lee Jones authored
This patch fixes a regression where serial is enabled by the first (board) DTSI, then disabled by the second (SoC) file. To enable serial and keep it enabled, we need to include the file which enables it last. Reported-by: LAVA [via Peter Griffin <peter.griffin@linaro.org>] Signed-off-by:
Lee Jones <lee.jones@linaro.org> Signed-off-by:
Maxime Coquelin <maxime.coquelin@st.com>
-
Eric Anholt authored
There exists a tiny MMU, configurable only by the VC (running the closed firmware), which maps from the ARM's physical addresses to bus addresses. These bus addresses determine the caching behavior in the VC's L1/L2 (note: separate from the ARM's L1/L2) according to the top 2 bits. The bits in the bus address mean: From the VideoCore processor: 0x0... L1 and L2 cache allocating and coherent 0x4... L1 non-allocating, but coherent. L2 allocating and coherent 0x8... L1 non-allocating, but coherent. L2 non-allocating, but coherent 0xc... SDRAM alias. Cache is bypassed. Not L1 or L2 allocating or coherent From the GPU peripherals (note: all peripherals bypass the L1 cache. The ARM will see this view once through the VC MMU): 0x0... Do not use 0x4... L1 non-allocating, and incoherent. L2 allocating and coherent. 0x8... L1 non-allocating, and incoherent. L2 non-allocating, but coherent 0xc... SDRAM alias. Cache is bypassed. Not L1 or L2 allocating or coherent The 2835 firmware always configures the MMU to turn ARM physical addresses with 0x0 top bits to 0x4, meaning present in L2 but incoherent with L1. However, any bus addresses we were generating in the kernel to be passed to a device had 0x0 bits. That would be a reserved (possibly totally incoherent) value if sent to a GPU peripheral like USB, or L1 allocating if sent to the VC (like a firmware property request). By setting dma-ranges, all of the devices below it get a dev->dma_pfn_offset, so that dma_alloc_coherent() and friends return addresses with 0x4 bits and avoid cache incoherency. This matches the behavior in the downstream 2708 kernel (see BUS_OFFSET in arch/arm/mach-bcm2708/include/mach/memory.h). Signed-off-by:
Eric Anholt <eric@anholt.net> Tested-by:
Noralf Trønnes <noralf@tronnes.org> Acked-by:
Stephen Warren <swarren@wwwdotorg.org> Signed-off-by:
-
Eric Anholt authored
Signed-off-by:
-
Baruch Siach authored
Device tree node names should contain the node's reg property address value. The i2c0 node was apparently forgotten in commit 25b2f1bd (ARM: bcm2835: node name unit address cleanup). Acked-by:
Baruch Siach <baruch@tkos.co.il> Signed-off-by:
-
Stefan Wahren authored
This patch converts all bcm2835 dts and dtsi files to use the pinctrl header file. Reviewed-by:
Stefan Wahren <stefan.wahren@i2se.com> Signed-off-by:
-
Stefan Wahren authored
This new header file defines pincontrol constants to use from bcm2835 DTS files for pincontrol properties option. Reviewed-by:
-
