[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <521F9F2F.1060307@wwwdotorg.org>
Date: Thu, 29 Aug 2013 13:21:19 -0600
From: Stephen Warren <swarren@...dotorg.org>
To: George Cherian <george.cherian@...com>
CC: balbi@...com, myungjoo.ham@...sung.com, cw00.choi@...sung.com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org, grant.likely@...aro.org,
rob@...dley.net, ian.campbell@...rix.com, mark.rutland@....com,
pawel.moll@....com, rob.herring@...xeda.com,
linux-omap@...r.kernel.org, linux-usb@...r.kernel.org,
bcousson@...libre.com, davidb@...eaurora.org, arnd@...db.de,
swarren@...dia.com, popcornmix@...il.com
Subject: Re: [PATCH v3 3/3] ARM: dts: dra7-evm: Add extcon nodes for USB ID
pin detection
On 08/28/2013 11:33 AM, George Cherian wrote:
> Add
> -extcon nodes for USB ID pin detection.
> -i2c nodes.
> -pcf nodes to which USB ID pin is connected.
> diff --git a/arch/arm/boot/dts/dra7-evm.dts b/arch/arm/boot/dts/dra7-evm.dts
> &dwc3_1 {
> - dr_mode = "otg";
> + dr_mode = "host";
> };
I wonder why one cares about ID/VBUS detection if the port doesn't
operate in OTG mode?
> &dwc3_2 {
> dr_mode = "host";
> };
> +
> +&usb1 {
> + extcon = <&extcon1>;
> +};
> +
> +&usb2 {
> + extcon = <&extcon2>;
> +};
I assume the "extcon" property is already fully documented in the
binding for the USB controller? For some reason, "extcon" looks like an
odd property name; I would have expected something more HW-oriented that
Linux-subsystem-oriented, such as "connector", or "usb-connector".
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists