From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nick Hu <nick.hu@sifive.com>
Cc: Cyan Yang <cyan.yang@sifive.com>,
Samuel Holland <samuel.holland@sifive.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH] dt-bindings: power: Add SiFive Domain Management controllers
Date: Mon, 12 May 2025 12:39:37 +0200 [thread overview]
Message-ID: <bd001136-eb48-44f0-8724-09eeb022df8e@kernel.org> (raw)
In-Reply-To: <CAKddAkAzDGL-7MbroRqQnZzPXOquUMKNuGGppqB-d_XZXbcvBA@mail.gmail.com>
On 12/05/2025 05:20, Nick Hu wrote:
> On Fri, May 9, 2025 at 2:40 PM Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> On Fri, May 09, 2025 at 10:16:04AM GMT, Nick Hu wrote:
>>> SiFive Domain Management controller includes the following components
>>> - SiFive Tile Management Controller
>>> - SiFive Cluster Management Controller
>>> - SiFive Core Complex Management Controller
>>>
>>> These controllers control the clock and power domain of the
>>> corresponding domain.
>>>
>>> Signed-off-by: Nick Hu <nick.hu@sifive.com>
>>> Reviewed-by: Samuel Holland <samuel.holland@sifive.com>
>>> ---
>>> .../devicetree/bindings/power/sifive,tmc.yaml | 89 +++++++++++++++++++
>>
>> Where is a patch with the driver (user of the binding)?
>>
> We are hoping the driver can be submitted at a later stage.
> The driver that handles the MMIO is implemented in OpenSBI and depends
> on some prerequisite patches [1], so it will follow afterward.
This patch alone makes little sense and brings little benefit. Post this
with user.
...
>>> + reg:
>>> + maxItems: 1
>>> +
>>> + sifive,feature-level:
>>> + description: |
>>> + Supported power features. This property is absent if the full set of features
>>> + is supported
>>
>> Compatible defines this. Drop.
>>
> The property depends on how the IP is hooked up to the rest of the SoC.
> Having this property simplifies the SW and allows us to use a single
> fallback compatible string, so we prefer to keep it.
And we prefer you to follow standard DT rules, see writing bindings or
talks on conferences.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-12 10:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 2:16 Nick Hu
2025-05-09 6:40 ` Krzysztof Kozlowski
2025-05-09 15:57 ` Conor Dooley
2025-05-10 14:57 ` Krzysztof Kozlowski
2025-05-12 3:28 ` Nick Hu
2025-05-12 3:26 ` Nick Hu
2025-05-12 3:20 ` Nick Hu
2025-05-12 10:39 ` Krzysztof Kozlowski [this message]
2025-05-12 11:00 ` Conor Dooley
2025-05-28 3:15 ` Nick Hu
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=bd001136-eb48-44f0-8724-09eeb022df8e@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cyan.yang@sifive.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=nick.hu@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=samuel.holland@sifive.com \
/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
all inboxes | Powered by JetHome®