From: Petr Vorel <petr.vorel@gmail.com>
To: linux-arm-msm@vger.kernel.org
Cc: Konrad Dybcio <konradybcio@gmail.com>,
Alexey Minnekhanov <alexeymin@postmarketos.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
devicetree@vger.kernel.org, Jean Thomas <virgule@jeanthomas.me>
Subject: Re: [PATCH 1/1] arm64: dts: qcom: bullhead: Fix sdcard1 overclocking
Date: Wed, 23 Mar 2022 21:44:53 +0100 [thread overview]
Message-ID: <YjuGxQNt8xUZdW8J@pevik> (raw)
In-Reply-To: <20220221200540.14460-1-petr.vorel@gmail.com>
Hi,
> rev 1.01 (msm8992-lg-bullhead-rev-101.dts) has overclocking warnings:
> [ 1.997606] mmc0: Card appears overclocked; req 200000000 Hz, actual 343999999 Hz
> [ 1.997681] mmc0: Card appears overclocked; req 200000000 Hz, actual 343999999 Hz
> [ 2.010904] mmc0: Card appears overclocked; req 400000000 Hz, actual 687999999 Hz
> [ 2.012961] mmc0: Card appears overclocked; req 200000000 Hz, actual 343999999 Hz
> [ 2.027497] mmc0: Card appears overclocked; req 400000000 Hz, actual 687999999 Hz
> [ 2.027607] mmc0: Card appears overclocked; req 400000000 Hz, actual 687999999 Hz
> [ 2.039699] mmc0: new HS400 MMC card at address 0001
> Similarly to angler use gcc GPLL4_EARLY to get rid of the warnings.
> Not tested on 1.0, but should work here as well.
As I wrote at Konrad's patch "clk: qcom: gcc-msm8994: Fix gpll4 width" [1]
with that fix this workaround is not needed if Konrad's patch applied.
Kind regards,
Petr
[1] https://lore.kernel.org/linux-arm-msm/YjuE+cgGXCLihPIa@pevik/T/#t
prev parent reply other threads:[~2022-03-23 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 20:05 [PATCH 1/1] arm64: dts: qcom: bullhead: Fix sdcard1 overclocking Petr Vorel
2022-03-23 20:44 ` Petr Vorel [this message]
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=YjuGxQNt8xUZdW8J@pevik \
--to=petr.vorel@gmail.com \
--cc=agross@kernel.org \
--cc=alexeymin@postmarketos.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=virgule@jeanthomas.me \
/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