From: Phil Elwell <phil@raspberrypi.org>
To: Stefan Wahren <stefan.wahren@i2se.com>,
linux-clk@vger.kernel.org, Eric Anholt <eric@anholt.net>,
linux-kernel@vger.kernel.org,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Florian Fainelli <f.fainelli@gmail.com>,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] clk: bcm2835: Limit PCM clock to OSC and PLLD_PER
Date: Wed, 31 May 2017 09:28:31 +0100 [thread overview]
Message-ID: <56d5f9c5-ba15-4d3e-7956-fb697fe12114@raspberrypi.org> (raw)
In-Reply-To: <684006892.45085.1496169665454@email.1und1.de>
Hi Stefan,
On 30/05/2017 19:41, Stefan Wahren wrote:
> Hi Phil,
>
>> Phil Elwell <phil@raspberrypi.org> hat am 30. Mai 2017 um 18:28 geschrieben:
>>
>>
>> Restrict clock sources for the PCM peripheral to the oscillator and
>> PLLD_PER because other source may have varying rates or be switched off.
>
>> Prevent other sources from being selected by replacing their names in
>> the list of potential parents with dummy entries (entry index is
>> significant).
>
> i like to have this as a comment above the definition of bcm2835_pcm_per_parents.
Sure - good idea.
>>
>> Signed-off-by: Phil Elwell <phil@raspberrypi.org>
>> ---
>> drivers/clk/bcm/clk-bcm2835.c | 11 +++++++++++
>> 1 file changed, 11 insertions(+)
>>
>> diff --git a/drivers/clk/bcm/clk-bcm2835.c b/drivers/clk/bcm/clk-bcm2835.c
>> index 0258538..facc346 100644
>> --- a/drivers/clk/bcm/clk-bcm2835.c
>> +++ b/drivers/clk/bcm/clk-bcm2835.c
>> @@ -1511,6 +1511,16 @@ struct bcm2835_clk_desc {
>> "pllh_aux",
>> };
>>
>> +static const char *const bcm2835_pcm_per_parents[] = {
>
> As mentioned above, there should be a comment like all the others.
Yes, will do.
>> + "-",
>> + "xosc",
>> + "-",
>> + "-",
>> + "-",
>> + "-",
>> + "plld_per",
>> +};
>
> Is there a dummy entry for "pllh_aux" missing?
Yes and no - adding it will cause an extra iteration around the loop, but
perhaps it's less confusing. I'll add one.
>> +
>> #define REGISTER_PER_CLK(...) REGISTER_CLK( \
>> .num_mux_parents = ARRAY_SIZE(bcm2835_clock_per_parents), \
>> .parents = bcm2835_clock_per_parents, \
>> @@ -2000,6 +2010,7 @@ struct bcm2835_clk_desc {
>> .int_bits = 12,
>> .frac_bits = 12,
>> .is_mash_clock = true,
>> + .parents = bcm2835_pcm_per_parents,
>
> This looks a little bit hacky to me. Not sure, but can we do something like this?
>
> #define REGISTER_PCM_CLK(...) REGISTER_CLK( \
> .num_mux_parents = ARRAY_SIZE(bcm2835_pcm_per_parents), \
> .parents = bcm2835_pcm_per_parents, \
> __VA_ARGS__)
Of course - no problem.
Thanks for the feedback - it will be incorporated into V2.
Phil
next prev parent reply other threads:[~2017-05-31 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 16:28 Phil Elwell
2017-05-30 18:41 ` Stefan Wahren
2017-05-31 8:28 ` Phil Elwell [this message]
2017-05-31 8:59 ` Stefan Wahren
2017-05-31 9:18 ` [PATCH v2 " Phil Elwell
2017-06-01 13:41 ` kbuild test robot
2017-05-31 21:24 ` [PATCH " Eric Anholt
2017-06-01 8:46 ` Phil Elwell
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=56d5f9c5-ba15-4d3e-7956-fb697fe12114@raspberrypi.org \
--to=phil@raspberrypi.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=stefan.wahren@i2se.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
all inboxes | Powered by JetHome®