From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/4] clk: shmobile: add CPG driver for rz-platforms
Date: Wed, 05 Mar 2014 14:59:37 +0100 [thread overview]
Message-ID: <1460103.hdWs652aMT@avalon> (raw)
In-Reply-To: <20140305135431.GA7985@katana>
Hi Wolfram,
On Wednesday 05 March 2014 14:54:32 Wolfram Sang wrote:
> > > > While the parent is indeed selected at boot time only, and only one
> > > > parent is thus needed, parent selection could be performed by a DIP
> > > > switch connected to MD_CLK on the board for instance. In that case
> > > > both parents should be available in DT, as selection will be done by
> > > > the kernel at boot time, not at DT compile time.
> > >
> > > OK, I understand the case. I still wonder about specifying two parents,
> > > though. If a board uses USB_X1, it then has to spefify a dummy EXTAL
> > > clock (or an empty one), just because USB_X1 is enumerated as second
> > > entry?
> >
> > That's a good question. Mike, would it be possible to support "holes" in
> > the DT clocks lists, like the GPIO DT bindings do ?
>
> I talked to Magnus and we decided to start with hardcoded EXTAL for now,
> and leave USB_X1 support for in incremental patch when this is actually
> needed.
That's fine with me (although given the low complexity I would probably have
gone directly to supporting both clocks) as long as we can ensure both forward
and backward compatibility. Should we give a name to the clock input through
the clock-names property for that reason ?
> Note that the devkit will most likely be the only board ever with a
> selectable root clock.
Most probably, but that's no reason not to support it :-)
--
Regards,
Laurent Pinchart
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140305/c3a5fc7e/attachment.sig>
next prev parent reply other threads:[~2014-03-05 13:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-28 21:09 [PATCH 0/4] CCF support for Renesas r7s72100 Wolfram Sang
2014-02-28 21:09 ` [PATCH 1/4] ARM: r7s72100: add clock nodes to dtsi Wolfram Sang
2014-02-28 21:09 ` [PATCH 2/4] ARM: r7s72100: genmai: populate extal clock node Wolfram Sang
2014-02-28 21:09 ` [PATCH 3/4] clk: shmobile: add CPG driver for rz-platforms Wolfram Sang
2014-03-02 22:15 ` Laurent Pinchart
2014-03-03 9:19 ` Wolfram Sang
2014-03-03 10:59 ` Laurent Pinchart
2014-03-03 16:27 ` Wolfram Sang
2014-03-04 11:02 ` Laurent Pinchart
2014-03-04 11:07 ` Wolfram Sang
2014-03-04 11:13 ` Laurent Pinchart
2014-03-04 11:56 ` Wolfram Sang
2014-03-05 13:54 ` Wolfram Sang
2014-03-05 13:59 ` Laurent Pinchart [this message]
2014-03-05 15:07 ` Wolfram Sang
2014-02-28 21:09 ` [PATCH 4/4] ARM: shmobile: r7s72100: use workaround for non DT-clocks Wolfram Sang
2014-03-02 22:21 ` Laurent Pinchart
2014-03-03 9:22 ` Wolfram Sang
2014-03-03 11:00 ` Laurent Pinchart
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=1460103.hdWs652aMT@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).