public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: u-boot@emagii.com
To: u-boot@lists.denx.de
Cc: marex@denx.de, monstr@monstr.eu, sjg@chromium.org,
	Ulf Samuelsson <ulf@emagii.com>
Subject: [PATCH 1/4] include/mtd/mtd-abi.h: Add FPGA as MTD device
Date: Sat, 11 Feb 2023 11:07:40 +0100	[thread overview]
Message-ID: <20230211100743.12087-2-u-boot@emagii.com> (raw)
In-Reply-To: <20230211100743.12087-1-u-boot@emagii.com>

From: Ulf Samuelsson <ulf@emagii.com>

Signed-off-by: Ulf Samuelsson <ulf@emagii.com>
---
 include/mtd/mtd-abi.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/mtd/mtd-abi.h b/include/mtd/mtd-abi.h
index ea244fbaeb..cd826b64dd 100644
--- a/include/mtd/mtd-abi.h
+++ b/include/mtd/mtd-abi.h
@@ -89,6 +89,7 @@ struct mtd_write_req {
 #define MTD_DATAFLASH		6
 #define MTD_UBIVOLUME		7
 #define MTD_MLCNANDFLASH	8	/* MLC NAND (including TLC) */
+#define	MTD_FPGA		9
 
 #define MTD_WRITEABLE		0x400	/* Device is writeable */
 #define MTD_BIT_WRITEABLE	0x800	/* Single bits can be flipped */
@@ -100,6 +101,7 @@ struct mtd_write_req {
 #define MTD_CAP_RAM		(MTD_WRITEABLE | MTD_BIT_WRITEABLE | MTD_NO_ERASE)
 #define MTD_CAP_NORFLASH	(MTD_WRITEABLE | MTD_BIT_WRITEABLE)
 #define MTD_CAP_NANDFLASH	(MTD_WRITEABLE)
+#define MTD_CAP_FPGA		(MTD_WRITEABLE | MTD_NO_ERASE)
 
 /* Obsolete ECC byte placement modes (used with obsolete MEMGETOOBSEL) */
 #define MTD_NANDECC_OFF		0	// Switch off ECC (Not recommended)
-- 
2.17.1


  reply	other threads:[~2023-02-11 10:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 10:07 [PATCH 0/4] FPGAs as Memory Technology Devices in U-Boot u-boot
2023-02-11 10:07 ` u-boot [this message]
2023-02-11 10:07 ` [PATCH 2/4] cmd/mtd.c: Support FPGAs in mtd command u-boot
2023-02-11 10:07 ` [PATCH 3/4] mtd/fpga: add fpga directory to mtd (with Cyclone 10) u-boot
2023-02-12 19:31   ` Marek Vasut
2023-02-12 19:52     ` Ulf Samuelsson
2023-02-12 20:01       ` Marek Vasut
2023-02-12 22:07         ` Ulf Samuelsson
2023-02-12 22:40           ` Marek Vasut
2023-02-13  9:30             ` Ulf Samuelsson
2023-02-20 16:17               ` Marek Vasut
2023-02-20 21:29                 ` Ulf Samuelsson
2023-02-20 22:34                   ` Marek Vasut
2023-02-20 23:47                     ` Ulf Samuelsson
2023-02-21  1:13                       ` Marek Vasut
2023-02-21  9:08                         ` Michael Walle
2023-02-21 10:42                           ` Ulf Samuelsson
2023-02-21 11:19                             ` Michael Walle
2023-02-21 11:20                               ` Michael Walle
2023-02-21 15:37                               ` Ulf Samuelsson
2023-02-21 16:01                                 ` Michael Walle
2023-02-21 10:58                           ` Ulf Samuelsson
2023-02-22 19:51                             ` Steffen Dirkwinkel
2023-02-23  8:28                               ` Ulf Samuelsson
2023-02-23  8:51                                 ` Steffen Dirkwinkel
2023-02-23  8:51                                   ` Steffen Dirkwinkel
2023-02-21 11:54                         ` Ulf Samuelsson
2023-02-11 10:07 ` [PATCH 4/4] mtd/Kconfig,Makefile support FPGA u-boot

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=20230211100743.12087-2-u-boot@emagii.com \
    --to=u-boot@emagii.com \
    --cc=marex@denx.de \
    --cc=monstr@monstr.eu \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=ulf@emagii.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