From: Bin Meng <bmeng.cn@gmail.com>
To: Stefan Roese <sr@denx.de>, u-boot@lists.denx.de
Subject: [PATCH 2/3] flash.h: Remove CONFIG_SYS_FLASH_CFI from flash_info_t
Date: Sat, 7 Aug 2021 13:00:01 +0800 [thread overview]
Message-ID: <20210807050002.32723-2-bmeng.cn@gmail.com> (raw)
In-Reply-To: <20210807050002.32723-1-bmeng.cn@gmail.com>
Those embers wrapped with CONFIG_SYS_FLASH_CFI in struct flash_info_t
are unconditionally used in the cfi_flash.c driver.
Drop the #ifdefs in the definition of flash_info_t.
Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
---
include/flash.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/include/flash.h b/include/flash.h
index 42b18a6047..f3959f5012 100644
--- a/include/flash.h
+++ b/include/flash.h
@@ -21,7 +21,6 @@ typedef struct {
ulong flash_id; /* combined device & manufacturer code */
ulong start[CONFIG_SYS_MAX_FLASH_SECT]; /* virtual sector start address */
uchar protect[CONFIG_SYS_MAX_FLASH_SECT]; /* sector protection status */
-#ifdef CONFIG_SYS_FLASH_CFI
uchar portwidth; /* the width of the port */
uchar chipwidth; /* the width of the chip */
uchar chip_lsb; /* extra Least Significant Bit in the */
@@ -45,7 +44,6 @@ typedef struct {
ulong addr_unlock2; /* unlock address 2 for AMD flash roms */
uchar sr_supported; /* status register supported */
const char *name; /* human-readable name */
-#endif
#ifdef CONFIG_DM_MTD
struct mtd_info *mtd;
#endif
--
2.25.1
next prev parent reply other threads:[~2021-08-07 5:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 5:00 [PATCH 1/3] mtd: kconfig: Fix CFI_FLASH dependency Bin Meng
2021-08-07 5:00 ` Bin Meng [this message]
2021-08-11 8:34 ` [PATCH 2/3] flash.h: Remove CONFIG_SYS_FLASH_CFI from flash_info_t Stefan Roese
2021-08-11 10:45 ` Stefan Roese
2021-08-07 5:00 ` [PATCH 3/3] riscv: qemu: Enable MTD NOR flash support Bin Meng
2021-08-11 8:34 ` Stefan Roese
2021-08-11 10:45 ` Stefan Roese
2021-08-11 8:33 ` [PATCH 1/3] mtd: kconfig: Fix CFI_FLASH dependency Stefan Roese
2021-08-11 10:44 ` Stefan Roese
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=20210807050002.32723-2-bmeng.cn@gmail.com \
--to=bmeng.cn@gmail.com \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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