Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Xu Yang <xu.yang_2@nxp.com>
To: Hui Wang <hui.wang@canonical.com>
Cc: linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev,
	devicetree@vger.kernel.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, festevam@gmail.com
Subject: Re: [PATCH] ARM: dts: nxp: imx6qdl: add dr_mode to usbotg
Date: Fri, 13 Dec 2024 20:55:28 +0800	[thread overview]
Message-ID: <20241213125528.m2skucuhqtrc5f4s@hippo> (raw)
In-Reply-To: <cb6c7f8d-6244-4370-944f-a1a2beac3a79@canonical.com>

On Fri, Dec 13, 2024 at 07:25:32PM +0800, Hui Wang wrote:
> 
> On 12/13/24 16:17, Xu Yang wrote:
> > Hi,
> > 
> > On Thu, Dec 12, 2024 at 12:31:26PM +0800, Hui Wang wrote:
> > > For the chipidea usb driver, if the dr_mode is not set, it will set
> > > the device to otg mode by default, so here the dr_mode has not been
> > > set for a long time. But some testcases need to parse the dr_mode from
> > > DT and decide the follow-up test strategy, here set the dr_mode to otg
> > > explicitly for QA's testcases.
> > The dr_mode is board specific property, so we normally don't put it in
> > dtsi file. Also, imx6qdl.dtsi is a common dtsi, therefore it's not a
> > correct place. I wonder you don't set dr_mode in other dts file which
> > include will imx6qdl.dtsi?
> 
> Yes, our QA reported this issue against the imx6q-sabresd board, I thought
> dr_mode could be overwritten if board dts set the dr_mode, so this change
> will not impact existing boards. But as you said "we normally don't put it
> in dtsi file", I will move it to imx6q-sabresd.dts.

Okay. You can move it to imx6qdl-sabresd.dtsi too. Then you can reuse
&usbotg {}.

Thanks,
Xu Yang

> 
> Thanks,
> 
> Hui.
> 
> > Thanks,
> > Xu Yang
> > 
> > > Signed-off-by: Hui Wang <hui.wang@canonical.com>
> > > ---
> > >   arch/arm/boot/dts/nxp/imx/imx6qdl.dtsi | 1 +
> > >   1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/arch/arm/boot/dts/nxp/imx/imx6qdl.dtsi b/arch/arm/boot/dts/nxp/imx/imx6qdl.dtsi
> > > index d2200c9db25a..285fb7314a88 100644
> > > --- a/arch/arm/boot/dts/nxp/imx/imx6qdl.dtsi
> > > +++ b/arch/arm/boot/dts/nxp/imx/imx6qdl.dtsi
> > > @@ -982,6 +982,7 @@ usbotg: usb@2184000 {
> > >   				clocks = <&clks IMX6QDL_CLK_USBOH3>;
> > >   				fsl,usbphy = <&usbphy1>;
> > >   				fsl,usbmisc = <&usbmisc 0>;
> > > +				dr_mode = "otg";
> > >   				ahb-burst-config = <0x0>;
> > >   				tx-burst-size-dword = <0x10>;
> > >   				rx-burst-size-dword = <0x10>;
> > > -- 
> > > 2.34.1
> > > 


  reply	other threads:[~2024-12-13 12:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12  4:31 [PATCH] ARM: dts: nxp: imx6qdl: add dr_mode to usbotg Hui Wang
2024-12-13  8:17 ` Xu Yang
2024-12-13 11:25   ` Hui Wang
2024-12-13 12:55     ` Xu Yang [this message]
2024-12-16  1:07       ` Hui Wang

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=20241213125528.m2skucuhqtrc5f4s@hippo \
    --to=xu.yang_2@nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=hui.wang@canonical.com \
    --cc=imx@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.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