All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Simon Horman <horms@verge.net.au>,
	Magnus Damm <magnus.damm@gmail.com>,
	Linux-Renesas <linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH] arm64: dts: renesas: revise properties for usb 2.0
Date: Thu, 6 Sep 2018 10:43:08 +0000	[thread overview]
Message-ID: <OSBPR01MB2293ABF15F00E5B1029D1046D8010@OSBPR01MB2293.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <CAMuHMdVvscpSDX6X_j7c02RPV_6E8Df1Gz7Ci4Ssi46Pf5ehxA@mail.gmail.com>

Hi Geert-san,

> From: Geert Uytterhoeven, Sent: Thursday, September 6, 2018 7:19 PM
> 
> Hi Shimoda-san,
> 
> On Thu, Sep 6, 2018 at 12:09 PM Yoshihiro Shimoda
> <yoshihiro.shimoda.uh@renesas.com> wrote:
> > > From: Geert Uytterhoeven, Sent: Wednesday, September 5, 2018 9:59 PM
> > > On Fri, Aug 31, 2018 at 10:22 AM Yoshihiro Shimoda
> > > <yoshihiro.shimoda.uh@renesas.com> wrote:
> > > > R-Car Gen3 needs to enable/deassert clocks/resets of both usb 2.0
> > > > host (included phy) and peripheral. Otherwise, other side device
> > > > cannot work correctly. So, this patch revises properties of clocks
> > > > and resets. After that, each device driver can enable/deassert
> > > > clocks/resets by its self.
> > > >
> > > > Notes:
> > > >  - To work the renesas_usbhs driver correctly when host side drivers
> > > >    are disabled and the renesas_usbhs driver doesn't have multiple
> > > >    clock management, this patch doesn't change the order of the clocks
> > > >    property in each hsusb node.
> > > >  - This patch doesn't have any side-effects even if the renesas_usbhs
> > > >    driver doesn't have reset_control and multiple clock management.
> > > >
> > > > Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> > >
> > > Thanks for your patch!
> > >
> > > I'm a bit confused about the HS-USB <-> EHCI/OHCI topology.
> > > Can you please explain?
> > >
> > > Thanks!
> >
> > HS-USB <-> EHCI/OHCI topology on R-Car H3 is:
> >
> >  EHCI/OHCI ch0/3 ---+--- PHY (is included on the EHCI/OHCI) --- External pins
> >  HS-USB ch0/3    ---+
> >
> >  EHCI ch1/2      ------- PHY (is included on the EHCI/OHCI) --- External pins
> >  # These channels don't have HS-USB.
> 
> Thanks, that's the part is missed, and couldn't find immediately in the
> HW manual.

That's true...

> So HS-USB is the usb device ("gadget") part, and EHCI/OHCI is the
> usb host part?

That's right.

> >
> > And module stops and resets of HS-USB and EHCI/OHCI topology on R-Car H3 is:
> >
> >  MSTP/RST703 ---+(OR)---+--- EHCI/OHCI ch0
> >  MSTP/RST704 ---+       +--- HS-USB ch0
> >
> >  MSTP/RST702 --------------- EHCI/OHCI ch1
> >  MSTP/RST701 --------------- EHCI/OHCI ch2
> >
> >  MSTP/RST700 ---+(OR)---+--- EHCI/OHCI ch3
> >  MSTP/RST705 ---+       +--- HS-USB ch3
> >
> > Should I describe these topology on the commit log or somewhere?
> 
> Yes, I think that would be helpful.

I got it. I'll submit v2 patch tomorrow or later.

Best regards,
Yoshihiro Shimoda

> Thanks!
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds

      reply	other threads:[~2018-09-06 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-31  8:20 [PATCH] arm64: dts: renesas: revise properties for usb 2.0 Yoshihiro Shimoda
2018-09-05 10:33 ` Simon Horman
2018-09-20  5:55   ` Yoshihiro Shimoda
2018-09-21  7:37     ` Simon Horman
2018-09-21  7:58       ` Yoshihiro Shimoda
2018-09-05 12:59 ` Geert Uytterhoeven
2018-09-06 10:09   ` Yoshihiro Shimoda
2018-09-06 10:19     ` Geert Uytterhoeven
2018-09-06 10:43       ` Yoshihiro Shimoda [this message]

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=OSBPR01MB2293ABF15F00E5B1029D1046D8010@OSBPR01MB2293.jpnprd01.prod.outlook.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --cc=geert@linux-m68k.org \
    --cc=horms@verge.net.au \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.