From: Tudor Ambarus <tudor.ambarus@linaro.org>
To: Michael Walle <michael@walle.cc>,
Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Luke He <sixuerain@gmail.com>,
pratyush@kernel.org, richard@nod.at, vigneshr@ti.com,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: spi-nor: Add support for XMC XM25QH256C / XM25QU256C / XM25QH512C / XM25QU512C site: https://www.xmcwh.com/site/product#
Date: Mon, 13 Mar 2023 11:23:13 +0000 [thread overview]
Message-ID: <939c029f-6679-b364-531c-bf0193135ffd@linaro.org> (raw)
In-Reply-To: <17d46633869f64e029e065693e341e3b@walle.cc>
On 3/13/23 10:39, Michael Walle wrote:
> Am 2023-03-13 11:33, schrieb Miquel Raynal:
>> Hi Michael,
>>
>> michael@walle.cc wrote on Mon, 13 Mar 2023 11:08:15 +0100:
>>
>>> Hi,
>>>
>>> please have a look at Documentation/process/submitting-patches.rst
>>> how to properly format patches. But also see below.
>>>
>>> Am 2023-03-13 11:01, schrieb Luke He:
>>> > Signed-off-by: Luke He <sixuerain@gmail.com>
>>> > ---
>>> > drivers/mtd/spi-nor/xmc.c | 12 ++++++++++++
>>> > 1 file changed, 12 insertions(+)
>>> >
>>> > diff --git a/drivers/mtd/spi-nor/xmc.c b/drivers/mtd/spi-nor/xmc.c
>>> > index 051411e86339..6db01b80237f 100644
>>> > --- a/drivers/mtd/spi-nor/xmc.c
>>> > +++ b/drivers/mtd/spi-nor/xmc.c
>>> > @@ -16,6 +16,18 @@ static const struct flash_info xmc_nor_parts[] = {
>>> > { "XM25QH128A", INFO(0x207018, 0, 64 * 1024, 256)
>>> > NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
>>> > SPI_NOR_QUAD_READ) },
>>> > + { "XM25QH256C", INFO(0x204019, 0, 64 * 1024, 512)
>>> > + NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
>>> > + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
>>> > + { "XM25QU256C", INFO(0x204119, 0, 64 * 1024, 512)
>>> > + NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
>>> > + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
>>> > + { "XM25QH512C", INFO(0x204020, 0, 64 * 1024, 1024)
>>> > + NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
>>> > + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) },
>>> > + { "XM25QU512C", INFO(0x204120, 0, 64 * 1024, 1024)
>>> > + NO_SFDP_FLAGS(SECT_4K | SPI_NOR_DUAL_READ |
>>> > + SPI_NOR_QUAD_READ | SPI_NOR_4B_OPCODES) }
>>>
>>> I've just looked at XM25QH256C [1], but I suspect all of these
>>> flashes supports SFDP, therefore you shouldn't use the NO_SFDP_FLAGS.
>>
>> I didn't check, do we have a kdoc or something like that which explains
>> what flags to use and when?
>
> https://elixir.bootlin.com/linux/v6.3-rc2/source/drivers/mtd/spi-nor/core.h#L429
>
> What's missing is still some overview document when and how to add a new
> entry to our database. /me looks in Tudors direction :)
>
Right, the code comments should help. I've been planning to do the
documentation, even started it few months ago, but I'm still behind with
some patch reviews, including Miquel's, so the documentation has to
wait. I'm doing this in my spare time, so I'll stop giving estimates.
Cheers,
ta
prev parent reply other threads:[~2023-03-13 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 10:01 Luke He
2023-03-13 10:08 ` Michael Walle
2023-03-13 10:33 ` Miquel Raynal
2023-03-13 10:39 ` Michael Walle
2023-03-13 11:23 ` Tudor Ambarus [this message]
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=939c029f-6679-b364-531c-bf0193135ffd@linaro.org \
--to=tudor.ambarus@linaro.org \
--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=sixuerain@gmail.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
all inboxes | Powered by JetHome®