SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 08/10] clk: shmobile: Add r8a7740, sh73a0 SoCs to MSTP bindings
Date: Tue, 09 Sep 2014 22:05:24 +0000	[thread overview]
Message-ID: <9161337.CEqz2KtdhV@avalon> (raw)
In-Reply-To: <1409649186-1046-9-git-send-email-ulrich.hecht+renesas@gmail.com>

On Wednesday 03 September 2014 09:41:05 Simon Horman wrote:
> On Tue, Sep 02, 2014 at 05:21:13PM -0700, Mike Turquette wrote:
> > Quoting Simon Horman (2014-09-02 16:56:04)
> > 
> > > On Tue, Sep 02, 2014 at 11:13:04AM +0200, Ulrich Hecht wrote:
> > > > Signed-off-by: Ulrich Hecht <ulrich.hecht+renesas@gmail.com>
> > > 
> > > Acked-by: Simon Horman <horms+renesas@verge.net.au>
> > > 
> > > Mike, could you consider picking this up?
> > 
> > I had a question about patch 9/10. My mailer seems to have messed up the
> > Cc list but it managed to hit the list[0].
> 
> Hi Mike,
> 
> Thanks, I agree there seem to be some outstanding questions
> regarding that patch. However, I believe although it is not
> clear from the arrangement of this patchset that this patch is entirely
> independent of 9/10 and can be considered separately.

Correct, there's no reason to delay this patch.

> > [0] http://lkml.kernel.org/r/<20140902224500.5251.83168@quantum>
> > 
> >>> ---
> >>> 
> >>>  Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt |
> >>>  2 ++
> >>>  1 file changed, 2 insertions(+)
> >>> 
> >>> diff --git
> >>> a/Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> >>> b/Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> >>> index 8a92b5f..8f1424f 100644
> >>> ---
> >>> a/Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> >>> +++
> >>> b/Documentation/devicetree/bindings/clock/renesas,cpg-mstp-clocks.txt
> >>> 
> >>> @@ -11,9 +11,11 @@ Required Properties:
> >>>    - compatible: Must be one of the following
> >>>      - "renesas,r7s72100-mstp-clocks" for R7S72100 (RZ) MSTP gate
> >>>      clocks
> >>> +    - "renesas,r8a7740-mstp-clocks" for R8A7740 (R-Mobile A1) MSTP
> >>> gate clocks
> >>>      - "renesas,r8a7779-mstp-clocks" for R8A7779 (R-Car H1) MSTP gate
> >>>      clocks
> >>>      - "renesas,r8a7790-mstp-clocks" for R8A7790 (R-Car H2) MSTP gate
> >>>      clocks
> >>>      - "renesas,r8a7791-mstp-clocks" for R8A7791 (R-Car M2) MSTP gate
> >>>      clocks
> >>> +    - "renesas,sh73a0-mstp-clocks" for SH73A0 (SH-MobileAG5) MSTP
> >>> gate clocks
> >>>      - "renesas,cpg-mstp-clock" for generic MSTP gate clocks
> >>>    
> >>>    - reg: Base address and length of the I/O mapped registers used by
> >>>    the MSTP
> >>>      clocks. The first register is the clock control register and is
> >>>      mandatory.

-- 
Regards,

Laurent Pinchart


  parent reply	other threads:[~2014-09-09 22:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02  9:13 [PATCH v2 08/10] clk: shmobile: Add r8a7740, sh73a0 SoCs to MSTP bindings Ulrich Hecht
2014-09-02 23:56 ` Simon Horman
2014-09-03  0:21 ` Mike Turquette
2014-09-03  0:41 ` Simon Horman
2014-09-09 22:05 ` Laurent Pinchart [this message]
2014-09-10  0:02 ` Simon Horman

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=9161337.CEqz2KtdhV@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-sh@vger.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