From: Shawn Guo <shawn.guo@linaro.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@somainline.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Andy Gross <agross@kernel.org>,
Akash Asthana <akashast@codeaurora.org>,
linux-arm-msm@vger.kernel.org, konrad.dybcio@somainline.org,
marijn.suijten@somainline.org
Subject: Re: [PATCH] soc: qcom: geni: shield ICC calls for ACPI boot
Date: Thu, 14 Jan 2021 11:18:29 +0800 [thread overview]
Message-ID: <20210114031828.GA24107@dragon> (raw)
In-Reply-To: <32e270de-3d23-f26d-9dd3-85a654a4ad52@somainline.org>
On Thu, Jan 14, 2021 at 12:17:23AM +0100, AngeloGioacchino Del Regno wrote:
> Il 28/12/20 14:56, Shawn Guo ha scritto:
> > Currently, GENI devices like i2c-qcom-geni fails to probe in ACPI boot,
> > if interconnect support is enabled. That's because interconnect driver
> > only supports DT right now. As interconnect is not necessarily required
> > for basic function of GENI devices, let's shield those ICC calls to get
> > GENI devices probe for ACPI boot.
> >
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > ---
> > drivers/soc/qcom/qcom-geni-se.c | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
> >
> Hello!
>
> To avoid developers booting on ACPI getting "strange slownesses" and
> possibly timeouts with no apparent reason, wouldn't it be a bit more proper
> and friendly to actually send a kernel message to advertise that there is
> *no interconnect support* and that this may lead to the aforementioned
> potential issues?
Thanks for the comment.
The commit 58ffbba6a399 ("soc: qcom: geni: Support for ICC voting")
was landed just recently, and we have been running those geni-se device
drivers without ICC voting for years. I doubt it would have been the
case if missing ICC from any of those geni-se will cause any strange
slowness or timeout issues.
There are only a limited number of drivers on Snapdragon that support
ACPI boot right now. We are running it with distro installer, and
haven't seen any slowness or timeout.
In short, I prefer to add warnings that are really helpful rather than
just something noisy.
Shawn
next prev parent reply other threads:[~2021-01-14 3:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 13:56 [PATCH] soc: qcom: geni: shield ICC calls for ACPI boot Shawn Guo
2021-01-13 23:17 ` AngeloGioacchino Del Regno
2021-01-14 3:18 ` Shawn Guo [this message]
2021-01-14 4:12 ` Bjorn Andersson
2021-01-14 11:25 ` Shawn Guo
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=20210114031828.GA24107@dragon \
--to=shawn.guo@linaro.org \
--cc=agross@kernel.org \
--cc=akashast@codeaurora.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=bjorn.andersson@linaro.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=marijn.suijten@somainline.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