From: Jules Maselbas <jmaselbas@kalray.eu>
To: barebox@lists.infradead.org
Cc: Jules Maselbas <jmaselbas@kalray.eu>
Subject: [PATCH 4/5] mtd: spi-nor: move SPI_NOR_MAX_ADDR_WIDTH define to spi-nor.h
Date: Mon, 17 Jul 2023 18:54:27 +0200 [thread overview]
Message-ID: <20230717165428.27286-4-jmaselbas@kalray.eu> (raw)
In-Reply-To: <20230717165428.27286-1-jmaselbas@kalray.eu>
Move the SPI_NOR_MAX_ADDR_WIDTH define into spi-nor.h to be used by
drivers.
Signed-off-by: Jules Maselbas <jmaselbas@kalray.eu>
---
drivers/mtd/spi-nor/spi-nor.c | 1 -
include/linux/mtd/spi-nor.h | 2 ++
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
index 968fd3ea7a..ab61e7824c 100644
--- a/drivers/mtd/spi-nor/spi-nor.c
+++ b/drivers/mtd/spi-nor/spi-nor.c
@@ -21,7 +21,6 @@
#include <of.h>
#define SPI_NOR_MAX_ID_LEN 6
-#define SPI_NOR_MAX_ADDR_WIDTH 4
/*
* For everything but full-chip erase; probably could be much smaller, but kept
diff --git a/include/linux/mtd/spi-nor.h b/include/linux/mtd/spi-nor.h
index fc7cefb55e..720b4888d4 100644
--- a/include/linux/mtd/spi-nor.h
+++ b/include/linux/mtd/spi-nor.h
@@ -142,6 +142,8 @@
SNOR_PROTO_ADDR(_addr_nbits) | \
SNOR_PROTO_DATA(_data_nbits))
+#define SPI_NOR_MAX_ADDR_WIDTH 4
+
enum spi_nor_protocol {
SNOR_PROTO_1_1_1 = SNOR_PROTO_STR(1, 1, 1),
SNOR_PROTO_1_1_2 = SNOR_PROTO_STR(1, 1, 2),
--
2.17.1
next prev parent reply other threads:[~2023-07-17 16:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 16:54 [PATCH 1/5] mtd: spi-nor: Add SPI_NOR_QUAD_WRITE hwcap Jules Maselbas
2023-07-17 16:54 ` [PATCH 2/5] mtd: spi-nor: enable {dual,quad}-read and quad-write for w25q256 Jules Maselbas
2023-07-17 16:54 ` [PATCH 3/5] mtd: spi-nor: enable quad-write for is25lp01g Jules Maselbas
2023-07-17 16:54 ` Jules Maselbas [this message]
2023-07-17 16:54 ` [PATCH 5/5] mtd: spi-nor: Add Synopsys DesignWare Octal SPI driver Jules Maselbas
2023-07-26 11:39 ` Sascha Hauer
2023-08-10 15:20 ` Jules Maselbas
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=20230717165428.27286-4-jmaselbas@kalray.eu \
--to=jmaselbas@kalray.eu \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox