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>,
Jassi Brar <jassisinghbrar@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Manivannan Sadhasivam <mani@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 00/13] mailbox/arm64/ qcom: rework compatibles for fallback
Date: Thu, 16 Mar 2023 07:52:31 +0100 [thread overview]
Message-ID: <290b9b19-a320-38a1-4426-51f5725dd54f@linaro.org> (raw)
In-Reply-To: <c35fd641-12ff-beba-341c-4d0305bcaa40@linaro.org>
On 14/03/2023 13:16, Dmitry Baryshkov wrote:
> On 14/03/2023 10:09, Krzysztof Kozlowski wrote:
>> Hi,
>>
>> Changes since v1
>> ================
>> 1. Rebase
>> 2. Make msm8994 fallback for several variants, not msm8953, because the latter
>> actually might take some clocks.
>
> Although the approach looks correct, I think that in some cases it tries
> to mark devices compatible judging from the current driver, not from the
> hardware itself.
Which is what compatibility is about...
>
> For the reference, on msm8994 the apcs is a clock controller for the l2
> clocks (which we do not support yet). If I'm not mistaken, on msm8976
> the apcs region contains a mux for the cluster1 clocks. On sdm630/660
> the apcs region also seems to be involved in CPU clocks scaling.
The question is this means they are incompatible?
>
> On the other hand, the sc7180/sm8150 part seems logical.
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-16 6:52 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 8:09 [PATCH v2 00/13] mailbox/arm64/ qcom: rework compatibles for fallback Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 01/13] dt-bindings: mailbox: qcom,apcs-kpss-global: correct SDX55 clocks Krzysztof Kozlowski
2023-03-17 21:07 ` Rob Herring
2023-03-17 21:07 ` Rob Herring
2023-03-20 10:39 ` Manivannan Sadhasivam
2023-03-14 8:09 ` [PATCH v2 02/13] dt-bindings: mailbox: qcom,apcs-kpss-global: fix SDX55 'if' match Krzysztof Kozlowski
2023-03-17 21:07 ` Rob Herring
2023-03-20 10:40 ` Manivannan Sadhasivam
2023-03-14 8:09 ` [PATCH v2 03/13] dt-bindings: mailbox: qcom,apcs-kpss-global: use fallbacks Krzysztof Kozlowski
2023-03-17 21:08 ` Rob Herring
2023-03-14 8:09 ` [PATCH v2 04/13] mailbox: qcom-apcs-ipc: do not grow the of_device_id Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 05/13] arm64: dts: qcom: ipq8074: add compatible fallback to mailbox Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 06/13] arm64: dts: qcom: msm8976: " Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 07/13] arm64: dts: qcom: msm8998: " Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 08/13] arm64: dts: qcom: sdm630: " Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 09/13] arm64: dts: qcom: sm6115: " Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 10/13] arm64: dts: qcom: sm6125: " Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 11/13] arm64: dts: qcom: qcs404: " Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 12/13] arm64: dts: qcom: sc7180: " Krzysztof Kozlowski
2023-03-14 8:09 ` [PATCH v2 13/13] arm64: dts: qcom: sm8150: " Krzysztof Kozlowski
2023-03-14 12:16 ` [PATCH v2 00/13] mailbox/arm64/ qcom: rework compatibles for fallback Dmitry Baryshkov
2023-03-16 6:52 ` Krzysztof Kozlowski [this message]
2023-03-22 17:37 ` Krzysztof Kozlowski
2023-03-22 22:28 ` Dmitry Baryshkov
2023-03-23 6:33 ` Krzysztof Kozlowski
2023-03-23 9:44 ` Dmitry Baryshkov
2023-03-27 13:43 ` Krzysztof Kozlowski
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=290b9b19-a320-38a1-4426-51f5725dd54f@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=jassisinghbrar@gmail.com \
--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=mani@kernel.org \
--cc=robh+dt@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).