From: Stephen Boyd <sboyd@codeaurora.org>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Jun Nie <jun.nie@linaro.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: zx296718: register driver earlier with core_initcall
Date: Fri, 23 Sep 2016 14:43:51 -0700 [thread overview]
Message-ID: <20160923214351.GB21232@codeaurora.org> (raw)
In-Reply-To: <1474595108-15790-1-git-send-email-shawn.guo@linaro.org>
On 09/23, Shawn Guo wrote:
> Clock driver should be registered with an earlier initcall than
> module_init which is used by most of client device drivers. Otherwise,
> probing of these client drivers will likely be deferred due to that
> calls into clk API will return -EPROBE_DEFER.
>
> Deferred probing is not a problem for most subsystems, but could bring
> some side effect for particular subsystem, like display. On ZX296718
> platform, we get Linux logo and boot log lost from display device, just
> because the DRM/KMS driver gets -EPROBE_DEFER from devm_clk_get() call.
>
> Let's use core_initcall (qcom and a few other clk drivers use that) for
> driver registration to avoid those unnecessary -EPROBE_DEFER and get rid
> of the side effect with ZX296718 display system.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
Not the ideal solution but it'll do for now.
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: zx296718: register driver earlier with core_initcall
Date: Fri, 23 Sep 2016 14:43:51 -0700 [thread overview]
Message-ID: <20160923214351.GB21232@codeaurora.org> (raw)
In-Reply-To: <1474595108-15790-1-git-send-email-shawn.guo@linaro.org>
On 09/23, Shawn Guo wrote:
> Clock driver should be registered with an earlier initcall than
> module_init which is used by most of client device drivers. Otherwise,
> probing of these client drivers will likely be deferred due to that
> calls into clk API will return -EPROBE_DEFER.
>
> Deferred probing is not a problem for most subsystems, but could bring
> some side effect for particular subsystem, like display. On ZX296718
> platform, we get Linux logo and boot log lost from display device, just
> because the DRM/KMS driver gets -EPROBE_DEFER from devm_clk_get() call.
>
> Let's use core_initcall (qcom and a few other clk drivers use that) for
> driver registration to avoid those unnecessary -EPROBE_DEFER and get rid
> of the side effect with ZX296718 display system.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
Not the ideal solution but it'll do for now.
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-09-23 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 1:45 [PATCH] clk: zx296718: register driver earlier with core_initcall Shawn Guo
2016-09-23 1:45 ` Shawn Guo
2016-09-23 21:43 ` Stephen Boyd [this message]
2016-09-23 21:43 ` 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=20160923214351.GB21232@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=jun.nie@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=shawn.guo@linaro.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.