From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Taniya Das <quic_tdas@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH v3 09/10] ARM: dts: qcom-mdm9615: specify clocks for the lcc device
Date: Wed, 17 May 2023 09:42:53 +0200 [thread overview]
Message-ID: <10a0c64c-1b56-a1fe-0f4e-3185cce18d1c@linaro.org> (raw)
In-Reply-To: <52005148-c0fb-8bf8-80b8-7c1077cced17@linaro.org>
On 16/05/2023 19:44, Dmitry Baryshkov wrote:
> On 13/05/2023 12:20, Krzysztof Kozlowski wrote:
>> On 12/05/2023 23:17, Dmitry Baryshkov wrote:
>>> Specify clocks used by the LCC device on the MDM9615 platform.
>>>
>>> Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
>>> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
>>> ---
>>> arch/arm/boot/dts/qcom-mdm9615.dtsi | 16 +++++++++++++++-
>>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm/boot/dts/qcom-mdm9615.dtsi b/arch/arm/boot/dts/qcom-mdm9615.dtsi
>>> index b40c52ddf9b4..556abe90cf5b 100644
>>> --- a/arch/arm/boot/dts/qcom-mdm9615.dtsi
>>> +++ b/arch/arm/boot/dts/qcom-mdm9615.dtsi
>>> @@ -39,7 +39,7 @@ cpu-pmu {
>>> };
>>>
>>> clocks {
>>> - cxo_board {
>>> + cxo_board: cxo_board {
>>
>> Maybe it is possible now to change the node name to cxo-board-clk?
>
> This would break compatibility with the possible drivers using
> "cxo_board" sys name. It seems this is the last platform using old
> bindings. Let's probably settle that for 6.6 I can go and rename all
> fixed clock nodes. Would that work for you?
>
Yes, sure.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-17 7:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 21:17 [PATCH v3 00/10] clk: qcom: convert mdm9615 to parent_hws/_data Dmitry Baryshkov
2023-05-12 21:17 ` [PATCH v3 01/10] dt-bindings: clock: qcom,lcc.yaml: describe clocks for lcc,qcom-mdm9615 Dmitry Baryshkov
2023-05-12 21:17 ` [PATCH v3 02/10] dt-bindings: clock: drop qcom,lcc-mdm9615 header file Dmitry Baryshkov
2023-05-12 21:17 ` [PATCH v3 03/10] dt-bindings: clock: provide separate bindings for qcom,gcc-mdm9615 Dmitry Baryshkov
2023-05-12 21:17 ` [PATCH v3 04/10] clk: qcom: gcc-mdm9615: use ARRAY_SIZE instead of specifying num_parents Dmitry Baryshkov
2023-05-12 21:17 ` [PATCH v3 05/10] clk: qcom: drop lcc-mdm9615 in favour of lcc-msm8960 Dmitry Baryshkov
2023-05-12 21:17 ` [PATCH v3 06/10] clk: qcom: gcc-mdm9615: use proper parent for pll0_vote clock Dmitry Baryshkov
2023-05-15 11:38 ` Konrad Dybcio
2023-05-12 21:17 ` [PATCH v3 07/10] clk: qcom: gcc-mdm9615: use parent_hws/_data instead of parent_names Dmitry Baryshkov
2023-05-15 11:40 ` Konrad Dybcio
2023-05-12 21:17 ` [PATCH v3 08/10] clk: qcom: gcc-mdm9615: drop the cxo clock Dmitry Baryshkov
2023-05-15 11:40 ` Konrad Dybcio
2023-06-13 23:41 ` Bjorn Andersson
2023-06-21 14:15 ` Dmitry Baryshkov
2023-05-12 21:17 ` [PATCH v3 09/10] ARM: dts: qcom-mdm9615: specify clocks for the lcc device Dmitry Baryshkov
2023-05-13 9:20 ` Krzysztof Kozlowski
2023-05-16 17:44 ` Dmitry Baryshkov
2023-05-17 7:42 ` Krzysztof Kozlowski [this message]
2023-05-12 21:17 ` [PATCH v3 10/10] ARM: dts: qcom-mdm9615: specify gcc clocks Dmitry Baryshkov
2023-07-31 23:52 ` (subset) [PATCH v3 00/10] clk: qcom: convert mdm9615 to parent_hws/_data Bjorn Andersson
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=10a0c64c-1b56-a1fe-0f4e-3185cce18d1c@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.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;
as well as URLs for NNTP newsgroup(s).