[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e36da496-04f3-4f00-aab1-f52aa0c1450f@linaro.org>
Date: Mon, 9 Dec 2024 08:19:34 +0000
From: Tudor Ambarus <tudor.ambarus@...aro.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
alim.akhtar@...sung.com, linux-kernel@...r.kernel.org,
linux-samsung-soc@...r.kernel.org, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, andre.draszik@...aro.org,
kernel-team@...roid.com, willmcvicker@...gle.com, peter.griffin@...aro.org,
javierm@...hat.com, tzimmermann@...e.de, daniel.lezcano@...aro.org,
vincent.guittot@...aro.org, ulf.hansson@...aro.org, arnd@...db.de
Subject: Re: [PATCH v3 1/3] dt-bindings: firmware: add samsung,exynos-acpm-ipc
bindings
On 12/9/24 8:03 AM, Krzysztof Kozlowski wrote:
>> + initdata-base:
>> + $ref: /schemas/types.yaml#/definitions/uint32
>> + description:
>> + Base address of the configuration data in the shared memory.
> If you really need this, then it should be rather encoded as part of
> shemm phandle (phandle-array with describing items, just like syscon
> phandles are done).
>
> But OTOH, I don't see why this is needed at all so far - compatible
> defines it.
Indeed, I shall move it to compatible. If firmware ever changes, and
uses a different offset to the configuration data, then I can introduce
a new compatible.
I agree with all the other comments as well, will address them in v4.
Thanks!
ta
Powered by blists - more mailing lists