[PATCH v3] drivers: spi-nor: Add JEDEC id for W25Q16JV

[Tudor.Ambarus at microchip.com]

On 1/20/22 4:39 PM, Jagan Teki wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On Thu, Jan 20, 2022 at 7:53 PM <Tudor.Ambarus at microchip.com> wrote:
>>
>> On 1/20/22 3:20 PM, Michael Walle wrote:
>>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>>
>>>>> +       {
>>>>> +               INFO("w25q16jvm", 0xef7015, 0, 64 * 1024,  32,
>>>>
>>>> Can this name as "w25q16jv-im/jm" ?
>>>
>>> FWIW, "w25q15jvm" would be the "correct" name in linux. Although for this
>>> particular flash the name in linux is "w25q16jv-im/jm"..
>>
>> would you fix it? :D
>>
>>>
>>> Anyhow, see [1] for a lengthy discussion on that name. That being said, I
>>> still don't share Tudors opinion on using that made up name, just because
>>> no one will find any flash if one searches for w25q16jvm in the internet.
>>
>> The temperature range "I/J" is skipped in the name because it does not have
>> any influence on the jedec-id. That's why we don't include the "Package Type"
>> field in the naming convention as well.
> 
> Okay, I'm merging v3. let me know if you have any questions?
> 

For now it should be fine. But if anyone is feeling brave enough maybe we should
fix the naming scheme for winbond once and for all. It seems that the flashes
were we append "m" support DTR, and in fact winbond names them blabla-dtr [1].
So instead of "w25q16jvm" maybe it's better to convert to "w25q16jv-dtr".
Are there any volunteers to check if my assumption is correct?

[1] https://www.winbond.com/hq/product/code-storage-flash-memory/serial-nor-flash/?__locale=en&selected=128Mb#Density