[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ed317bc-ce3a-2da2-1d96-f0ea8ff0b48c@arinc9.com>
Date: Tue, 21 Mar 2023 12:02:47 +0300
From: Arınç ÜNAL <arinc.unal@...nc9.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Sergio Paracuellos <sergio.paracuellos@...il.com>
Cc: linux-clk@...r.kernel.org, linux-mips@...r.kernel.org,
tsbogend@...ha.franken.de, john@...ozen.org,
linux-kernel@...r.kernel.org, p.zabel@...gutronix.de,
mturquette@...libre.com, sboyd@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org, matthias.bgg@...il.com,
devicetree@...r.kernel.org
Subject: Re: [PATCH 01/10] dt: bindings: clock: add mtmips SoCs clock device
tree binding documentation
On 21.03.2023 12:01, Krzysztof Kozlowski wrote:
> On 21/03/2023 09:53, Arınç ÜNAL wrote:
>>>
>>> I do not see how choosing one variant for compatibles having two
>>> variants of prefixes, complicates things. Following this argument
>>> choosing "ralink" also complicates!
>>
>> The idea is to make every compatible string of MTMIPS to have the ralink
>> prefix so it's not mediatek on some schemas and ralink on others. Simpler.
>
> Which is an ABI break, so you cannot do it.
No, both strings stay on the driver, it's the schemas that will only
keep ralink.
Arınç
Powered by blists - more mailing lists