mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philippe Schenker <philippe.schenker@toradex.com>
To: "francesco@dolcini.it" <francesco@dolcini.it>,
	"alexander.stein@ew.tq-group.com"
	<alexander.stein@ew.tq-group.com>
Cc: "kernel@pengutronix.de" <kernel@pengutronix.de>,
	"linux-imx@nxp.com" <linux-imx@nxp.com>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"krzysztof.kozlowski+dt@linaro.org" 
	<krzysztof.kozlowski+dt@linaro.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>
Subject: Re: [PATCH] ARM: dts: colibri-imx6ull: Enable dual-role switching
Date: Mon, 7 Nov 2022 12:00:18 +0000	[thread overview]
Message-ID: <f901af9b264ee58233c3549f85ee876829fdd721.camel@toradex.com> (raw)
In-Reply-To: <Y2N2JYGvmzLjpGUq@francesco-nb.int.toradex.com>

On Thu, 2022-11-03 at 09:04 +0100, Francesco Dolcini wrote:
> On Thu, Nov 03, 2022 at 08:46:58AM +0100, Alexander Stein wrote:
> > Hi Philippe,
> > 
> > Am Mittwoch, 2. November 2022, 16:52:26 CET schrieb Philippe
> > Schenker:
> > > From: Philippe Schenker <philippe.schenker@toradex.com>
> > > 
> > > The Colibri standard provides a GPIO called USBC_DET to switch
> > > from
> > > USB Host to USB Device and back. The Colibri iMX6ULL does have the
> > > SoC
> > > ball USB_OTG1_VBUS connected in series with a capacitor to ground.
> > > 
> > > This means that we need to provide to the extcon framework VBUS
> > > and ID
> > > events using the single GPIO we have. The Extcon USB GPIO driver
> > > does
> > > use id-gpio also for VBUS event, as in our case where vbus-gpio is
> > > absent.
> > > 
> > > Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
> > > 
> > > ---
> > > 
> > >  arch/arm/boot/dts/imx6ull-colibri.dtsi | 8 ++++++++
> > >  1 file changed, 8 insertions(+)
> > > 
> > > diff --git a/arch/arm/boot/dts/imx6ull-colibri.dtsi
> > > b/arch/arm/boot/dts/imx6ull-colibri.dtsi index
> > > 577a424b0e1d..feb1fcd9a684
> > > 100644
> > > --- a/arch/arm/boot/dts/imx6ull-colibri.dtsi
> > > +++ b/arch/arm/boot/dts/imx6ull-colibri.dtsi
> > > @@ -24,6 +24,13 @@ backlight: backlight {
> > >                 status = "okay";
> > >         };
> > > 
> > > +       extcon_usbc_det: usbc-det {
> > > +               compatible = "linux,extcon-usb-gpio";
> > > +               id-gpio = <&gpio5 2 GPIO_ACTIVE_HIGH>; /* SODIMM
> > > 137 / 
> > USBC_DET */
> > > +               pinctrl-names = "default";
> > > +               pinctrl-0 = <&pinctrl_snvs_usbc_det>;
> > > +       };
> > > +
> > >         gpio-keys {
> > >                 compatible = "gpio-keys";
> > >                 pinctrl-names = "default";
> > > @@ -275,6 +282,7 @@ &uart5 {
> > >  /* Colibri USBC */
> > >  &usbotg1 {
> > >         dr_mode = "otg";
> > > +       extcon = <&extcon_usbc_det>, <&extcon_usbc_det>;
> > 
> > How came you up with this double entries? Is there some
> > documentation you need 
> > two phandles?
> 
> extcon-usb-gpio provides both vbus/otg_id with a single handle,
> however
> the integration in chipidea is somehow weird, the first entry is
> supposed to be
> used to read the vbus, the second one to read the otg_id.
> 
> So if you need to read both you really need to have the handle twice
> ...

Thanks for the suggestion Alex and Francesco for answering. I cannot add
much more, we tried a lot back and forth due to the really special
hardware-design this solution was the best we found for the colibri-
imx6ull.

Regards,
Philippe

> 
> Francesco
> 


  reply	other threads:[~2022-11-07 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 15:52 Philippe Schenker
2022-11-03  7:46 ` Alexander Stein
2022-11-03  8:04   ` Francesco Dolcini
2022-11-07 12:00     ` Philippe Schenker [this message]
2022-11-11  5:17     ` Shawn Guo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f901af9b264ee58233c3549f85ee876829fdd721.camel@toradex.com \
    --to=philippe.schenker@toradex.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=francesco@dolcini.it \
    --cc=kernel@pengutronix.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®