[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc7bca02-5eb3-3b33-8911-a950b630f197@linaro.org>
Date: Wed, 3 Aug 2022 08:11:03 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Mark Brown <broonie@...nel.org>
Cc: Naga Sureshkumar Relli <nagasuresh.relli@...rochip.com>,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
conor.dooley@...rochip.com, linux-spi@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] spi: dt-binding: add Microchip CoreQSPI compatible
On 02/08/2022 15:13, Mark Brown wrote:
> On Tue, Aug 02, 2022 at 10:52:25AM +0200, Krzysztof Kozlowski wrote:
>> On 01/08/2022 11:42, Naga Sureshkumar Relli wrote:
>
>>> - enum:
>>> - - microchip,mpfs-spi
>>> - - microchip,mpfs-qspi
>>> + oneOf:
>>> + - description: Microchip's Polarfire SoC SPI controller.
>>> + const: microchip,mpfs-spi
>>> + - description: Microchip's Polarfire SoC QSPI controller.
>
>> Useless descriptions - they repeat compatible. Just keep it as enum and
>> skip descriptions. What value do they bring?
>
> Someone not familiar with the full Microchip product line might not be
> aware of the expansion of mpfs, it's not blindingly obvious.
Then it should be explained in title/description of the binding, not in
compatible. This is the usual way of providing some text description,
not for each compatible by repeating the compatible text.
Best regards,
Krzysztof
Powered by blists - more mailing lists