[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f323f1bc-1d91-f8bb-2c1f-2f1b93fe1b3e@linaro.org>
Date: Mon, 20 Mar 2023 19:11:01 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Arınç ÜNAL <arinc.unal@...nc9.com>,
Sergio Paracuellos <sergio.paracuellos@...il.com>,
linux-clk@...r.kernel.org
Cc: 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 20/03/2023 19:07, Arınç ÜNAL wrote:
> On 20.03.2023 21:01, Krzysztof Kozlowski wrote:
>> On 20/03/2023 17:18, Sergio Paracuellos wrote:
>>> +properties:
>>> + compatible:
>>> + items:
>>> + - enum:
>>> + - ralink,rt2880-sysc
>>> + - ralink,rt3050-sysc
>>> + - ralink,rt3052-sysc
>>> + - ralink,rt3352-sysc
>>> + - ralink,rt3883-sysc
>>> + - ralink,rt5350-sysc
>>> + - ralink,mt7620-sysc
>>> + - ralink,mt7620a-sysc
>>> + - ralink,mt7628-sysc
>>> + - ralink,mt7688-sysc
>>
>> One more comment - this and maybe other compatibles - have wrong vendor
>> prefix. This is mediatek, not ralink.
>
> This platform was acquired from Ralink by MediaTek. I couldn't change
> some existing ralink compatible strings to mediatek as Rob explained on
> my pinctrl patch series that we don't do that. The compatible strings on
> this patch series here are new but I'd rather keep the compatible
> strings ralink to keep things consistent.
The comment that you cannot change existing compatibles does not apply
to these, because these are new. However indeed some SoCs have already
compatibles with ralink, so it's fine for these. mt7620 and mt7628 are
already used with mediatek, so these should be rather corrected to new
prefix.
Best regards,
Krzysztof
Powered by blists - more mailing lists