From: sboyd@kernel.org
To: unlisted-recipients:; (no To-header on input)
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: at91: add sama5d3 pmc driver
Date: Thu, 09 Jan 2020 16:11:23 -0800 [thread overview]
Message-ID: <20200110001124.8B82B20661@mail.kernel.org> (raw)
In-Reply-To: <20200109214128.GB1027187@piout.net>
From: Stephen Boyd <sboyd@kernel.org>
Quoting Alexandre Belloni (2020-01-09 13:41:28)
> On 09/01/2020 10:19:09-0800, Stephen Boyd wrote:
> > Quoting Alexandre Belloni (2020-01-08 03:02:18)
> > >
> > > As for the other PMC driver, we need a few of the peripheral clocks very
> > > early which means that we would have to register most of the clock tree
> > > registered early leaving only a few clocks to be registered by a
> > > platform driver.
> > >
> >
> > What peripheral clks? Can you add a comment to the code?
> >
>
> The TCB is used as the clocksource so its clock is needed. Its parent is
> the master clock which has UTMI, PLLA, the mainclock and the slow clock
> as parents so by that point, most of the tree is registered.
>
What in sama5d3_periphck[] is in that list? I still don't see why
platform device is rejected here.
next prev parent reply other threads:[~2020-01-10 0:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-29 20:29 [PATCH] clk: at91: add sama5d3 pmc driver Alexandre Belloni
2020-01-06 3:09 ` Stephen Boyd
2020-01-08 11:02 ` Alexandre Belloni
2020-01-09 18:19 ` Stephen Boyd
2020-01-09 21:41 ` Alexandre Belloni
2020-01-10 0:11 ` sboyd [this message]
2020-01-02 11:37 Karl Rudbæk Olsen
2020-01-04 0:46 ` Alexandre Belloni
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=20200110001124.8B82B20661@mail.kernel.org \
--to=sboyd@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nicolas.ferre@microchip.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).