[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1cfc1e0a-1dcf-4e3b-b0ff-0a1a6860997b@kernel.org>
Date: Mon, 6 Jan 2025 08:28:45 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Ivaylo Ivanov <ivo.ivanov.ivanov1@...il.com>
Cc: Rob Herring <robh@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Alim Akhtar <alim.akhtar@...sung.com>,
Sam Protsenko <semen.protsenko@...aro.org>,
Peter Griffin <peter.griffin@...aro.org>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-samsung-soc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: soc: samsung: usi: replace USI_V2 in
constants with USI_MODE
On 06/01/2025 08:09, Ivaylo Ivanov wrote:
>>>
>>> -#define USI_V2_NONE 0
>>> -#define USI_V2_UART 1
>>> -#define USI_V2_SPI 2
>>> -#define USI_V2_I2C 3
>>> +#define USI_MODE_NONE 0
>>> +#define USI_MODE_UART 1
>>> +#define USI_MODE_SPI 2
>>> +#define USI_MODE_I2C 3
>> This breaks ABI and does not build. You still need also:
>> #define USI_V2_NONE USI_MODE_NONE
>> and same for the rest.
>
> Alright, sounds good to me. That way I shouldn't s/USI_V2/USI_MODE/g
> for the other SoC device trees, right? Should I also mention with a
You can change them as well, because USI_MODE_XXX will be preferred from
now on. The DTS commit will just wait one cycle till bindings get accepted.
> comment that the V2 constants are deprecated?
Yes, this would be good.
Thanks for working on this.
Best regards,
Krzysztof
Powered by blists - more mailing lists