[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87tsvvf58k.fsf@bootlin.com>
Date: Thu, 05 Feb 2026 18:51:55 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Santhosh Kumar K <s-k6@...com>
Cc: <broonie@...nel.org>, <robh@...nel.org>, <krzk+dt@...nel.org>,
<conor+dt@...nel.org>, <richard@....at>, <vigneshr@...com>,
<tudor.ambarus@...aro.org>, <pratyush@...nel.org>, <mwalle@...nel.org>,
<linux-spi@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-mtd@...ts.infradead.org>,
<praneeth@...com>, <u-kumar1@...com>, <p-mantena@...com>,
<a-dutta@...com>
Subject: Re: [RFC PATCH v2 12/12] spi: cadence-quadspi: enable PHY for
direct reads and writes
On 13/01/2026 at 19:46:17 +0530, Santhosh Kumar K <s-k6@...com> wrote:
> Enable PHY mode for direct memory-mapped reads and large indirect writes
> (>= 1KB) to leverage calibrated RX/TX timing delays for high-frequency
> operations.
Is enabling the calibration so impacting? Did you measure it? Isn't
skipping any non read or non write operations enough? Status reads for
example should have a smaller op->max_freq based on my previous comment,
so in theory I do not see when we will meet these cases.
Fine for the other conditions.
Miquèl
Powered by blists - more mailing lists