From: Shawn Guo <email@example.com>
To: Bjorn Andersson <firstname.lastname@example.org>
Cc: Stephen Boyd <email@example.com>, Rob Herring <firstname.lastname@example.org>,
Loic Poulain <email@example.com>,
Subject: Re: [PATCH 1/3] clk: qcom: smd-rpm: Add rate hooks for clk_smd_rpm_branch_ops
Date: Wed, 15 Sep 2021 23:12:37 +0800 [thread overview]
Message-ID: <20210915151236.GF25255@dragon> (raw)
On Tue, Sep 14, 2021 at 07:55:21PM -0700, Bjorn Andersson wrote:
> On Mon 13 Sep 19:55 PDT 2021, Shawn Guo wrote:
> > On QCM2290 platform, the clock xo_board runs at 38400000, while the
> > child clock bi_tcxo needs to run at 19200000. That said,
> > clk_smd_rpm_branch_ops needs the capability of setting rate. Add rate
> > hooks into clk_smd_rpm_branch_ops to make it possible.
> Most platforms has a crystal oscillator ticking at 38.4MHz feeding the
> PMIC (represented by the rpmcc and its "xo" parent) and out comes the
> bi_tcxo with a fixed 19.2MHz rate.
Yeah, but all those platforms are running clk-rpmh driver, I think.
> Is there a problem with the way sdm660_bi_tcxo is defined in this
There is no problem if xo clock is 19.2MHz, but for platforms with
38.4MHz xo, bi_tcxo will be seen as 38.4MHz in clock tree, while we
expect it to be 19.2MHz.
next prev parent reply other threads:[~2021-09-15 15:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 2:55 [PATCH 0/3] Add QCM2290 RPM clocks support Shawn Guo
2021-09-14 2:55 ` [PATCH 1/3] clk: qcom: smd-rpm: Add rate hooks for clk_smd_rpm_branch_ops Shawn Guo
2021-09-14 21:56 ` Stephen Boyd
2021-09-15 15:05 ` Shawn Guo
2021-09-15 17:23 ` Bjorn Andersson
2021-09-15 17:44 ` Bjorn Andersson
2021-09-16 5:04 ` Shawn Guo
2021-09-15 2:55 ` Bjorn Andersson
2021-09-15 15:12 ` Shawn Guo [this message]
2021-09-14 2:55 ` [PATCH 2/3] dt-bindings: clk: qcom,rpmcc: Document QCM2290 compatible Shawn Guo
2021-09-14 2:55 ` [PATCH 3/3] clk: qcom: smd-rpm: Add QCM2290 RPM clock support Shawn Guo
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.