From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Vlim <vlim@gigadevice.com>, Michael Walle <michael@walle.cc>
Cc: "pratyush@kernel.org" <pratyush@kernel.org>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"richard@nod.at" <richard@nod.at>,
"vigneshr@ti.com" <vigneshr@ti.com>,
"akumarma@amd.com" <akumarma@amd.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"vikhyat.goyal@amd.com" <vikhyat.goyal@amd.com>
Subject: Re: [PATCH V1 1/1] linux: drivers: mtd: spi-nor: gigadevice.c
Date: Fri, 21 Jul 2023 09:06:00 +0300 [thread overview]
Message-ID: <55d60aec-3b20-d9d3-aeb2-77abbcc47d16@linaro.org> (raw)
In-Reply-To: <TY0PR06MB56580D3FEE55389F41E33398BB3EA@TY0PR06MB5658.apcprd06.prod.outlook.com>
On 21.07.2023 00:48, Vlim wrote:
> Hi, Michael,
>
> Our parts do support SFDP.
> Can you provide the guideline for the part definition?
There's none at the moment, you have to read the code.
> I do see these samples in the gigadevice.c file; but, not sure of the
> purpose of each parameter.
The flags are defined in drivers/mtd/spi-nor/core.h. Start from there.
>
All the flashes that you proposed, but one probably (gd25lx256e) can be
probed using the generic spi-nor driver, thus you won't need to add
dedicated flash entries. See:
773bbe104497 mtd: spi-nor: add generic flash driver
Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2023-07-21 6:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 4:28 [PATCH V1 1/1] linux: drivers: mtd: spi-nor: gigadevice.c Victor Lim
2023-07-20 6:25 ` kernel test robot
2023-07-20 6:53 ` Tudor Ambarus
2023-07-20 7:05 ` Michael Walle
[not found] ` <TY0PR06MB56580D3FEE55389F41E33398BB3EA@TY0PR06MB5658.apcprd06.prod.outlook.com>
2023-07-21 6:06 ` Tudor Ambarus [this message]
[not found] ` <TY0PR06MB56581B9A28DCD7A7270CFC0ABB3FA@TY0PR06MB5658.apcprd06.prod.outlook.com>
2023-07-21 7:38 ` Tudor Ambarus
2023-07-21 7:41 ` Michael Walle
2023-07-21 7:42 ` Tudor Ambarus
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=55d60aec-3b20-d9d3-aeb2-77abbcc47d16@linaro.org \
--to=tudor.ambarus@linaro.org \
--cc=akumarma@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=miquel.raynal@bootlin.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=vigneshr@ti.com \
--cc=vikhyat.goyal@amd.com \
--cc=vlim@gigadevice.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).