From: Bjorn Andersson <andersson@kernel.org>
To: Adam Skladowski <a39.skl@gmail.com>
Cc: linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Marijn Suijten <marijn.suijten@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Andy Gross <agross@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Subject: Re: (subset) [PATCH 1/2] arm64: dts: qcom: msm8976: Add and provide xo clk to rpmcc
Date: Wed, 15 Mar 2023 20:20:50 -0700 [thread overview]
Message-ID: <167893686410.303819.4842310251256800007.b4-ty@kernel.org> (raw)
In-Reply-To: <20230302123051.12440-1-a39.skl@gmail.com>
On Thu, 2 Mar 2023 13:30:49 +0100, Adam Skladowski wrote:
> In order for consumers of RPMCC XO clock to probe successfully
> their parent needs to be feed with reference clock to obtain proper rate,
> add fixed xo-board clock and supply it to rpmcc to make consumers happy.
> Frequency setting is left per board basis just like on other recent trees.
>
>
Applied, thanks!
[1/2] arm64: dts: qcom: msm8976: Add and provide xo clk to rpmcc
commit: 4a2c9b9e1215c557c17a48e3fabe9b1674c1d608
[2/2] arm64: dts: qcom: msm8956-loire: Provide rate for xo_board clock
commit: 4a2c9b9e1215c557c17a48e3fabe9b1674c1d608
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-03-16 3:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 12:30 [PATCH 1/2] arm64: dts: qcom: msm8976: Add and provide xo clk to rpmcc Adam Skladowski
2023-03-02 12:30 ` [PATCH 2/2] arm64: dts: qcom: msm8956-loire: Provide rate for xo_board clock Adam Skladowski
2023-03-02 16:38 ` Dmitry Baryshkov
2023-03-02 18:12 ` Dmitry Baryshkov
2023-03-02 16:40 ` [PATCH 1/2] arm64: dts: qcom: msm8976: Add and provide xo clk to rpmcc Dmitry Baryshkov
2023-03-03 0:52 ` Konrad Dybcio
2023-03-16 3:20 ` Bjorn Andersson [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=167893686410.303819.4842310251256800007.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=a39.skl@gmail.com \
--cc=agross@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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.