From: Sylwester Nawrocki <snawrocki@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: linux-samsung-soc@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-clk@vger.kernel.org, linux-pm@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Lukasz Luba <lukasz.luba@arm.com>
Subject: Re: [PATCH v2] clk: samsung: Keep top BPLL mux on Exynos542x enabled
Date: Mon, 24 Aug 2020 12:28:51 +0200 [thread overview]
Message-ID: <fff07b05-f1f6-5333-a056-69ba6995ed4f@kernel.org> (raw)
In-Reply-To: <f4c87130-25a0-2195-9caa-be805d207c34@kernel.org>
On 8/23/20 12:12, Sylwester Nawrocki wrote:
> On 8/19/20 05:14, Stephen Boyd wrote:
>> Quoting Marek Szyprowski (2020-08-07 06:31:43)
>>> BPLL clock must not be disabled because it is needed for proper DRAM
>>> operation. This is normally handled by respective memory devfreq driver,
>>> but when that driver is not yet probed or its probe has been deferred
>>> the
>>> clock might got disabled what causes board hang. Fix this by calling
>>> clk_prepare_enable() directly from the clock provider driver.
>>>
>>> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
>>> Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
>>> Tested-by: Lukasz Luba <lukasz.luba@arm.com>
>>> Acked-by: Krzysztof Kozlowski <krzk@kernel.org>
>>> ---
>>
>> Can I pick this up for clk-fixes?
>
> Sure, thanks for taking care of this.
OTOH, I planned to queue that patch for next merged window, together
with a patch that depends on that one, since the fix is not for an issue
introduced in the last merge window.
I guess it's better to avoid pulling (part of) the clk-fixes branch to
the clk/samsung tree for next merge window?
next prev parent reply other threads:[~2020-08-24 10:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200807133152eucas1p1d83611a984f5c5d875192d08e2f5711f@eucas1p1.samsung.com>
2020-08-07 13:31 ` [PATCH v2] clk: samsung: Keep top BPLL mux on Exynos542x enabled Marek Szyprowski
2020-08-10 2:58 ` Chanwoo Choi
2020-08-11 11:31 ` Sylwester Nawrocki
2020-08-19 3:12 ` Stephen Boyd
2020-08-19 3:14 ` Stephen Boyd
2020-08-23 10:12 ` Sylwester Nawrocki
2020-08-24 10:28 ` Sylwester Nawrocki [this message]
2020-08-24 10:31 ` Krzysztof Kozlowski
2020-09-02 9:24 ` Sylwester Nawrocki
2020-09-15 12:43 ` Sylwester Nawrocki
2020-09-15 16:17 ` Stephen Boyd
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=fff07b05-f1f6-5333-a056-69ba6995ed4f@kernel.org \
--to=snawrocki@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=krzk@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=m.szyprowski@samsung.com \
--cc=sboyd@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox