This is a note to let you know that I've just added the patch titled
ARM: dt: tegra trimslice: add vbus-gpio property
to the 3.5-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
arm-dt-tegra-trimslice-add-vbus-gpio-property.patch
and it can be found in the queue-3.5 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From 01ad8063a5db9ac8320f197577a34b423ba64eca Mon Sep 17 00:00:00 2001
From: Stephen Warren <[email protected]>
Date: Wed, 25 Jul 2012 14:02:44 -0600
Subject: ARM: dt: tegra trimslice: add vbus-gpio property
From: Stephen Warren <[email protected]>
commit 01ad8063a5db9ac8320f197577a34b423ba64eca upstream.
On TrimSlice, Tegra's USB1 port may be routed to either an external micro
USB port, or an internal USB->SATA bridge for SSD or HDD. This muxing is
controlled by a GPIO. Whilst not strictly a VBUS GPIO, the TrimSlice
board files caused this GPIO to be set appropriately to enable the SATA
bridge by passing it as the VBUS GPIO to the USB driver. Echo this same
configuration in device tree to enable the SATA bridge.
An alternative might be to implement a full USB bus mux driver. However,
that seems over-complex right now.
Signed-off-by: Stephen Warren <[email protected]>
Signed-off-by: Arnd Bergmann <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
arch/arm/boot/dts/tegra-trimslice.dts | 1 +
1 file changed, 1 insertion(+)
--- a/arch/arm/boot/dts/tegra-trimslice.dts
+++ b/arch/arm/boot/dts/tegra-trimslice.dts
@@ -276,6 +276,7 @@
usb@c5000000 {
status = "okay";
+ nvidia,vbus-gpio = <&gpio 170 0>; /* gpio PV2 */
};
usb@c5004000 {
Patches currently in stable-queue which might be from [email protected] are
queue-3.5/arm-dt-tegra-trimslice-enable-usb2-port.patch
queue-3.5/arm-dt-tegra-trimslice-add-vbus-gpio-property.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
