From: Conor Dooley <conor@kernel.org>
To: Robert Marko <robert.marko@sartura.hr>
Cc: nicolas.ferre@microchip.com, claudiu.beznea@tuxon.dev,
robh@kernel.org, krzk+dt@kernel.org, broonie@kernel.org,
alexandre.belloni@bootlin.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, daniel.machon@microchip.com,
luka.perkov@sartura.hr
Subject: Re: [PATCH 3/4] spi: atmel-quadspi: add LAN969x QSPI support
Date: Wed, 8 Jul 2026 18:02:38 +0100 [thread overview]
Message-ID: <20260708-guide-outing-b471d0dc92c9@spud> (raw)
In-Reply-To: <20260708165201.624271-3-robert.marko@sartura.hr>
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
On Wed, Jul 08, 2026 at 06:51:10PM +0200, Robert Marko wrote:
> Microchip LAN969x has two QSPI controllers based on SAMA7G5 QSPI.
>
> It requires pad calibration, supports DMA, and supports 100 MHz operation.
>
> Signed-off-by: Robert Marko <robert.marko@sartura.hr>
> @@ -1708,7 +1769,10 @@ static const struct of_device_id atmel_qspi_dt_ids[] = {
> .compatible = "microchip,sama7d65-qspi",
> .data = &atmel_sama7d65_qspi_caps,
> },
> -
> + {
> + .compatible = "microchip,lan9691-qspi",
Where is this compatible string documented?
> + .data = &atmel_lan969x_qspi_caps,
> + },
>
> { /* sentinel */ }
> };
> --
> 2.55.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-07-08 17:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 16:51 [PATCH 1/4] spi: atmel-quadspi: add controller init callback Robert Marko
2026-07-08 16:51 ` [PATCH 2/4] spi: atmel-quadspi: use init callback for gclk variants Robert Marko
2026-07-08 16:51 ` [PATCH 3/4] spi: atmel-quadspi: add LAN969x QSPI support Robert Marko
2026-07-08 17:02 ` Conor Dooley [this message]
2026-07-08 17:05 ` Robert Marko
2026-07-08 16:51 ` [PATCH 4/4] arm64: dts: microchip: lan969x: add QSPI nodes Robert Marko
2026-07-08 17:23 ` [PATCH 1/4] spi: atmel-quadspi: add controller init callback Mark Brown
2026-07-08 17:46 ` Robert Marko
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=20260708-guide-outing-b471d0dc92c9@spud \
--to=conor@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=broonie@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=daniel.machon@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luka.perkov@sartura.hr \
--cc=nicolas.ferre@microchip.com \
--cc=robert.marko@sartura.hr \
--cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.