- 02 Nov, 2017 12 commits
-
-
Chen-Yu Tsai authored
The WiFi side of the AP6212 WiFi/BT combo module is connected to mmc1. There are also GPIOs for enable and interrupts. An external clock from the AC100 RTC is also used. Enable WiFi on this board by enabling mmc1 and adding the power sequencing clocks and GPIO, as well as the chip's interrupt line. Signed-off-by:
Chen-Yu Tsai <wens@csie.org> Signed-off-by:
Maxime Ripard <maxime.ripard@free-electrons.com>
-
Chen-Yu Tsai authored
The WiFi side of the AP6330 WiFi/BT combo module is connected to mmc1. There are also GPIOs for enable and interrupts. An external clock from the AC100 RTC is also used. Enable WiFi on this board by enabling mmc1 and adding the power sequencing clocks and GPIO, as well as the chip's interrupt line. For the WiFi module to correctly detect the frequency of its main oscillator, the external low power clock must be set to 32768 Hz. Their does not seem to be proper out-of-band interrupt support for the BCM4330 chip within the AP6330 module. This part is left out for now. Signed-off-by:
-
Chen-Yu Tsai authored
mmc1 only has 1 possible pinmux setting. Move any settings to the dtsi file and set it by default. Signed-off-by:
-
Chen-Yu Tsai authored
This patch adds device nodes for all the regulators of the AXP818 PMIC. Sunxi common regulators are removed, and USB VBUS regulators are added. Signed-off-by:
-
Chen-Yu Tsai authored
This patch adds device nodes for all the regulators of the AXP813 PMIC. Sunxi common regulators are removed, and USB VBUS regulators are added. Signed-off-by:
-
Chen-Yu Tsai authored
This patch adds device nodes for all the regulators of the AXP818 PMIC. Sunxi common regulators are removed, and USB VBUS regulators are added. Signed-off-by:
-
Chen-Yu Tsai authored
The AXP81x family of PMIC is used with the Allwinner A83T and H8 SoCs. This includes the AXP813 and AXP818. There is no discernible difference except the labeling. The AXP813 is paired with the A83T, while the AXP818 is paired with the H8. This patch adds a dtsi file for all the common bindings for these two PMICs. Currently this is just listing all the regulator nodes. The regulators are initialized based on their device node names. In the future this would be expanded to include power supplies and GPIO controllers. Signed-off-by:
-
Corentin Labbe authored
The original dwmac-sun8i DT bindings have some issue on how to handle integrated PHY and was reverted in last RC of 4.13. But now we have a solution so we need to get back that was reverted. This patch restore arm64 DT about dwmac-sun8i for H5 This reverts a part of commit 87e1f5e8 ("arm64: dts: allwinner: Revert EMAC changes") Signed-off-by:
Corentin Labbe <clabbe.montjoie@gmail.com> Acked-by:
Florian Fainelli <f.fainelli@gmail.com> Signed-off-by:
-
Corentin Labbe authored
The original dwmac-sun8i DT bindings have some issue on how to handle integrated PHY and was reverted in last RC of 4.13. But now we have a solution so we need to get back that was reverted. This patch restore all boards DT about dwmac-sun8i This reverts partially commit fe45174b ("arm: dts: sunxi: Revert EMAC changes") Signed-off-by:
-
Corentin Labbe authored
Since dwmac-sun8i could use either an integrated PHY or an external PHY (which could be at same MDIO address), we need to represent this selection by a MDIO switch. Signed-off-by:
Andrew Lunn <andrew@lunn.ch> Signed-off-by:
-
Corentin Labbe authored
The original dwmac-sun8i DT bindings have some issue on how to handle integrated PHY and was reverted in last RC of 4.13. But now we have a solution so we need to get back that was reverted. This patch restore sunxi-h3-h5.dtsi This reverts partially commit fe45174b ("arm: dts: sunxi: Revert EMAC changes") Signed-off-by:
-
Corentin Labbe authored
This patch add documentation about the MDIO switch used on sun8i-h3-emac for integrated PHY. Signed-off-by:
Rob Herring <robh@kernel.org> Reviewed-by:
-
- 31 Oct, 2017 1 commit
-
-
Corentin Labbe authored
The original dwmac-sun8i DT bindings have some issue on how to handle integrated PHY and was reverted in last RC of 4.13. But now we have a solution so we need to get back that was reverted. This patch restore dt-bindings documentation about dwmac-sun8i This reverts commit 8aa33ec2 ("dt-bindings: net: Revert sun8i dwmac binding") Signed-off-by:
-
- 20 Oct, 2017 4 commits
-
-
Icenowy Zheng authored
Banana Pi M2 Ultra board features two USB host ports, connected to the two USB host ports on the SoC. Add support for them. Signed-off-by:
Icenowy Zheng <icenowy@aosc.xyz> Signed-off-by:
-
Icenowy Zheng authored
On the Banana Pi M2 Berry board, the 5V power output (used by HDMI, SATA and USB) is controlled via a GPIO. Add regulator node for it. Signed-off-by:
Icenowy Zheng <icenowy@aosc.io> Signed-off-by:
-
Icenowy Zheng authored
On newer revisions of the Banana Pi M2 Ultra boards, the 5V power output (used by HDMI, SATA and USB) is controller via a GPIO. Add the regulator node for it. Older revisions just have the 5V power output always on, and the GPIO is reserved on these boards. So it won't affect the older revisions. Signed-off-by:
-
Icenowy Zheng authored
Allwinner R40 SoC features a USB OTG port and two USB HOST ports. Add support for the host ports in the DTSI file. The OTG controller still cannot work with existing compatibles, and needs more investigation. So it's not added yet. Signed-off-by:
-
- 18 Oct, 2017 5 commits
-
-
Chen-Yu Tsai authored
Various A10-based development boards have standard HDMI connectors wired to the dedicated HDMI pins on the SoC. Enable the display pipeline and HDMI output on boards I have or have access to schematics: - Cubieboard - Olimex A10-OLinuXino-LIME Signed-off-by:
-
Chen-Yu Tsai authored
All the A20 devices I own have standard HDMI connectors wired to the dedicated HDMI pins on the SoC: - Bananapi M1+ - Cubieboard 2 - Cubietruck - Lamobo R1 (or Bananapi R1) Development boards from Olimex also have standard HDMI connectors. Schematics for them are publicly available. Enable HDMI on them as well. - Olimex A20-OLinuXino-LIME - Olimex A20-OLinuXino-LIME2 - Olimex A20-OLinuXino-MICRO Enable the display pipeline and HDMI output for them. Signed-off-by:
-
Jonathan Liu authored
The A20 has two interconnected display pipelines, mirroring the A10. Add all the device nodes for them, including the downstream HDMI controller that we already support. Signed-off-by:
Jonathan Liu <net147@gmail.com> [wens@csie.org: Squashed in HDMI and provided commit message] Signed-off-by:
-
Chen-Yu Tsai authored
The A10 has two interconnected display pipelines, much like the A31, but without the DRCs between the backend and TCONs. Add all the device nodes for them, including the downstream HDMI controller that we already support. Signed-off-by:
-
Icenowy Zheng authored
The R40 SoC has a watchdog like the one on A20, in the timer memory zone (which is also the same on A20). Add the device tree node for it. Signed-off-by:
-
- 13 Oct, 2017 6 commits
-
-
Chen-Yu Tsai authored
The reference design tablet has the DC jack wired to AXP209's ACIN. As a tablet, it also has an internal LiPo battery, wired to the PMIC's battery charger. Enable both. Signed-off-by:
-
Maxime Ripard authored
Some boards have had node names with underscores. Remove them in favour of hyphens in order to reduce the DTC warnings. Signed-off-by: -
Maxime Ripard authored
Some node names in the A80 DTSI still have underscores in them. Remove them in favour of hyphens to remove DTC warnings. Signed-off-by: -
Maxime Ripard authored
Some GPIO pinctrl nodes cannot be easily removed, because they would also change the pin configuration, for example to add a pull resistor or change the current delivered by the pin. Those nodes still have underscores and unit-addresses in their node names in our DTs, so adjust their name to remove the warnings. Use that occasion to also fix some poorly chosen node-names. Acked-by:
-
Maxime Ripard authored
The I2C's, MMC0 and EMAC controllers have only one muxing option in the SoC. In such a case, we can just move the muxing into the DTSI, and remove it from the DTS. Acked-by:
-
Maxime Ripard authored
All our pinctrl nodes were using a node name convention with a unit-address to differentiate the different muxing options. However, since those nodes didn't have a reg property, they were generating warnings in DTC. In order to accomodate for this, convert the old nodes to the syntax we've been using for the new SoCs, including removing the letter suffix of the node labels to the bank of those pins to make things more readable. Signed-off-by:
-
- 11 Oct, 2017 2 commits
-
-
Chen-Yu Tsai authored
All the A31/A31s devices I own have some kind of HDMI connector wired to the dedicated HDMI pins on the SoC: - A31 Hummingbird (standard HDMI connector, display already enabled) - Sinlinx SinA31s (standard HDMI connector) - MSI Primo81 tablet (micro HDMI connector) Enable the display pipeline (if needed) and HDMI output for them. Signed-off-by:
-
Chen-Yu Tsai authored
Now that we support the HDMI controller on the A31 SoC, we can add it to the device tree. This adds a device node for the HDMI controller, and the of_graph nodes connecting it to the 2 TCONs. Signed-off-by:
-
- 09 Oct, 2017 3 commits
-
-
Maxime Ripard authored
One of the usage of the LRADC is to implement buttons. The bindings define that we should have one subnode per button, with their associated voltage as a property. However, there was no reg property but we still used the voltage associated to the button as the unit-address, which eventually generated warnings in DTC. Rename the node names to avoid those warnings. Signed-off-by: -
Maxime Ripard authored
Using skeleton.dtsi will create a memory node that will generate a warning in DTC. However, that node will be created by the bootloader, so we can just remove it entirely in order to remove that warning. Acked-by:
-
Maxime Ripard authored
Some gpio-keys definitions in our DTs were having buttons defined with a unit-address and that would generate a DTC warning. Change the buttons node names to remove the warnings. Acked-by:
-
- 06 Oct, 2017 7 commits
-
-
Maxime Ripard authored
The board has an external pull-up on the card-detect signal, so there's no need to add another one. This also removes a DTC warning. Acked-by:
-
Maxime Ripard authored
The board has an external pull-up on the card-detect signal, so there's no need to add another one. This also removes a DTC warning. Acked-by:
-
Maxime Ripard authored
Our pinctrl node names were containing unit-adresses without a reg property, resulting in a warning. Change the names for our new convention. Acked-by:
-
Maxime Ripard authored
The A80 boards still define some GPIO pinctrl nodes that are not really useful, and redundant with the muxing already happening on gpio_request. Let's remove those nodes. This will also remove DTC warnings. Acked-by:
-
Maxime Ripard authored
Using skeleton.dtsi will create a memory node that will generate a warning in DTC. However, that node will be created by the bootloader, so we can just remove it entirely in order to remove that warning. Acked-by:
-
Maxime Ripard authored
The gpio pinctrl nodes are redundant and as such useless most of the times. Since they will also generate warnings in DTC, we can simply remove most of them. Acked-by:
-
Maxime Ripard authored
The thermal-zone subnodes we defined for the A10 have underscores in them that will generate DTC warnings. Change those underscores for hyphens. Acked-by:
-
