All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pratyush Yadav <ptyadav@amazon.de>
To: Mike Williamson <michael.williamson@criticallink.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: Question about SPI-NOR micron-st.c driver and OSPI devices.
Date: Tue, 24 Jan 2023 13:38:42 +0100	[thread overview]
Message-ID: <mafs0lelsf6p9.fsf@amazon.de> (raw)
In-Reply-To: <CAHEoWwuK_rZfka+skd=CTBf2mjAFL71HX_qC77rCWcaO+qy-vg@mail.gmail.com> (Mike Williamson's message of "Mon, 16 Jan 2023 08:44:20 -0500")

Hi Mike,

On Mon, Jan 16 2023, Mike Williamson wrote:

> Hello,
>
> I am looking at the drivers/mtd/spi-not/micron-st.c file.
>
> I was wondering why the mt35xu512aba_fixups, and in general the patch below,
> were not also applied to the mt35xu02g device entry?  Best I can tell, the
> datasheets for the two parts (same family, different densities) look nearly
> identical and the
>
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2333941.html
>
> I ask because we are having some troubles with the mt35xu02g and I am
> wondering if we need these fixups to run reliably in octal mode.

When I wrote the patches for Octal DTR support on MT35 flash family, I
only had the mt35xu512aba flash on me. And it was a new feature so I did
not want to add it to a flash I could not test, and risk breaking it. I
figured if someone really wanted Octal DTR support on the 02G part, they
can populate the fixups and test it themselves.

So this is what I suggest you do as well. Add the fixups, test it out,
and if it works, upstream the patch. While you are at it, perhaps also
convert it to use the PARSE_SFDP flag. See db391efe765c ("mtd: spi-nor:
spansion: Remove NO_SFDP_FLAGS from s28hs512t info") or a30f53d8bc0f
("mtd: spi-nor: issi: is25wp256: Init flash based on SFDP") for example.

-- 
Regards,
Pratyush Yadav



Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879




______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2023-01-24 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 13:44 Question about SPI-NOR micron-st.c driver and OSPI devices Mike Williamson
2023-01-24 12:38 ` Pratyush Yadav [this message]
2023-01-24 13:48   ` Mike Williamson
2023-01-24 14:01     ` Pratyush Yadav

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=mafs0lelsf6p9.fsf@amazon.de \
    --to=ptyadav@amazon.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael.williamson@criticallink.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.