[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35b87d1a-f290-4d41-91d1-fe089e5d8229@linaro.org>
Date: Thu, 14 Dec 2023 16:29:42 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Tomer Maimon <tmaimon77@...il.com>
Cc: arnd@...db.de, pmenzel@...gen.mpg.de, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
avifishman70@...il.com, tali.perry1@...il.com, joel@....id.au,
venture@...gle.com, yuenn@...gle.com, benjaminfair@...gle.com,
j.neuschaefer@....net, openbmc@...ts.ozlabs.org,
linux-gpio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/3] dt-bindings: soc: nuvoton: Add NPCM BPC
On 14/12/2023 14:34, Tomer Maimon wrote:
>>> +properties:
>>> + compatible:
>>> + items:
>>> + - enum:
>>> + - nuvoton,npcm845-bpc
>>> + - nuvoton,npcm750-bpc
>>> + - const: nuvoton,npcm-bpc
>>
>> That's not what I suggested. I asked to make 845 compatible with 750.
>> This works, but I want to be sure you really, really understand the
>> consequences of this.
> Did you mean to do the compatible as follows?
> properties:
> compatible:
> items:
> - enum:
> - nuvoton,npcm845-bpc
> - const: nuvoton,npcm750-bpc
>
> Appreciate it if you could explain what is the difference between the
> compatibility suggested in V3?
Your v3 says there is a generic, common to all current and future SoCs,
interface to BPC.
Best regards,
Krzysztof
Powered by blists - more mailing lists