From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Binbin Zhou <zhoubb.aaron@gmail.com>, Conor Dooley <conor@kernel.org>
Cc: Binbin Zhou <zhoubinbin@loongson.cn>,
Huacai Chen <chenhuacai@loongson.cn>,
Yinbo Zhu <zhuyinbo@loongson.cn>, Arnd Bergmann <arnd@arndb.de>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Huacai Chen <chenhuacai@kernel.org>,
loongson-kernel@lists.loongnix.cn, devicetree@vger.kernel.org,
linux-pm@vger.kernel.org, Xuerui Wang <kernel@xen0n.name>,
loongarch@lists.linux.dev
Subject: Re: [PATCH 2/5] dt-bindings: soc: loongson,ls2k-pmc: Add missing compatible for Loongson-2K2000
Date: Tue, 29 Aug 2023 08:29:43 +0200 [thread overview]
Message-ID: <3fd27e64-2221-ec38-1320-9ae966f998aa@linaro.org> (raw)
In-Reply-To: <CAMpQs4Jp0rb8sbrLrPnNziLph4Ym4LxBsFt-00G69ecd8bUHNg@mail.gmail.com>
On 29/08/2023 05:21, Binbin Zhou wrote:
> HI Conor:
>
> Thanks for your reply.
>
> On Mon, Aug 28, 2023 at 11:49 PM Conor Dooley <conor@kernel.org> wrote:
>>
>> On Mon, Aug 28, 2023 at 08:38:32PM +0800, Binbin Zhou wrote:
>>> Document the Power Management Unit system controller compatible for
>>> Loongson-2K2000.
>>>
>>> This is a missing compatible, now we add it.
>>>
>>> Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>
>>> ---
>>> .../devicetree/bindings/soc/loongson/loongson,ls2k-pmc.yaml | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/soc/loongson/loongson,ls2k-pmc.yaml b/Documentation/devicetree/bindings/soc/loongson/loongson,ls2k-pmc.yaml
>>> index da2dcfeebf12..7473c5659929 100644
>>> --- a/Documentation/devicetree/bindings/soc/loongson/loongson,ls2k-pmc.yaml
>>> +++ b/Documentation/devicetree/bindings/soc/loongson/loongson,ls2k-pmc.yaml
>>> @@ -15,6 +15,7 @@ properties:
>>> - enum:
>>> - loongson,ls2k0500-pmc
>>> - loongson,ls2k1000-pmc
>>> + - loongson,ls2k2000-pmc
>>
>> Same thing here as the driver patch, the pmc on this newly added SoC
>> appears to use the same codepaths as the existing ones. Does it share a
>> programming model & should there be a fallback compatible here?
>
> I noticed the guideline about fallback compatible:
>
> "DO use fallback compatibles when devices are the same as or a subset
> of prior implementations."
>
> But in fact, ls2k0500/ls2k1000/ls2k2000 are independent, there is no subset.
We do not consider here ls2k0500/ls2k1000/ls2k2000, but PMC in each of
them. If they are independent, why would they use the same interface?
> Can we define a "loongson,ls2k-pmc" superset for each ls2k SoC
> compatible fallback.
>
> Such as:
>
> compatible:
> oneOf:
> - enum:
> - loongson,ls2k0500-pmc
> - loongson,ls2k1000-pmc
> - loongson,ls2k2000-pmc
> - const: loongson,ls2k-pmc
This is discouraged. Use 0500 as fallback.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-29 6:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 12:38 [PATCH 0/5] soc: loongson: Fix some issues about loongson_pm2 Binbin Zhou
2023-08-28 12:38 ` [PATCH 1/5] soc: loongson: loongson_pm2: add dependency for INPUT Binbin Zhou
2023-08-28 17:25 ` Krzysztof Kozlowski
2023-08-28 20:50 ` Randy Dunlap
2023-08-28 12:38 ` [PATCH 2/5] dt-bindings: soc: loongson,ls2k-pmc: Add missing compatible for Loongson-2K2000 Binbin Zhou
2023-08-28 15:49 ` Conor Dooley
2023-08-29 3:21 ` Binbin Zhou
2023-08-29 6:29 ` Krzysztof Kozlowski [this message]
2023-08-29 6:42 ` Conor Dooley
2023-08-29 6:52 ` Binbin Zhou
2023-08-31 16:39 ` Rob Herring
2023-08-28 12:38 ` [PATCH 3/5] soc: loongson: loongson_pm2: " Binbin Zhou
2023-08-28 15:32 ` Conor Dooley
2023-08-29 6:28 ` Krzysztof Kozlowski
2023-08-28 12:38 ` [PATCH 4/5] dt-bindings: soc: loongson,ls2k-pmc: Allow syscon-reboot/syscon-poweroff as child Binbin Zhou
2023-08-28 17:17 ` Krzysztof Kozlowski
2023-08-29 2:15 ` Binbin Zhou
2023-08-28 12:39 ` [PATCH 5/5] soc: loongson: loongson_pm2: Populate children syscon nodes Binbin Zhou
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=3fd27e64-2221-ec38-1320-9ae966f998aa@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=robh+dt@kernel.org \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@loongson.cn \
--cc=zhuyinbo@loongson.cn \
/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).