From: naga sureshkumar <nagasuresh12@gmail.com>
To: Conor.Dooley@microchip.com
Cc: Nagasuresh.Relli@microchip.com, broonie@kernel.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
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: Mon, 1 Aug 2022 16:22:16 +0530 [thread overview]
Message-ID: <CAH_iE_03fHMbCwGPsE_CmbokRh5cW_bEaX8RodK1ovWeTSHuhQ@mail.gmail.com> (raw)
In-Reply-To: <a431ac00-ee65-df7a-674c-27f13fc7be82@microchip.com>
Hi Conor,
Thanks for your review.
On Mon, Aug 1, 2022 at 3:54 PM <Conor.Dooley@microchip.com> wrote:
>
> Hey Suresh,
>
> On 01/08/2022 10:42, Naga Sureshkumar Relli wrote:
> > Add compatible string for Microchip CoreQSPI controller.
> >
> > Signed-off-by: Naga Sureshkumar Relli <nagasuresh.relli@microchip.com>
> > ---
> > .../devicetree/bindings/spi/microchip,mpfs-spi.yaml | 10 +++++++---
> > 1 file changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml b/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> > index 7326c0a28d16..b65f4e070796 100644
> > --- a/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> > +++ b/Documentation/devicetree/bindings/spi/microchip,mpfs-spi.yaml
> > @@ -14,9 +14,13 @@ allOf:
> >
> > properties:
> > compatible:
> > - enum:
> > - - microchip,mpfs-spi
> > - - microchip,mpfs-qspi
> > + oneOf:
> > + - description: Microchip's Polarfire SoC SPI controller.
> ^
> (This is a capital F btw)
>
> > + const: microchip,mpfs-spi
> > + - description: Microchip's Polarfire SoC QSPI controller.
> > + const: microchip,mpfs-qspi
> > + - description: Microchip's FPGA QSPI controller.
> > + const: microchip,coreqspi-rtl-v2
>
> I am not sure that this is the correct "hierarchy". coreQSPI has a
> subset of the registers of the "hard" QSPI & the same driver works
> for both at the moment. The "hard" QSPI is based on the FPGA core,
> so I think this should be changed to something like the following:
I have added each element for each controller separately.
but the below one hierarchy explains clearly about the cores.
I will update the bindings.
>
> properties:
> compatible:
> oneOf:
> - description: Microchip's PolarFire SoC QSPI controller
> items:
> - const: microchip,mpfs-qspi
> - const: microchip,coreqspi-rtl-v2
> - description: Microchip's fabric based QSPI IP core
> const: microchip,coreqspi-rtl-v2
> - description: Microchip's PolarFire SoC SPI controller
> const: microchip,mpfs-spi
>
> Unrelated to this patch, but a
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index f4202a19faa1..887bfee5c7af 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17526,6 +17526,7 @@ F: drivers/pci/controller/pcie-microchip-host.c
> F: drivers/rtc/rtc-mpfs.c
> F: drivers/soc/microchip/
> F: drivers/spi/spi-microchip-core.c
> +F: drivers/spi/spi-microchip-core-qspi.c
> F: drivers/usb/musb/mpfs.c
> F: include/soc/microchip/mpfs.h
>
> Would be nice too.
Ok.
Thanks,
Naga Sureshkumar Relli.
>
> Thanks,
> Conor.
next prev parent reply other threads:[~2022-08-01 10:52 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 [this message]
2022-08-02 8:52 ` Krzysztof Kozlowski
2022-08-02 13:13 ` Mark Brown
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=CAH_iE_03fHMbCwGPsE_CmbokRh5cW_bEaX8RodK1ovWeTSHuhQ@mail.gmail.com \
--to=nagasuresh12@gmail.com \
--cc=Conor.Dooley@microchip.com \
--cc=Nagasuresh.Relli@microchip.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--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).