From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Naga Sureshkumar Relli <nagasuresh.relli@microchip.com>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor.dooley@microchip.com, linux-spi@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] spi: dt-binding: add Microchip CoreQSPI compatible
Date: Tue, 2 Aug 2022 14:13:02 +0100 [thread overview]
Message-ID: <Yuki3jpCSJDdXcWA@sirena.org.uk> (raw)
In-Reply-To: <6d36b192-9e63-ec13-5583-22b81c99c18b@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 650 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-08-02 13:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 9:42 [PATCH 0/2] Add support for Microchip QSPI controller Naga Sureshkumar Relli
2022-08-01 9:42 ` [PATCH 1/2] spi: dt-binding: add Microchip CoreQSPI compatible Naga Sureshkumar Relli
2022-08-01 10:17 ` Conor.Dooley
2022-08-01 10:52 ` naga sureshkumar
2022-08-02 8:52 ` Krzysztof Kozlowski
2022-08-02 13:13 ` Mark Brown [this message]
2022-08-03 6:11 ` Krzysztof Kozlowski
2022-08-03 6:59 ` naga sureshkumar
2022-08-03 7:48 ` Krzysztof Kozlowski
2022-08-03 13:29 ` Mark Brown
2022-08-04 11:31 ` Krzysztof Kozlowski
2022-08-04 11:35 ` Krzysztof Kozlowski
2022-08-04 12:13 ` Mark Brown
2022-08-01 9:42 ` [PATCH 2/2] spi: microchip-core-qspi: Add support for microchip fpga qspi controllers Naga Sureshkumar Relli
2022-08-01 10:40 ` Conor.Dooley
2022-08-01 11:09 ` naga sureshkumar
2022-08-01 12:33 ` Mark Brown
2022-08-01 12:56 ` Conor.Dooley
2022-08-02 8:54 ` Krzysztof Kozlowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yuki3jpCSJDdXcWA@sirena.org.uk \
--to=broonie@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nagasuresh.relli@microchip.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).