linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: Mark Brown <broonie@kernel.org>
Cc: Nicolas Ferre <nicolas.ferre@microchip.com>,
	linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] spi: atmel-quadspi: Fix and add full CS delay support
Date: Wed, 18 Sep 2024 10:27:42 +0200	[thread overview]
Message-ID: <20240918082744.379610-1-ada@thorsis.com> (raw)

Hello everyone,

when testing on a SAM9X60 based board with an FPGA implementing a custom
SPI-MEM protocol, we found the need to fully control the delay settings
the atmel/microchip QSPI controller offers.

Greets
Alex

(series based on v6.11, tested on top of v6.6.44)

Cc: linux-spi@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org

Alexander Dahl (2):
  spi: atmel-quadspi: Avoid overwriting delay register settings
  spi: atmel-quadspi: Add cs_hold and cs_inactive setting support

 drivers/spi/atmel-quadspi.c | 50 +++++++++++++++++++++++++++++--------
 1 file changed, 40 insertions(+), 10 deletions(-)


base-commit: 98f7e32f20d28ec452afb208f9cffc08448a2652
-- 
2.39.5


             reply	other threads:[~2024-09-18  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  8:27 Alexander Dahl [this message]
2024-09-18  8:27 ` [PATCH 1/2] spi: atmel-quadspi: Avoid overwriting delay register settings Alexander Dahl
2024-09-20  8:22   ` Mark Brown
2024-09-20  8:53     ` Alexander Dahl
2024-09-26  7:25   ` Alexander Dahl
2024-09-26  7:45     ` Mark Brown
2024-09-18  8:27 ` [PATCH 2/2] spi: atmel-quadspi: Add cs_hold and cs_inactive setting support Alexander Dahl
2024-09-20 11:20 ` (subset) [PATCH 0/2] spi: atmel-quadspi: Fix and add full CS delay support Mark Brown
2024-09-30 21:42 ` Mark Brown

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=20240918082744.379610-1-ada@thorsis.com \
    --to=ada@thorsis.com \
    --cc=broonie@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).