All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 03/11] ARM: shmobile: r8a7778: Common clock framework DT description
Date: Mon, 26 Jan 2015 01:10:56 +0000	[thread overview]
Message-ID: <87fvaybb1j.wl%kuninori.morimoto.gx@renesas.com> (raw)
In-Reply-To: <1421857262-16607-4-git-send-email-ulrich.hecht+renesas@gmail.com>


Hi Geert

> >> > +                       clock-output-names > >> > +                               "i2c0", "i2c1", "i2c2", "i2c3", "scif0",
> >> > +                               "scif1", "scif2", "scif3", "scif4", "scif5",
> >> > +                               "tmu0", "tmu1", "tmu2", "ssi0", "ssi1",
> >> > +                               "ssi2", "ssi3", "sru", "hspi";
> >>
> >> On r8a7790, we use "ssi%u", on r8a7791, we use "ssi.%u"?
> > (snip)
> >> > +                       clock-output-names > >> > +                               "scu0", "scu1", "scu2", "scu3", "scu4",
> >> > +                               "scu5", "scu6", "scu7", "scu8";
> >>
> >> On r8a7790, we use "scu-src%u", on r8a7791, we use "src.%u"?
> >>
> >> Shall we use "sru-src%u" or "src.%u" here?
> >
> > I guess
> >  mstp  node is using "ssi%u"  / "scu-src%u"
> >  sound node is using "ssi.%u" / "src.%u"
> 
> Right, obviously I compared the wrong nodes. There are too many sound
> parameters in DTS ;-)
> 
> So on r8a7778 it should be ssi%u"  / "sru-src%u", right?

Thanks, I think so

Best regards
---
Kuninori Morimoto

      parent reply	other threads:[~2015-01-26  1:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 16:20 [PATCH 03/11] ARM: shmobile: r8a7778: Common clock framework DT description Ulrich Hecht
2015-01-22 10:58 ` Geert Uytterhoeven
2015-01-23  0:49 ` Kuninori Morimoto
2015-01-23  9:09 ` Geert Uytterhoeven
2015-01-26  1:10 ` Kuninori Morimoto [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=87fvaybb1j.wl%kuninori.morimoto.gx@renesas.com \
    --to=kuninori.morimoto.gx@renesas.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 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.