[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <eae501a6-d210-4576-afa0-010f9cc8c5fd@prolan.hu>
Date: Mon, 21 Oct 2024 14:19:21 +0200
From: Csókás Bence <csokas.bence@...lan.hu>
To: Tudor Ambarus <tudor.ambarus@...rochip.com>, <broonie@...nel.org>
CC: <nicolas.ferre@...rochip.com>, <alexandre.belloni@...tlin.com>,
<ludovic.desroches@...rochip.com>, <linux-spi@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
Varshini Rajendran <varshini.rajendran@...rochip.com>, Claudiu Beznea
<Claudiu.Beznea@...rochip.com>
Subject: Re: [PATCH] spi: atmel-quadspi: Add support for sama7g5 QSPI
Hi,
On 2021. 12. 14. 14:34, Tudor Ambarus wrote:
> The sama7g5 QSPI controller uses dedicated clocks for the
> QSPI Controller Interface and the QSPI Controller Core, and
> requires synchronization before accessing registers or bit
> fields.
>
> QSPI_SR.SYNCBSY must be zero before accessing any of the bits:
> QSPI_CR.QSPIEN, QSPI_CR.QSPIDIS, QSPI_CR.SRFRSH, QSPI_CR.SWRST,
> QSPI_CR.UPDCFG, QSPI_CR.STTFR, QSPI_CR.RTOUT, QSPI_CR.LASTXFER.
>
> Also, the QSPI controller core configuration can be updated by
> writing the QSPI_CR.UPDCFG bit to ‘1’. This is needed by the
> following registers: QSPI_MR, QSPI_SCR, QSPI_IAR, QSPI_WICR,
> QSPI_IFR, QSPI_RICR, QSPI_SMR, QSPI_SKR,QSPI_REFRESH, QSPI_WRACNT
> QSPI_PCALCFG.
>
> The Octal SPI supports frequencies up to 200 MHZ DDR. The need
> for output impedance calibration arises. To avoid the degradation
> of the signal quality, a PAD calibration cell is used to adjust
> the output impedance to the driven I/Os.
>
> The transmission flow requires different sequences for setting
> the configuration and for the actual transfer, than what is in
> the sama5d2 and sam9x60 versions of the IP. Different interrupts
> are handled. aq->ops->set_cfg() and aq->ops->transfer() are
> introduced to help differentiating the flows.
>
> Tested single and octal SPI mode with mx66lm1g45g.
>
> Signed-off-by: Tudor Ambarus <tudor.ambarus@...rochip.com>
This patch doesn't seem to have been merged. Is it no longer needed? Has
Claudiu's comment been addressed? Likely not, as the vendor kernel
(linux4microchip) still contains the un-amended commit.
Bence
Powered by blists - more mailing lists