From: Sven Eckelmann <sven@narfation.org>
To: openwrt-devel@lists.openwrt.org
Cc: Павел <be.dissent@gmail.com>, "Petr Štetiar" <ynezz@true.cz>,
"Christian Lamparter" <chunkeey@gmail.com>,
"Andy Gross" <agross@kernel.org>,
"David Brown" <david.brown@linaro.org>,
linux-arm-msm@vger.kernel.org,
"Varadarajan Narayanan" <varada@codeaurora.org>,
"Gopinath Sekar" <gsekar@codeaurora.org>
Subject: Re: [OpenWrt-Devel] [PATCH 2/4] ipq40xx: fix sleep clock
Date: Thu, 16 May 2019 14:22:14 +0200 [thread overview]
Message-ID: <5064672.lGSt0B6DOn@bentobox> (raw)
In-Reply-To: <CAEdN=pFJ_AoNftsHySvZU6Vsf+L8tP7gccfABms-X6GMz0TFoA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]
On Tuesday, 14 May 2019 15:42:18 CEST Pavel Kubelun wrote:
> +--- a/arch/arm/boot/dts/qcom-ipq4019.dtsi
> ++++ b/arch/arm/boot/dts/qcom-ipq4019.dtsi
> +@@ -141,9 +141,9 @@
> + };
> +
> + clocks {
> +- sleep_clk: sleep_clk {
> ++ sleep_clk: gcc_sleep_clk_src {
> + compatible = "fixed-clock";
> +- clock-frequency = <32768>;
> ++ clock-frequency = <32000>;
> + #clock-cells = <0>;
> + };
On Thursday, 16 May 2019 13:18:14 CEST Павел wrote:
[...]
> > And maybe some of these guys also know how to find the ipq40xx clock
> > controller reference or hardware reference. Because I was only able to
> > verify
> > for IPQ8072 that it had a 32.768 KHz sleep clock. But the
> >
>
> If you are completely sure about that, then I guess that they have
> (un)intentionally messed with the clock in QSDK, because they state that
> ipq807x has the same 32000 khz crystal.
> https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/tree/arch/arm64/boot/dts/qcom/qcom-ipq807x-soc.dtsi?h=eggplant#n2055
Confidence is the wrong word. I can only state that this is written in
80-YA727-13 Rev. D (IPQ8072.AP.HK07). Same for other devices like
IPQ8078 AP.HK02, IPQ8074 AP.HK01, ...
But I found in the same document that they call it the "32 KHz sleep clock in"
in one section and and in another table "32.768 KHz sleep clock input to the
IPQ8072" (next to the name "...32K..."). So it is now to the reader to find
out what they meant here in which reference document. So maybe they also meant
32.768 KHz when in the IPQ4019 Watchdog document when they wrote 32 Khz sleep
clock... who knows.
My gut feeling (sorry, not an HW guy) tell me that they are just using a
32.768 KHz clock (from a standard 32.768 KHz oscillator) in all these products
and just shortened it to 32K at some point in the document. And now Gopinath
Sekar wrote 32000 instead of 32768. But I absolutely don't know what actually
is there in HW.
Kind regards,
Sven
[1] https://source.codeaurora.org/quic/qsdk/oss/kernel/linux-msm/commit/?id=d92ec59973484acc86dd24b67f10f8911b4b4b7d
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2019-05-16 12:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAEdN=pFJ_AoNftsHySvZU6Vsf+L8tP7gccfABms-X6GMz0TFoA@mail.gmail.com>]
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=5064672.lGSt0B6DOn@bentobox \
--to=sven@narfation.org \
--cc=agross@kernel.org \
--cc=be.dissent@gmail.com \
--cc=chunkeey@gmail.com \
--cc=david.brown@linaro.org \
--cc=gsekar@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=openwrt-devel@lists.openwrt.org \
--cc=varada@codeaurora.org \
--cc=ynezz@true.cz \
/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