From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Chanwoo Choi <cw00.choi@samsung.com>, linux-clk@vger.kernel.org
Cc: sboyd@codeaurora.org, mturquette@baylibre.com,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, b.zolnierkie@samsung.com,
m.szyprowski@samsung.com
Subject: Re: [PATCH 2/3] clk: exynos5433: Allow audio subsystem clock rate propagation
Date: Wed, 07 Feb 2018 16:18:32 +0100 [thread overview]
Message-ID: <3fcfad37-4c8f-7375-b2c2-5154607aa47a@samsung.com> (raw)
In-Reply-To: <5A7929C1.8040706@samsung.com>
Hi Chanwoo,
On 02/06/2018 05:06 AM, Chanwoo Choi wrote:
>> drivers/clk/samsung/clk-exynos5433.c | 22 +++++++++++-----------
>> 1 file changed, 11 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/clk/samsung/clk-exynos5433.c b/drivers/clk/samsung/clk-exynos5433.c
>> index 74b70ddab4d6..d74361736e64 100644
>> --- a/drivers/clk/samsung/clk-exynos5433.c
>> +++ b/drivers/clk/samsung/clk-exynos5433.c
>> @@ -246,14 +246,14 @@ static const struct samsung_fixed_rate_clock top_fixed_clks[] __initconst = {
>>
>> static const struct samsung_mux_clock top_mux_clks[] __initconst = {
>> /* MUX_SEL_TOP0 */
>> - MUX(CLK_MOUT_AUD_PLL, "mout_aud_pll", mout_aud_pll_p, MUX_SEL_TOP0,
>> - 4, 1),
>> + MUX_F(CLK_MOUT_AUD_PLL, "mout_aud_pll", mout_aud_pll_p, MUX_SEL_TOP0,
>> + 4, 1, CLK_SET_RATE_PARENT, 0),
>
> If you add CLK_SET_RATE_PARENT to 'mout_aud_pll' and mout_aud_pll changes the rate,
> fout_aud_pll's rate will be changed. But, fout_aud_pll is also the parent
> of 'mout_aud_pll_user'. It might change the rate of children of mout_aud_pll_user.
> mout_aud_pll_user would not want to change the parent's clock.
>
> fout_aud_pll 2 2 196608009 0 0
> mout_aud_pll_user 1 1 196608009 0 0
> mout_aud_pll 0 0 196608009 0 0
I'd say the range of changes is such that the consumers of the affected child
clocks can cope and could adjust to the changed frequencies. Those consumer
devices are all components/peripherals of the audio subsystem (LPASS) and,
for example, in case of TM2 there is no issues at all with varying the AUD PLL
frequency depending on the HDMI audio sample rate. The other audio path uses
the audio CODEC's internal PLL as the root clock source. The AUD PLL frequency
will need to be adjusted somehow anyway, we could also get the PLL clock
directly and set it's rate, instead of relying on that rate propagation
algorithm. I think we could also export a function from the exynos-lpass mfd
driver for setting the PLL's rate directly, after listing the AUD PLL clock
in the lpass DT node. That would be more flexible API, easier to adopt for
various use cases/boards, now we have only TM2. I can't list the PLL clock
in the sound node, that would not have passed the DT maintainters' review.
--
Regards,
Sylwester
WARNING: multiple messages have this Message-ID (diff)
From: s.nawrocki@samsung.com (Sylwester Nawrocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] clk: exynos5433: Allow audio subsystem clock rate propagation
Date: Wed, 07 Feb 2018 16:18:32 +0100 [thread overview]
Message-ID: <3fcfad37-4c8f-7375-b2c2-5154607aa47a@samsung.com> (raw)
In-Reply-To: <5A7929C1.8040706@samsung.com>
Hi Chanwoo,
On 02/06/2018 05:06 AM, Chanwoo Choi wrote:
>> drivers/clk/samsung/clk-exynos5433.c | 22 +++++++++++-----------
>> 1 file changed, 11 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/clk/samsung/clk-exynos5433.c b/drivers/clk/samsung/clk-exynos5433.c
>> index 74b70ddab4d6..d74361736e64 100644
>> --- a/drivers/clk/samsung/clk-exynos5433.c
>> +++ b/drivers/clk/samsung/clk-exynos5433.c
>> @@ -246,14 +246,14 @@ static const struct samsung_fixed_rate_clock top_fixed_clks[] __initconst = {
>>
>> static const struct samsung_mux_clock top_mux_clks[] __initconst = {
>> /* MUX_SEL_TOP0 */
>> - MUX(CLK_MOUT_AUD_PLL, "mout_aud_pll", mout_aud_pll_p, MUX_SEL_TOP0,
>> - 4, 1),
>> + MUX_F(CLK_MOUT_AUD_PLL, "mout_aud_pll", mout_aud_pll_p, MUX_SEL_TOP0,
>> + 4, 1, CLK_SET_RATE_PARENT, 0),
>
> If you add CLK_SET_RATE_PARENT to 'mout_aud_pll' and mout_aud_pll changes the rate,
> fout_aud_pll's rate will be changed. But, fout_aud_pll is also the parent
> of 'mout_aud_pll_user'. It might change the rate of children of mout_aud_pll_user.
> mout_aud_pll_user would not want to change the parent's clock.
>
> fout_aud_pll 2 2 196608009 0 0
> mout_aud_pll_user 1 1 196608009 0 0
> mout_aud_pll 0 0 196608009 0 0
I'd say the range of changes is such that the consumers of the affected child
clocks can cope and could adjust to the changed frequencies. Those consumer
devices are all components/peripherals of the audio subsystem (LPASS) and,
for example, in case of TM2 there is no issues at all with varying the AUD PLL
frequency depending on the HDMI audio sample rate. The other audio path uses
the audio CODEC's internal PLL as the root clock source. The AUD PLL frequency
will need to be adjusted somehow anyway, we could also get the PLL clock
directly and set it's rate, instead of relying on that rate propagation
algorithm. I think we could also export a function from the exynos-lpass mfd
driver for setting the PLL's rate directly, after listing the AUD PLL clock
in the lpass DT node. That would be more flexible API, easier to adopt for
various use cases/boards, now we have only TM2. I can't list the PLL clock
in the sound node, that would not have passed the DT maintainters' review.
--
Regards,
Sylwester
next prev parent reply other threads:[~2018-02-07 15:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180205142252epcas1p4471e32e2b513806420c64b323af2ffa6@epcas1p4.samsung.com>
2018-02-05 14:22 ` [PATCH 1/3] clk: exynos5433: Extend list of available AUD_PLL output frequencies Sylwester Nawrocki
2018-02-05 14:22 ` Sylwester Nawrocki
[not found] ` <CGME20180205142308epcas2p376f8656f7e421f8474938de788cea8db@epcas2p3.samsung.com>
2018-02-05 14:22 ` [PATCH 2/3] clk: exynos5433: Allow audio subsystem clock rate propagation Sylwester Nawrocki
2018-02-05 14:22 ` Sylwester Nawrocki
2018-02-06 4:06 ` Chanwoo Choi
2018-02-06 4:06 ` Chanwoo Choi
2018-02-07 15:18 ` Sylwester Nawrocki [this message]
2018-02-07 15:18 ` Sylwester Nawrocki
2018-02-09 7:36 ` Chanwoo Choi
2018-02-09 7:36 ` Chanwoo Choi
2018-02-12 11:45 ` Sylwester Nawrocki
2018-02-12 11:45 ` Sylwester Nawrocki
2018-02-12 21:44 ` Chanwoo Choi
2018-02-12 21:44 ` Chanwoo Choi
[not found] ` <CGME20180205142314epcas1p2c9b9bdcba33290a9528a1b24fbc849eb@epcas1p2.samsung.com>
2018-02-05 14:22 ` [PATCH 3/3] clk: exynos5433: Add CLK_IGNORE_UNUSED flag to sclk_ioclk_i2s1_bclk Sylwester Nawrocki
2018-02-05 14:22 ` Sylwester Nawrocki
2018-02-06 4:08 ` Chanwoo Choi
2018-02-06 4:08 ` Chanwoo Choi
2018-02-14 14:52 ` Sylwester Nawrocki
2018-02-14 14:52 ` Sylwester Nawrocki
2018-02-06 2:44 ` [PATCH 1/3] clk: exynos5433: Extend list of available AUD_PLL output frequencies Chanwoo Choi
2018-02-06 2:44 ` Chanwoo Choi
2018-02-07 10:29 ` Sylwester Nawrocki
2018-02-07 10:29 ` Sylwester Nawrocki
2018-02-07 11:24 ` Chanwoo Choi
2018-02-07 11:24 ` Chanwoo Choi
2018-02-07 13:04 ` Sylwester Nawrocki
2018-02-07 13:04 ` Sylwester Nawrocki
2018-02-09 7:25 ` Chanwoo Choi
2018-02-09 7:25 ` Chanwoo Choi
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=3fcfad37-4c8f-7375-b2c2-5154607aa47a@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.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.