From: Krzysztof Kozlowski <krzk@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
Lukasz Luba <lukasz.luba@arm.com>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
linux-samsung-soc@vger.kernel.org,
Chanwoo Choi <cw00.choi@samsung.com>
Subject: Re: [PATCH] memory: samsung: exynos5422-dmc: propagate error from exynos5_counters_get()
Date: Tue, 4 Aug 2020 08:42:13 +0200 [thread overview]
Message-ID: <20200804064213.GA10089@kozik-lap> (raw)
In-Reply-To: <20200804061210.5415-1-m.szyprowski@samsung.com>
On Tue, Aug 04, 2020 at 08:12:10AM +0200, Marek Szyprowski wrote:
> exynos5_counters_get() might fail with -EPROBE_DEFER if the driver for
> devfreq event counter is not yet probed. Propagate that error value to
> the caller to ensure that the exynos5422-dmc driver will be probed again
> when devfreq event contuner is available.
>
> This fixes boot hang if both exynos5422-dmc and exynos-ppmu drivers are
> compiled as modules.
>
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> ---
> drivers/memory/samsung/exynos5422-dmc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thanks, looks good. I'll apply it to fixes after merge window.
Best regards,
Krzysztof
next prev parent reply other threads:[~2020-08-04 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200804061225eucas1p283c1e0dc404bc420a2184480fdfd2b0d@eucas1p2.samsung.com>
2020-08-04 6:12 ` [PATCH] memory: samsung: exynos5422-dmc: propagate error from exynos5_counters_get() Marek Szyprowski
2020-08-04 6:42 ` Krzysztof Kozlowski [this message]
2020-08-04 9:11 ` Lukasz Luba
2020-08-04 12:19 ` Marek Szyprowski
2020-08-04 12:38 ` Lukasz Luba
2020-08-17 12:07 ` Krzysztof Kozlowski
2020-08-17 12:27 ` Lukasz Luba
2020-08-24 7:44 ` Marek Szyprowski
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=20200804064213.GA10089@kozik-lap \
--to=krzk@kernel.org \
--cc=b.zolnierkie@samsung.com \
--cc=cw00.choi@samsung.com \
--cc=linux-kernel@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 \
/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