linux-kernel - Re: [PATCH] spi: atmel,quadspi: Define lan966x QSPI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Mon, 11 Apr 2022 16:46:19 +0200
From:   Michael Walle <michael@...le.cc>
To:     kavyasree.kotagiri@...rochip.com
Cc:     Claudiu.Beznea@...rochip.com, Manohar.Puri@...rochip.com,
        Nicolas.Ferre@...rochip.com, Tudor.Ambarus@...rochip.com,
        UNGLinuxDriver@...rochip.com, alexandre.belloni@...tlin.com,
        broonie@...nel.org, devicetree@...r.kernel.org, krzk+dt@...nel.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org, robh+dt@...nel.org,
        Michael Walle <michael@...le.cc>
Subject: Re: [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.

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