From: Melody Olvera <quic_molvera@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Bhupesh Sharma <bhupesh.sharma@linaro.org>,
<linux-arm-msm@vger.kernel.org>, <linux-mmc@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/5] dt-bindings: firmware: scm: Add QDU1000/QRU1000 compatibles
Date: Tue, 4 Oct 2022 11:08:30 -0500 [thread overview]
Message-ID: <bd50fcb0-f0a4-6552-e9df-c356c32972f1@quicinc.com> (raw)
In-Reply-To: <095742cb-61cc-af5d-848c-48b2ea5528ea@quicinc.com>
On 10/4/2022 10:52 AM, Melody Olvera wrote:
> On 10/4/2022 2:36 AM, Dmitry Baryshkov wrote:
>> On Tue, 4 Oct 2022 at 09:53, Krzysztof Kozlowski
>> <krzysztof.kozlowski@linaro.org> wrote:
>>> On 04/10/2022 00:14, Dmitry Baryshkov wrote:
>>>> On Tue, 4 Oct 2022 at 01:02, Melody Olvera <quic_molvera@quicinc.com> wrote:
>>>>> On 10/1/2022 4:25 AM, Krzysztof Kozlowski wrote:
>>>>>> On 01/10/2022 05:06, Melody Olvera wrote:
>>>>>>> Add compatibles for scm driver for QDU1000 and QRU1000 platforms.
>>>>>>>
>>>>>>> Signed-off-by: Melody Olvera <quic_molvera@quicinc.com>
>>>>>>> ---
>>>>>>> Documentation/devicetree/bindings/firmware/qcom,scm.yaml | 2 ++
>>>>>>> 1 file changed, 2 insertions(+)
>>>>>>>
>>>>>>> diff --git a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
>>>>>>> index c5b76c9f7ad0..b47a5dda3c3e 100644
>>>>>>> --- a/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
>>>>>>> +++ b/Documentation/devicetree/bindings/firmware/qcom,scm.yaml
>>>>>>> @@ -51,6 +51,8 @@ properties:
>>>>>>> - qcom,scm-sm8250
>>>>>>> - qcom,scm-sm8350
>>>>>>> - qcom,scm-sm8450
>>>>>>> + - qcom,scm-qdu1000
>>>>>>> + - qcom,scm-qru1000
>>>> I think after seeing all the patchsets it's time to ask the following
>>>> question. Do we really need a duplicate compatibility families:
>>>> qdu1000 vs qru1000? I'd suggest using a single set of compatibile
>>>> strings in most of the cases.
>>>> Settle down onto a single name (qdu,qru, qdru, whatever) and define
>>>> distinct compat strings only when there is an actual difference?
>>>>
>>>> E.g .we don't have separate compatible strings for all the sda660,
>>>> apq8096, etc. unless this is required by the corresponding hardware
>>>> block not being compatible with corresponding sdm or msm counterpart.
>>>>
>>> I am not that fluent in Qualcomm naming, so let me ask - what are the
>>> differences between QDU and QRU?
>>>
>>> For compatible (and/or similar) devices the general recommendation is to
>>> have specific compatibles followed by fallback. Even if devices are
>>> very, very, very similar, usually the recommendation still stays.
>> Well, true. But in some cases we handle this by using a single set of
>> compatibles. Consider e.g. sa8155 vs sm8150 (sa8155 overrides just few
>> compats that differ). Or qrb5165 vs sm8250 (there is no separate
>> qrb5165.dtsi). APQ8096 (#include "msm8996.dtsi"). Etc.
>>
>> I'd say this really depends on the actual difference between qru and qdu.
> To add some clarification, there's pretty little functional
> difference between the QDU (Distributed Unit) and the QRU
> (Radio Unit); they're largely the same SoC from the kernel's
> standpoint. I wasn't sure if it made more sense to separate
> the compat strings or mash them together (using qdru to
> specify that it applies to both), so I kept separate compat
> strings in case there was a separate RU/DU use case down
> the line and also to avoid some confusion (I guess that
> didn't work though). It makes the most sense in my mind
> to just use the qdru compat string for the things that apply
> to both SoCs (which is most of what's submitted currently) and
> then we can do qdu/qru specific override strings for more
> specific drivers.
> Thanks, Melody
Fixed formatting.
next prev parent reply other threads:[~2022-10-04 16:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-01 3:06 [PATCH 0/5] Add misc support for QDU1000/QRU1000 SoCs Melody Olvera
2022-10-01 3:06 ` [PATCH 1/5] dt-bindings: firmware: scm: Add QDU1000/QRU1000 compatibles Melody Olvera
2022-10-01 9:25 ` Krzysztof Kozlowski
2022-10-03 22:02 ` Melody Olvera
2022-10-03 22:14 ` Dmitry Baryshkov
2022-10-04 6:53 ` Krzysztof Kozlowski
2022-10-04 7:36 ` Dmitry Baryshkov
2022-10-04 15:52 ` Melody Olvera
2022-10-04 16:08 ` Melody Olvera [this message]
2022-10-04 21:05 ` Dmitry Baryshkov
2022-10-05 8:27 ` Krzysztof Kozlowski
2022-10-05 21:08 ` Trilok Soni
2022-10-01 3:06 ` [PATCH 2/5] dt-bindings: arm: qcom: Document QDU1000/QRU1000 SoCs and boards Melody Olvera
2022-10-01 9:26 ` Krzysztof Kozlowski
2022-10-04 15:16 ` Melody Olvera
2022-10-03 13:24 ` Rob Herring
2022-10-01 3:06 ` [PATCH 3/5] dt-bindings: power: rpmpd: Add QDU1000/QRU1000 to rpmpd binding Melody Olvera
2022-10-01 9:27 ` Krzysztof Kozlowski
2022-10-04 15:19 ` Melody Olvera
2022-10-01 3:06 ` [PATCH 4/5] soc: qcom: rpmhpd: Add QDU1000/QRU1000 power domains Melody Olvera
2022-10-01 7:50 ` Dmitry Baryshkov
2022-10-02 3:14 ` kernel test robot
2022-10-07 3:11 ` Bjorn Andersson
2022-10-12 20:32 ` Melody Olvera
2022-10-01 3:06 ` [PATCH 5/5] soc: qcom: socinfo: Add QDU1000/QRU1000 and variant IDs Melody Olvera
2022-10-01 9:28 ` Krzysztof Kozlowski
2022-10-01 9:34 ` [PATCH 0/5] Add misc support for QDU1000/QRU1000 SoCs Krzysztof Kozlowski
2022-10-04 15:27 ` Melody Olvera
2022-10-04 16:05 ` Melody Olvera
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=bd50fcb0-f0a4-6552-e9df-c356c32972f1@quicinc.com \
--to=quic_molvera@quicinc.com \
--cc=agross@kernel.org \
--cc=bhupesh.sharma@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.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).