devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yoshihiro Kaneko <ykaneko0929@gmail.com>,
	Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH/RFC] ARM: shmobile: r8a7790: Fix HSUSB clock to hp_clk from mp_clk
Date: Wed, 4 Mar 2015 16:02:59 +0900	[thread overview]
Message-ID: <20150304070258.GA16597@verge.net.au> (raw)
In-Reply-To: <CAMuHMdUHMA+cJTGWS-0Prt6-BT5=UkGQ4OWZ+bz-g2G7DSwLzw@mail.gmail.com>

Hi Geert,

On Mon, Feb 16, 2015 at 03:04:16PM +0100, Geert Uytterhoeven wrote:
> Hi Simon,
> 
> On Mon, Feb 16, 2015 at 2:57 PM, Simon Horman <horms@verge.net.au> wrote:
> > On Mon, Feb 16, 2015 at 10:20:10AM +0100, Geert Uytterhoeven wrote:
> >> Hi Kaneko-san, Mizuguchi-san,
> >>
> >> On Sun, Feb 15, 2015 at 3:49 PM, Yoshihiro Kaneko <ykaneko0929@gmail.com> wrote:
> >> > From: Kazuya Mizuguchi <kazuya.mizuguchi.ks@renesas.com>
> >> >
> >> > HSUSB uses hp_clk for H/W register access.
> >>
> >> That indeed seems to be true, and that's what this patch is changing.
> >>
> >> > HSUSB uses mp_clk for USB-DMAC access.
> >>
> >> However, page 64-2 doesn't mention the MP clock for USB-DMAC:
> >>    "AXI bus clock (ZSφ: 260 MHz), HPB bus clock (HPφ: 130 MHz).
> >>     USB local bus clock (48 MHz)"
> >> So your statement doesn't seem to be true?
> >
> > Thanks, I see that too.
> >
> >> Note that mstp3_clks in dtsi has hp_clk as the parent for both usbdmac0 and
> >> usbdmac1, so if your statement would be true, that has to changed, too?
> >>
> >> The same is true for other members of the R-Car Gen2 family, e.g. your patch
> >> for r8a7791.
> >
> > It seems to me that we could:
> >
> > 1. Apply this patch with the changelog updated and;
> > 2. Follow up on the DMAC clocks
> >
> > Does that sound reasonable to you?
> 
> Yes, that sounds fine to me.

The purpose of this email is to offer a quick status update which
I hope will bring this matter to a close.

I have submitted and queued up a patch as per 1. above.

With regards to item 2. above: I have also followed up on the "HSUSB uses
mp_clk for USB-DMAC access" comment in the original changelog (above).
Mizuguchi-san has confirmed that statement is not correct and its presence
in the changelog was an error.

      reply	other threads:[~2015-03-04  7:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 14:49 [PATCH/RFC] ARM: shmobile: r8a7790: Fix HSUSB clock to hp_clk from mp_clk Yoshihiro Kaneko
2015-02-15 15:36 ` Simon Horman
     [not found] ` <1424011746-3787-2-git-send-email-ykaneko0929-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-16  9:20   ` Geert Uytterhoeven
2015-02-16 13:57     ` Simon Horman
2015-02-16 14:04       ` Geert Uytterhoeven
2015-03-04  7:02         ` Simon Horman [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=20150304070258.GA16597@verge.net.au \
    --to=horms@verge.net.au \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=kazuya.mizuguchi.ks@renesas.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=ykaneko0929@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).