- 23 Oct, 2017 33 commits
-
-
Lucas Stach authored
This adds support for the Zodiac Inflight Innovations RDU1 board, which is based on the i.MX51. It is the predecessor of the already supported ZII RDU2 board and relies on the bootloader in the same way to enable correct display and touchscreen nodes. Signed-off-by:
Lucas Stach <l.stach@pengutronix.de> Tested-by:
Nikita Yushchenko <nikita.yoush@cogentembedded.com> Reviewed-by:
Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by:
Shawn Guo <shawnguo@kernel.org>
-
Lothar Waßmann authored
Create .dts files for various Ka-Ro electronics TX modules on the MB7 baseboard. Signed-off-by:
Lothar Waßmann <LW@KARO-electronics.de> Signed-off-by:
-
Lothar Waßmann authored
The TX6QP-8037 is a Computer On Module manufactured by Ka-Ro electronics GmbH with the following characteristics: Processor Freescale i.MX 6QuadPlus MCIMX6QP7, 1 GHz RAM 1GiB 64-bit DDR3 SDRAM ROM 4GB HiRel eMMC Power supply Single 3.3 to 5V Size 26mm SO-DIMM Temp. Range -40°C to 105°C Signed-off-by:
-
Lothar Waßmann authored
Move the MB7 specific settings to a separate .dtsi file to facilitate supporting more module variants with this baseboard. Signed-off-by:
-
Lothar Waßmann authored
Currently the display (LCD or LVDS) configuration is duplicated with slight variations in each TX6 module specific file. Move it to an include file for simplification and consistency. Signed-off-by:
-
Lothar Waßmann authored
Define the required properties to enable I2C bus recovery supported by the I2C subsystem. Signed-off-by:
-
Lothar Waßmann authored
Convert the DTS sound setup to use the simple-audio-card driver. Signed-off-by:
-
Lothar Waßmann authored
Under certain circumstances the ethernet PHY cannot be detected on Ka-Ro electronics TX6 modules. Using a phy-reset-post-delay of at least 2ms alleviates this problem. Define it to 10ms to be on the safe side. Signed-off-by:
-
Lothar Waßmann authored
Remove the PHY INT and RESET pins from hog section and put them into their own pinctrl nodes referenced by the appropriate driver nodes. Also, the MDIO pins are required for probing the Ethernet PHY, so they must be configured by the FEC driver, not by the PHY driver. Move the corresponding pinctrl settings from the PHY subnode to the FEC node. Signed-off-by:
-
Lothar Waßmann authored
As the DS1339 driver now supports enabling the trickle charge feature via DTB, add the appropriate properties to utilize this feature. Signed-off-by:
-
Lothar Waßmann authored
The 'ipu1' alias is already defined in imx6q.dtsi. There is no need to redefine it here. Signed-off-by:
-
Lothar Waßmann authored
The display, that incorporates this touchpanel is obsolete and won't be supported any more. Signed-off-by:
-
Lothar Waßmann authored
The current TX6Q module HW revision is 3 reflected in the module name suffix '-1030' (-1130 for LVDS). Change the model string to prevent confusion about what DTS file to use for these modules. Signed-off-by:
-
Fabio Estevam authored
The GPIO polarity is missing in the cd-gpios property. Fix it, so that the following build warnings are gone: DTC arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard.dtb arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard.dtb: Warning (gpios_property): cd-gpios property size (8) too small for cell size 2 in /soc/aips@53f00000/esdhc@53fb4000 DTC arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dtb arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-cmo-qvga.dtb: Warning (gpios_property): cd-gpios property size (8) too small for cell size 2 in /soc/aips@53f00000/esdhc@53fb4000 DTC arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-svga.dtb arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-svga.dtb: Warning (gpios_property): cd-gpios property size (8) too small for cell size 2 in /soc/aips@53f00000/esdhc@53fb4000 DTC arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-vga.dtb arch/arm/boot/dts/imx25-eukrea-mbimxsd25-baseboard-dvi-vga.dtb: Warning (gpios_property): cd-gpios property size (8) too small for cell size 2 in /soc/aips@53f00000/esdhc@53fb4000 Signed-off-by:
-
Fabio Estevam authored
Pass the '#dma-cells' property in the sdma node, so that the following build warning is gone: DTC arch/arm/boot/dts/imx50-evk.dtb arch/arm/boot/dts/imx50-evk.dtb: Warning (dmas_property): Missing property '#dma-cells' in node /soc/aips@60000000/sdma@63fb0000 or bad phandle (referred from /soc/aips@50000000/spba@50000000/ssi@50014000:dmas[0]) Signed-off-by:
-
Fabio Estevam authored
The GPIO polarity is missing in the cd-gpios property. Fix it, so that the following build warning is gone: DTC arch/arm/boot/dts/imx35-eukrea-mbimxsd35-baseboard.dtb arch/arm/boot/dts/imx35-eukrea-mbimxsd35-baseboard.dtb: Warning (gpios_property): cd-gpios property size (8) too small for cell size 2 in /soc/aips@53f00000/esdhc@53fb400 Signed-off-by:
-
Fabio Estevam authored
The correct property name is 'interrupt-parent', so fix it accordingly. This fixes the following build warning: arch/arm/boot/dts/imx6sx-softing-vining-2000.dtb: Warning (interrupts_property): interrupts size is (8), expected multiple of 12 in /soc/aips-bus@02100000/ethernet@02188000/mdio/ethernet0-phy@0 arch/arm/boot/dts/imx6sx-softing-vining-2000.dtb: Warning (interrupts_property): interrupts size is (8), expected multiple of 12 in /soc/aips-bus@02100000/ethernet@021b4000/mdio/ethernet1-phy@0 Cc: Christoph Fritz <chf.fritz@googlemail.com> Signed-off-by:
-
Fabio Estevam authored
The 'interrupts' property has an extra cell by mistake. Fix this, so that the following build warning is gone: DTC arch/arm/boot/dts/imx6ul-pico-hobbit.dtb arch/arm/boot/dts/imx6ul-pico-hobbit.dtb: Warning (interrupts_property): interrupts size is (12), expected multiple of 8 in /soc/aips-bus@2000000/ethernet@20b4000/mdio/ethernet-phy@1 Signed-off-by:
-
Fabio Estevam authored
The imx6qp variant also has sata, so add support for it. Reported-by:
Luís Mendes <luis.p.mendes@gmail.com> Signed-off-by:
-
Fabio Estevam authored
According to Documentation/devicetree/bindings/pci/fsl,imx6q-pcie.txt, the property for specifying the PCIe regulator is 'vpcie-supply', so use the correct one. Also fix the polarity of GPIO2_24 so that the regulator can operate correctly. Signed-off-by:
Christopher Spinrath <christopher.spinrath@rwth-aachen.de> Signed-off-by:
-
Fabio Estevam authored
Since commit c26ebe98 ("PCI: imx6: Add regulator support"), it is possible to pass the 'vpcie-supply' property to describe the PCIE supply. This way we can remove the 'regulator-always-on' property from the regulator and have a better device tree description. Signed-off-by:
Marek Vasut <marex@denx.de> Signed-off-by:
-
Leonard Crestez authored
This works identically to imx6sx-tempmon on both imx6ul and imx6ull. It just needs to be defined in dts. Signed-off-by:
Leonard Crestez <leonard.crestez@nxp.com> Signed-off-by:
-
Leonard Crestez authored
On imx6sx accessing OCOTP directly is wrong because the ocotp clock needs to be enabled first. Use the nvmem-cells binding instead. This requirement does not apply to older imx6qdl chips because there the ocotp access clock (clk_ipg_s) is always enabled. This is visible by comparing the "System Clocks, Gating, and Override" tables (OCOTP rows) in the 6DQ and 6SX manuals: http://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6SXRM.pdf http://www.nxp.com/assets/documents/data/en/reference-manuals/IMX6DQRM.pdf This happens to work right now because the ocotp clock might be enabled for some other reason. In particular the it might be enabled from the bootloader and it only gets disabled late during boot in clk_disable_unused, after imx-thermal has completed probing. If imx-thermal is compiled as a module then the system can hang on probe. Reported-by:
-
Tim Harvey authored
The container node in the iomuxc node is no longer necessary and causes pinctl errors on the Ventana boards with analog video capture since aa12693e: pinctrl core: initialized pinctrl subsystem imx6q-pinctrl 20e0000.iomuxc: no groups defined in /soc/aips-bus@02000000/iomuxc@020e0000/adv7180grp imx6q-pinctrl 20e0000.iomuxc: no groups defined in /soc/aips-bus@02000000/iomuxc@020e0000/ipu2_csi1grp imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver imx6q-pinctrl 20e0000.iomuxc: function 'iomuxc' not supported imx6q-pinctrl 20e0000.iomuxc: invalid function iomuxc in map table imx6q-pinctrl 20e0000.iomuxc: function 'iomuxc' not supported imx6q-pinctrl 20e0000.iomuxc: invalid function iomuxc in map table Signed-off-by:
Tim Harvey <tharvey@gateworks.com> Signed-off-by:
-
Fabio Estevam authored
Latest wandboard hardware revision is revd1, which brings the following new features: - PFUZE100 PMIC - AR8035 Ethernet PHY - Upgrade Wifi/BT chip to BCM4339/BCM43430. Add support for the mx6, mx6dl and mx6qp revd1 variants. Signed-off-by:
-
Philipp Zabel authored
By default, the lcdif_pre_sel mux is switched to the pll3_pfd1_540m PFD source. If this mux is allowed to propagate rate changes to its parent, setting the LCDIF pixel clock rate to 9 MHz, as required by the LCD panel, will cause the pll3_pfd1_540m PFD to be switched away from its nominal rate to 288 MHz. This has no negative side effects, as there are no other children to this PFD. Still, to avoid surprises, it might be preferrable to switch to the designated video PLL (pll5_video_div) as clock source for the LCDIF pixel clock. Signed-off-by:
Philipp Zabel <p.zabel@pengutronix.de> Reviewed-by:
-
Lothar Waßmann authored
The imx-i2c driver supports automatic bus recovery via the GPIO function of the I2C pins. Enable this functionality for the Ka-Ro electronics TX53 modules. Signed-off-by:
-
Lothar Waßmann authored
Don't rely on the padctl settings established by the boot loader, but explicitly specify the padctl values in DTB. This is also necessary to be able to use the DTB files from the Linux kernel for future U-Boot versions that support HW configuration via DTB. Signed-off-by:
-
Lothar Waßmann authored
As the DS1339 driver now supports enabling the trickle charge feature via DTB, add the appropriate properties to utilize this feature. Signed-off-by:
-
Lothar Waßmann authored
The display, that incorporates this touchpanel is obsolete and won't be supported any more. Signed-off-by:
-
Lothar Waßmann authored
It is not recommended to place the regulator nodes inside 'simple-bus', so adjust them accordingly. The motivation for rearranging this is to make it easier to add new regulator nodes in the future. Signed-off-by:
-
Lothar Waßmann authored
The current GPL only licensing on the dts files 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 our dts files first under a GPL/X11 dual-license. Signed-off-by:
-
Lothar Waßmann authored
As the DS1339 driver now supports enabling the trickle charge feature via DTB, add the appropriate properties to utilize this feature. Signed-off-by:
-
- 14 Oct, 2017 2 commits
-
-
Lothar Waßmann authored
It is not recommended to place the regulator nodes inside 'simple-bus', so adjust them accordingly. The motivation for rearranging this is to make it easier to add new regulator nodes in the future. Signed-off-by:
-
Lothar Waßmann authored
The current GPL only licensing on the dts file 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 our dts files first under a GPL/X11 dual-license. Signed-off-by:
-
- 13 Oct, 2017 5 commits
-
-
Marco Franchi authored
Contrary to later i.MX SoCs, the parallel display interface pad groups on i.MX51 are called DISP1 and DISP2 in the Reference Manual, not DISP0 and DISP1. Fix this inconsistence by changing the DISP names in the i.mx51 dts. Signed-off-by:
Marco Franchi <marco.franchi@nxp.com> Acked-by:
-
Marco Franchi authored
The following build warnings are seen with W=1: Warning (unit_address_vs_reg): Node /display@di0 has a unit name, but no reg property Warning (unit_address_vs_reg): Node /display@di1 has a unit name, but no reg property Fix all these warnings by changing 'display@diX' to 'dispX'. Signed-off-by:
-
Fabio Estevam authored
Add support for the built-in touchscreen controller present on MX25. Signed-off-by:
-
Marco Franchi authored
The following build warnings are seen with W=1: Warning (simple_bus_reg): Node /soc/sram@00900000 simple-bus unit address format error, expected "900000" Warning (simple_bus_reg): Node /soc/aips-bus@02000000 simple-bus unit address format error, expected "2000000" Warning (simple_bus_reg): Node /soc/aips-bus@02000000/pxp@020f0000 simple-bus unit address format error, expected "20f0000" (...) Remove the leading zeroes from unit addresses to fix the warnings. Signed-off-by:
-
Marco Franchi authored
The following build warnings are seen with W=1: Warning (unit_address_format): Node /interrupt-controller@00a01000 unit name should not have leading 0s Warning (simple_bus_reg): Node /soc/sram@00900000 simple-bus unit address format error, expected "900000" Warning (simple_bus_reg): Node /soc/dma-apbh@01804000 simple-bus unit address format error, expected "1804000" (...) Remove the leading zeroes from unit addresses to fix the warnings. Signed-off-by:
-
