[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241216141846.GA71151-robh@kernel.org>
Date: Mon, 16 Dec 2024 08:18:46 -0600
From: Rob Herring <robh@...nel.org>
To: Peter Griffin <peter.griffin@...aro.org>
Cc: Krzysztof Kozlowski <krzk@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Lee Jones <lee@...nel.org>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org,
tudor.ambarus@...aro.org, andre.draszik@...aro.org,
willmcvicker@...gle.com, kernel-team@...roid.com
Subject: Re: [PATCH 2/4] dt-bindings: mfd: syscon: allow two reg regions for
gs101-pmu
On Fri, Dec 13, 2024 at 04:44:39PM +0000, Peter Griffin wrote:
> To avoid dtschema warnings allow google,gs101-pmu to have
> two reg regions.
It's not a "simple" syscon if you have 2 regions, so put it in its own
schema doc.
> Signed-off-by: Peter Griffin <peter.griffin@...aro.org>
> ---
> I don't really like this patch, but also didn't want to submit the series
> with a dtschema warning ;-)
>
> Possibly a better solution is when Robs patch
> `mfd: syscon: Allow syscon nodes without a "syscon" compatible` [1]
>
> gets updated with a v2, we could remove syscon compatible from
> gs101.dtsi (an ABI issue). If I understood his patch correctly,
> it would mean this yaml update would then no longer be required.
Whether you can tolerate an ABI issue is up to you.
Rob
Powered by blists - more mailing lists