From: Marek Vasut <marek.vasut@gmail.com>
To: thor.thayer@linux.intel.com, dwmw2@infradead.org,
computersforpeace@gmail.com, boris.brezillon@bootlin.com,
richard@nod.at
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: spi-nor: Add Micron MT25QU02 support
Date: Tue, 10 Apr 2018 23:01:49 +0200 [thread overview]
Message-ID: <1b9cbb7a-1976-6e4e-498c-28e351357c7b@gmail.com> (raw)
In-Reply-To: <b580ae74-b54c-6912-7238-dae8deb94072@linux.intel.com>
On 04/10/2018 10:35 PM, Thor Thayer wrote:
> Hi Marek,
>
> On 04/05/2018 02:17 PM, Marek Vasut wrote:
>> On 04/05/2018 09:12 PM, thor.thayer@linux.intel.com wrote:
>>> From: Thor Thayer <thor.thayer@linux.intel.com>
>>>
>>> Add support for a new Micron 2Gb Flash memory part.
>>> Datasheet is available: mt25q_qlkt_l_02g_cbb_0.pdf
>>>
>>> Testing was done on a Stratix10 SoCFPGA Development Kit.
>>>
>>> Reported-by: Sujith Chidurala <sujith.chakra.chidurala@intel.com>
>>> Tested-by: Paul Kim <paul.kim@intel.com>
>>> Signed-off-by: Thor Thayer <thor.thayer@linux.intel.com>
>>> ---
>>
>> Do we need this or can this be recognized as a SFDP flash ?
>>
> The error is
> "cadence-qspi ff8d2000.spi: unrecognized JEDEC id bytes: 20, bb, 22"
> which is fixed with this table addition. Is there a better way to handle
> this?
Seems like even with the SFDP parsing in place, we still need to track
the supported IDs, oh well.
Acked-by: Marek Vasut <marek.vasut@gmail.com>
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2018-04-10 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 19:12 [PATCH] mtd: spi-nor: Add Micron MT25QU02 support thor.thayer
2018-04-05 19:17 ` Marek Vasut
2018-04-10 20:35 ` Thor Thayer
2018-04-10 21:01 ` Marek Vasut [this message]
2018-04-22 17:14 ` Boris Brezillon
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=1b9cbb7a-1976-6e4e-498c-28e351357c7b@gmail.com \
--to=marek.vasut@gmail.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=thor.thayer@linux.intel.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