[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <845d620b-9d5b-49bd-8f36-6376ecf14249@kernel.org>
Date: Wed, 26 Mar 2025 15:17:07 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Conor Dooley <conor@...nel.org>
Cc: Stephen Boyd <sboyd@...nel.org>, Conor Dooley
<conor.dooley@...rochip.com>, Daire McNamara <daire.mcnamara@...rochip.com>,
pierre-henry.moussay@...rochip.com, valentina.fernandezalanis@...rochip.com,
Michael Turquette <mturquette@...libre.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Jassi Brar <jassisinghbrar@...il.com>, Lee Jones <lee@...nel.org>,
Paul Walmsley <paul.walmsley@...ive.com>, Palmer Dabbelt
<palmer@...belt.com>, Philipp Zabel <p.zabel@...gutronix.de>,
linux-riscv@...ts.infradead.org, linux-clk@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v2 2/9] dt-bindings: soc: microchip: document the
simple-mfd syscon on PolarFire SoC
On 26/03/2025 12:00, Conor Dooley wrote:
> On Wed, Mar 26, 2025 at 07:53:55AM +0100, Krzysztof Kozlowski wrote:
>> On 25/03/2025 17:03, Conor Dooley wrote:
>>> On Tue, Mar 25, 2025 at 09:13:22AM +0100, Krzysztof Kozlowski wrote:
>>>> On Fri, Mar 21, 2025 at 05:22:35PM +0000, Conor Dooley wrote:
>>>>> +title: Microchip PolarFire SoC Microprocessor Subsystem (MSS) sysreg register region
>>>>> +
>>>>> +maintainers:
>>>>> + - Conor Dooley <conor.dooley@...rochip.com>
>>>>> +
>>>>> +description:
>>>>> + An wide assortment of registers that control elements of the MSS on PolarFire
>>>>> + SoC, including pinmuxing, resets and clocks among others.
>>>>> +
>>>>> +properties:
>>>>> + compatible:
>>>>> + items:
>>>>> + - const: microchip,mpfs-mss-top-sysreg
>>>>> + - const: syscon
>>>>> + - const: simple-mfd
>>>>
>>>> You need to list the children if you use simple-mfd. Commit msg
>>>> mentioned clock controller, so where is it?
>>>
>>> I don't think a child node is required here, there's not enough
>>
>> Then this is not a simple-mfd.
>
> The pinctrl will have one, whenever I get around to actually working on
> that. I can leave the simple-mfd out until I establish exactly what
> that's going to look like if that's what you want?
I want complete hardware, so simple-mfd with children, but if that is
not possible for some reason then at least accurate picture, thus drop
simple-mfd for now.
Best regards,
Krzysztof
Powered by blists - more mailing lists