From: "Wang, Yaliang" <yaliang.wang@windriver.com>
To: Tudor.Ambarus@microchip.com, vigneshr@ti.com,
miquel.raynal@bootlin.com, richard@nod.at
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: spi-nor: Use CLSR command for FL-L chips
Date: Tue, 30 Mar 2021 00:53:22 +0800 [thread overview]
Message-ID: <4ea8651b-7baa-2465-356c-d8c365eb4d07@windriver.com> (raw)
In-Reply-To: <7c8daaf6-a802-5de5-63d9-81febd7dd7b7@microchip.com>
Hi, Tudor
Sorry to have kept you waiting so long, I'm still working on it. The
previous version is not so rigorous, so I tried to understand the up
layer codes better and also do some tests.
I've learnt the strategy you mentioned in the comments, I'll prepare the
second version ASAP and send it for reviewing, we'll see if it's more
close to fixing the problem.
Best Regards,
Yaliang
On 2021/3/29 21:12, Tudor.Ambarus@microchip.com wrote:
> [Please note: This e-mail is from an EXTERNAL e-mail address]
>
> Hi, Yaliang,
>
> On 2/24/21 6:30 PM, Tudor Ambarus - M18064 wrote:
>> Yes, please. Let us know how it goes.
>
> I think I hit the same problem that you're trying to fix, when testing a
> s25fl064l. What's the status of this, do you still work on it? Do you
> want me to sketch the core patches and you to come on top of it with the
> spansion fix?
>
> Cheers,
> ta
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2021-03-29 23:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 15:39 [PATCH] mtd: spi-nor: Use CLSR command for FL-L chips yaliang.wang
2021-01-23 17:45 ` Tudor.Ambarus
2021-01-24 6:12 ` Vignesh Raghavendra
2021-01-26 2:06 ` Wang, Yaliang
2021-01-26 8:51 ` Tudor.Ambarus
2021-02-23 16:36 ` Yaliang.Wang
2021-02-23 17:31 ` Tudor.Ambarus
2021-02-24 16:24 ` Yaliang.Wang
2021-02-24 16:30 ` Tudor.Ambarus
2021-03-29 13:12 ` Tudor.Ambarus
2021-03-29 16:53 ` Wang, Yaliang [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=4ea8651b-7baa-2465-356c-d8c365eb4d07@windriver.com \
--to=yaliang.wang@windriver.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--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