On 4/7/22 13:54, Kavyasree Kotagiri wrote:
> 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?
Cheers,
ta
>
> Signed-off-by: Kavyasree Kotagiri <[email protected]>
> ---
> 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:
> > 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 <[email protected]>
> > ---
> > 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:
> > > 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.
Are you sure? There is a max frequency property in Tudor's sama7g5-qspi
driver (200/133MHz) which doesn't match neither the LAN9668 manual (which
states 150MHz on QSPI0 and 100MHZ on QSPI1, funny enough there is no
mention of QSPI2) nor does it match the max frequency set in the downstream
linux driver (24 MHz).
-michael