From: Michael Walle <michael@walle.cc>
To: Jae Hyun Yoo <quic_jaehyoo@quicinc.com>
Cc: clg@kaod.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org, p.yadav@ti.com,
quic_ggregory@quicinc.com, quic_jiles@quicinc.com,
tudor.ambarus@microchip.com
Subject: Re: [PATCH] mtd: spi-nor: winbond: add support for W25Q512NW-IQ/IN
Date: Thu, 14 Jul 2022 09:41:55 +0200 [thread overview]
Message-ID: <00f0c9d480ef5a414f1c34492661bd9e@walle.cc> (raw)
In-Reply-To: <2260955b-354d-ceda-cadc-49453bfca3e4@quicinc.com>
Hi,
Am 2022-07-13 23:01, schrieb Jae Hyun Yoo:
> On 7/13/2022 7:32 AM, Michael Walle wrote:
>> Am 2022-07-13 16:26, schrieb Jae Hyun Yoo:
>>>>> + { "w25q512nwq", INFO(0xef6020, 0, 64 * 1024, 1024)
>>>>
>>>> Please use INFO(0xef6020, 0, 0, 0) and test wether it will still
>>>> work correctly. We will then be able to convert it to SNOR_ID3()
>>>> later.
>>>
>>> Tested it but it doesn't work with INFO(0xef6020, 0, 0, 0). I'll keep
>>> it as is.
>>
>> Can you please look into this? I'd expect this to work if the SFDP
>> tables are correct because all this should come from the tables.
>> You can look at /sys/kernel/debug/spi-nor/spi0.0/params and see
>> what is changing there.
>
> I tested it again but result is still the same. I can check the parsed
> info like below if I use INFO(0xef6020, 0, 64 * 1024, 1024) but I can't
> even check the debugfs info if I use INFO(0xef6020, 0, 0, 0) since it
> doesn't boot at all. I think, this patch should go as is and the size
> parsing issue could be fixed using a separate fix.
What does "doesn't boot at all" mean? Are there any kernel startup
messages?
Just to be sure, you have PARSE_SFDP set, right?
The entry should be (skipping OTP to make sure that isn't
the problem here):
{ "w25q512nwq", INFO(0xef6020, 0, 0, 0) PARSE_SFDP }
-michael
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-07-14 7:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 14:57 [PATCH] mtd: spi-nor: winbond: add support for W25Q512NW-IQ/IN Jae Hyun Yoo
2022-07-11 6:24 ` Cédric Le Goater
2022-07-11 9:50 ` Michael Walle
2022-07-13 14:26 ` Jae Hyun Yoo
2022-07-13 14:32 ` Michael Walle
2022-07-13 21:01 ` Jae Hyun Yoo
2022-07-14 7:41 ` Michael Walle [this message]
2022-07-14 13:47 ` Jae Hyun Yoo
2022-07-14 14:16 ` Michael Walle
2022-07-14 14:21 ` Michael Walle
2022-07-14 14:30 ` Jae Hyun Yoo
2022-07-15 20:15 ` Jae Hyun Yoo
2022-07-15 22:35 ` Jae Hyun Yoo
2022-07-15 23:03 ` Michael Walle
2022-07-15 23:15 ` Jae Hyun Yoo
2022-07-15 23:20 ` Michael Walle
2022-07-15 23:26 ` Jae Hyun Yoo
2022-07-15 22:52 ` Michael Walle
2022-07-15 23:04 ` Jae Hyun Yoo
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=00f0c9d480ef5a414f1c34492661bd9e@walle.cc \
--to=michael@walle.cc \
--cc=clg@kaod.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=p.yadav@ti.com \
--cc=quic_ggregory@quicinc.com \
--cc=quic_jaehyoo@quicinc.com \
--cc=quic_jiles@quicinc.com \
--cc=tudor.ambarus@microchip.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