- Jan 25, 2016
-
-
Roger Shimizu authored
The GPIOs controlling the LEDs, listed below, are active high, not low: - gpio-leds: "lswxl:blue:power" pin - gpio-leds: "lswxl:red:func" pin - gpio-leds: "lswxl:red:hdderr{0,1}" pin Fixes: e54e4b1b ("ARM: dts: add buffalo linkstation ls-wxl/wsxl") Signed-off-by:Roger Shimizu <rogershimizu@gmail.com> Reviewed-by:
Andrew Lunn <andrew@lunn.ch> Signed-off-by:
Gregory CLEMENT <gregory.clement@free-electrons.com>
-
Roger Shimizu authored
For kirkwood, gpio pins starts from 32 are in the 2nd bank, so it should be converted to "gpio1 <pin minus 32>" in dts file. e.g. gpio 40 should be "gpio1 8" The pin/bank issue was found when discussing Debian Bug #810894 [https://bugs.debian.org/810894#47 ] Fixes: c43379e1 ("ARM: dts: add buffalo linkstation ls-wvl/vl") Reported-by:
Arnaud Patard (Rtp) <arnaud.patard@rtp-net.org> Signed-off-by:
-
Roger Shimizu authored
For kirkwood, gpio pins starts from 32 are in the 2nd bank, so it should be converted to "gpio1 <pin minus 32>" in dts file. e.g. gpio 40 should be "gpio1 8" Besides, a few other pin fixes for ls-wxl/wsxl, to match with mpp pin definition: - gpio-leds: "lswxl:blue:power" pin - gpio-leds: "lswxl:red:func" pin - gpio-leds: "lswxl:red:hdderr0" pin - gpio-leds: "lswxl:red:hdderr1" pin - gpio-fan: low/high/alarm pin The pin/bank issue was found when discussing Debian Bug #810894 [https://bugs.debian.org/810894#47 ] Fixes: e54e4b1b ("ARM: dts: add buffalo linkstation ls-wxl/wsxl") Reported-by:
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
Geert Uytterhoeven <geert+renesas@glider.be> Acked-by:
Brian Norris <computersforpeace@gmail.com> Signed-off-by:
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
-
- Jan 18, 2016
-
-
Geert Uytterhoeven authored
On r8a7740/armadillo, actual clock rates are ca. 4% lower than reported by /sys/kernel/debug/clk/clk_summary. Correct the extal1 frequency from 25 MHz to 24 MHz to fix this. This matches the Armadillo-800 EVA Product Manual, which claims the main crystal runs at 24 MHz, and the old legacy/reference board code. Fixes: 25aa7ba3 ("ARM: shmobile: armadillo800eva: Sync DTS") Signed-off-by:
Simon Horman <horms+renesas@verge.net.au>
-
- Jan 11, 2016
-
-
Stanimir Varbanov authored
Enable PCIe DT node and fill PCIe DT node with regulator, pinctrl and reset GPIO, to use the PCIe on the ifc6410 board. Signed-off-by:
Stanimir Varbanov <stanimir.varbanov@linaro.org> Signed-off-by:
Bjorn Helgaas <bhelgaas@google.com>
-
Stanimir Varbanov authored
Add the PCIe DT node so that it can probe and be used. Signed-off-by:
-
- Jan 08, 2016
-
-
Linus Walleij authored
The device tree version of Versatile AP/PB never had LED support so we are missing LEDs from our hardware boards. Add this as syscon LEDs like we did for Integrator and Juno. We need to spawn devices in the syscon with "simple-mfd" for this to work. Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
Arnd Bergmann <arnd@arndb.de>
-
- Jan 07, 2016
-
-
Roman Volkov authored
According to datasheet, the registers space of SDHC controller is 1Kb, not '0x1000', the correct value should be '0x400'. Bracket interrupt numbers individually per recommendations. Signed-off-by:
Roman Volkov <rvolkov@v1ros.org> Signed-off-by:
-
Roman Volkov authored
Since WM8650 has the same 'WMT' SDHC controller as WM8505, and the driver is already in the kernel, this node enables the controller support for WM8650 Signed-off-by:
Alexey Charkov <alchark@gmail.com> Cc: stable@vger.kernel.org Signed-off-by:
-
Linus Walleij authored
Commit 0976c946 "arm/versatile: Fix versatile irq specifications" has an off-by-one error on the Versatile AB that has been regressing the Versatile AB hardware for some time. However it seems like the interrupt assignments have never been correct and I have now adjusted them according to the specification. The masks for the valid interrupts made it impossible to assign the right SIC interrupt for the MMCI, so I went in and fixed these to correspond to the specifications, and added references if anyone wants to double-check. Due to the Versatile PB including the Versatile AB as a base DTS file, we need to override and correct some values to correspond to the actual changes in the hardware. For the Versatile PB I don't think the IRQ line assignment for MMCI has ever been correct for either of the two MMCI blocks. It would be nice if someone with the physical PB board could test this. Patch tested on the Versatile AB, QEMU for Versatile AB and QEMU for Versatile PB. Cc: Rob Herring <robh@kernel.org> Cc: Grant Likely <grant.likely@linaro.org> Cc: stable@vger.kernel.org Fixes: 0976c946 ("arm/versatile: Fix versatile irq specifications") Signed-off-by:
Olof Johansson <olof@lixom.net>
-
Linus Walleij authored
The Nomadik has sporadic crashes because of these latencies, setting them to max makes the platform work nicely, so use this values for now. These latencies were set to 2 since the Nomadik platform was merged, but I suspect they never took effect until the right size and associativity for the cache was specified in the device tree and that is why the crash comes now. Cc: stable@vger.kernel.org Signed-off-by:
-
Shawn Guo authored
The pinctrl group ipu2grp is a leftover from the previous iomuxc DT cleanup. It's not used by anyone now. More importantly, it's getting in the way of saving the unnecessary pinfunc container node from the board dts files that include imx6q.dtsi. Let's clean it up. Signed-off-by:
Shawn Guo <shawnguo@kernel.org> Tested-by:
Michael Trimarchi <michael@amarulasolutions.com> Signed-off-by:
-
- Jan 06, 2016
-
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
-
Geert Uytterhoeven authored
As of commit e488ca9f ("doc: dt: mtd: partitions: add compatible property to "partitions" node"), the "partitions" subnode of an SPI FLASH device node must have a compatible property. The partitions are no longer detected if it is not present. Signed-off-by:
-
- Jan 04, 2016
-
-
Carlo Caione authored
With this patch we add the watchdog node in the meson8b DTS file. Signed-off-by:Carlo Caione <carlo@endlessm.com>
-
Edward Cragg authored
Add the blue status LED to the Hardkernel Odroid C1 board DTS. Signed-off-by:
<edward.cragg@codethink.co.uk> Signed-off-by:
-
- Dec 31, 2015
-
-
Masahiro Yamada authored
Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Signed-off-by:
-
Eric Anholt authored
These will be used for enabling UART1, SPI1, and SPI2. Signed-off-by:
Eric Anholt <eric@anholt.net> Signed-off-by:
-
Eric Anholt authored
The Pi 2 B ends up like a Pi 1 B+, with the same peripherals and pinout, but the CPU and memory layout changed to use the 2836. Signed-off-by:
-
Eric Anholt authored
For Raspberry Pi 2, we want to use the same general pin assignment bits, but need to use bcm2836.dtsi for the CPU instead. Signed-off-by:
-
Eric Anholt authored
The set of peripherals remained constant across bcm2835 (Raspberry Pi 1) and bcm2836 (Raspberry Pi 2), but the CPU was swapped out. Split the files so that we can include just peripheral setup in 2836. Signed-off-by:
-
Linus Walleij authored
The L2 cache comes up in a "safe mode" on the PB11MPCore, as it has several issues. This sets it up properly with the right size and associativity, also requiring the outer sync to be disabled for the machine to boot properly. Cc: Russell King <linux@arm.linux.org.uk> Cc: Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
- Dec 29, 2015
-
-
Marek Szyprowski authored
G2D device is always available and doesn't depend on any external (board specific) peripherals, so it can be unconditionally enabled. Signed-off-by:
Marek Szyprowski <m.szyprowski@samsung.com> Signed-off-by:
Krzysztof Kozlowski <k.kozlowski@samsung.com>
-
Marek Szyprowski authored
G2D device and it's SYSMMU belongs to LCD0 power domain on Exynos 4210, so add missing power-domains property to G2D device node (G2D's SYSMMU is already bound to LCD0 power domain). Signed-off-by:
-
Marek Szyprowski authored
On Exynos 4210 MDMA1 device belongs to LCD0 power domain, so add proper power-domains property. On Exynos 4x12, it belongs to TOP power domain, which is always enabled, thus require no assignment in exynos4x12.dtsi. Signed-off-by:
-
Javier Martinez Canillas authored
The <dt-bindings/gpio/gpio.h> header is already included in the exynos4412-odroid-common DTSI so there's no need to do it again in the DTS file. Signed-off-by:
Javier Martinez Canillas <javier@osg.samsung.com> Signed-off-by:
-
Marek Szyprowski authored
PDMA for UART devices seems not to be working properly on Exynos 4210 revision 0 used in Universal C210 boards, so disable it to let one to use UART devices (driver defaults to PIO mode if DMA is not present). Signed-off-by:
-
Marek Szyprowski authored
DWC3 device found on Exynos SoCs cannot work in OTG mode alone, because it lacks some OTG related control part. OTG mode operation is possible only with external hardware logic (usually GPIO-based) specific to the board. Right now, however, there is no driver for such logic and no bindings, so the OTG mode is dysfunctional at all (this means that it doesn't work as a peripheral nor as a host). This patch sets the operation mode to peripheral to get DWC3_1 device at least somehow working. This can be later updated, when proper OTG driver and bindings get developed. Signed-off-by:
-
Marek Szyprowski authored
This patch adds device node for Rotator device and it's SYSMMU to Exynos 542x device tree file. Signed-off-by:
-
Marek Szyprowski authored
This patch adds device node for Rotator device to Exynos 5250 device tree file. Signed-off-by:
-
Marek Szyprowski authored
Rotator device and it's SYSMMU belongs to different power domains on various Exynos4 SoC revisions: LCD0 for 4210 and TOP for 4x12. This patch fixes this by moving power-domains property to exynos4210.dtsi. TOP power domain is always enabled and it is not represented in DTS. Signed-off-by:
-
Marek Szyprowski authored
This patch adds device node for Rotator device to Exynos 4210 and 4x12 device tree files. Signed-off-by:
-
Krzysztof Kozlowski authored
Enable Pseudo Random Number Generator (PRNG) on Trats2 board. This allows using hardware random number generator: $ echo exynos > /sys/class/misc/hw_random/rng_current Signed-off-by: -
Krzysztof Kozlowski authored
Add Pseudo Random Number Generator (PRNG) node of Security Sub System (SSS) to Exynos 4 DTSI. Signed-off-by:
-
