linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dhruva Gole <d-gole@ti.com>
To: <broonie@kernel.org>
Cc: Dhruva Gole <d-gole@ti.com>, <linux-spi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, Vignesh <vigneshr@ti.com>,
	Pratyush Yadav <pratyush@kernel.org>,
	Vaishnav Achath <vaishnav.a@ti.com>
Subject: [PATCH 0/2] spi: cqspi: Fix register reads in STIG Mode
Date: Wed, 4 Jan 2023 11:56:02 +0530	[thread overview]
Message-ID: <20230104062604.1556763-1-d-gole@ti.com> (raw)

Intent of these patches is to fix register reads in STIG mode and also
use STIG mode while reading flash registers.
Currently if you try to read a register while in STIG mode there is no
support for ADDR and thus naturally a register never gets read from the
flash.

Logs demonstrating the usage and working of QSPI-NOR Flash (Cypress
s25hs512t) on a modified AM625 SK EVM can be found on the link below:
https://gist.github.com/DhruvaG2000/a9b90d3d9c60edd3b2d8a360d869a00b

A series very similar to this was also sent to u-boot and the latest
revision can be viewed here:
[PATCH V4 0/2] spi: cqspi: Fix register reads in STIG Mode
https://lore.kernel.org/u-boot/20230103063112.1165898-1-d-gole@ti.com/


Dhruva Gole (2):
  spi: cadence-quadspi: setup ADDR Bits in cmd reads
  spi: cadence-quadspi: use STIG mode for small reads

 drivers/spi/spi-cadence-quadspi.c | 19 ++++++++++++++++++-
 1 file changed, 18 insertions(+), 1 deletion(-)

-- 
2.25.1


             reply	other threads:[~2023-01-04  6:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04  6:26 Dhruva Gole [this message]
2023-01-04  6:26 ` [PATCH 1/2] spi: cadence-quadspi: setup ADDR Bits in cmd reads Dhruva Gole
2023-01-04  6:26 ` [PATCH 2/2] spi: cadence-quadspi: use STIG mode for small reads Dhruva Gole
2023-01-10  5:10   ` Vaishnav Achath

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=20230104062604.1556763-1-d-gole@ti.com \
    --to=d-gole@ti.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=pratyush@kernel.org \
    --cc=vaishnav.a@ti.com \
    --cc=vigneshr@ti.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).