From: Clus Tom <ssunkkan@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: miquel.raynal@bootlin.com, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, pratyush@kernel.org,
richard@nod.at, tudor.ambarus@linaro.org, vigneshr@ti.com
Subject: Re: [PATCH] Add support for more XMC series
Date: Fri, 18 Aug 2023 01:17:06 +0800 [thread overview]
Message-ID: <2F4A4D23-1C71-42B9-8B2C-06496F773BDA@gmail.com> (raw)
In-Reply-To: <abd705350b650717dbbc187815d384e7@walle.cc>
Yes, I'm using the latest kernel.
> 在 2023年8月18日，01:10，Michael Walle <michael@walle.cc> 写道：
>
> Hi,
>
>>> XMC parts seem to have SFDP tables and they should work out of the box
>>> without any patches with the generic spi nor driver [1]. Therefore,
>>> you don't need any entry at all.
>> I think it is related to the PARSE_SFDP flag.
>> The XMC flash part supports SFDP, so i don’t needto add
>> NO_SFDP_FLAGS() macro.
>
> Correct. If the flash is working with PARSE_SFDP, it has SFDP and
> all the information of the flash_info table is pulled from the SFDP
> tables, except for the part name. Therefore, you don't need any entry
> at all. The flash should just work out of the box. Are you using the
> latest kernel?
>
> -michael
next prev parent reply other threads:[~2023-08-17 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 12:46 SSunk
2023-08-17 13:14 ` Michael Walle
2023-08-17 13:20 ` Miquel Raynal
2023-08-17 17:03 ` SSunk
2023-08-17 17:10 ` Michael Walle
2023-08-17 17:17 ` Clus Tom [this message]
2023-08-29 4:56 ` SSunk
2023-08-29 6:48 ` Michael Walle
2023-08-31 4:13 ` SSunk
2023-08-31 6:41 ` Michael Walle
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=2F4A4D23-1C71-42B9-8B2C-06496F773BDA@gmail.com \
--to=ssunkkan@gmail.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=tudor.ambarus@linaro.org \
--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®