[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CO1PR11MB48654DEFB31E8F8AB00C180292E99@CO1PR11MB4865.namprd11.prod.outlook.com>
Date: Fri, 8 Apr 2022 11:52:36 +0000
From: <Kavyasree.Kotagiri@...rochip.com>
To: <Tudor.Ambarus@...rochip.com>, <broonie@...nel.org>,
<robh+dt@...nel.org>, <krzk+dt@...nel.org>
CC: <Nicolas.Ferre@...rochip.com>, <alexandre.belloni@...tlin.com>,
<Claudiu.Beznea@...rochip.com>, <linux-spi@...r.kernel.org>,
<devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <UNGLinuxDriver@...rochip.com>,
<Manohar.Puri@...rochip.com>
Subject: [PATCH] spi: atmel,quadspi: Define lan966x QSPI
> > LAN966x SoC supports 3 QSPI controllers. Each of them support
> > data and clock frequency upto 100Mhz DDR and QUAD protocol.
>
> How is this IP different than microchip,sama7g5-qspi? Does this speed
> limitation come from the IP itself or from the board that you're using?
>
> Neither of these instances support octal mode?
>
Thanks for your comments. All the three instances support only QUAD protocol.
You are correct. There is no difference from sama7g5-qspi. Please ignore this patch. I will send next version of dt patches where I will use "microchip,sama7g5-qspi" for all my qspi nodes.
> Cheers,
> ta
>
> >
> > Signed-off-by: Kavyasree Kotagiri <kavyasree.kotagiri@...rochip.com>
> > ---
> > Documentation/devicetree/bindings/spi/atmel,quadspi.yaml | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/Documentation/devicetree/bindings/spi/atmel,quadspi.yaml
> b/Documentation/devicetree/bindings/spi/atmel,quadspi.yaml
> > index 1d493add4053..100d6e7f2748 100644
> > --- a/Documentation/devicetree/bindings/spi/atmel,quadspi.yaml
> > +++ b/Documentation/devicetree/bindings/spi/atmel,quadspi.yaml
> > @@ -19,6 +19,7 @@ properties:
> > - microchip,sam9x60-qspi
> > - microchip,sama7g5-qspi
> > - microchip,sama7g5-ospi
> > + - microchip,lan966x-qspi
> >
> > reg:
> > items:
Powered by blists - more mailing lists