From: Joseph Kust <joseph.kust@rockwellcollins.com>
To: Tudor.Ambarus@microchip.com
Cc: marek.vasut@gmail.com, brandon.maier@rockwellcollins.com,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: spi-nor: Add support for sst26vf016b
Date: Tue, 10 Dec 2019 13:49:51 -0600 [thread overview]
Message-ID: <CAJzBf2Y55hXOpKAFkVwXx2=cX+36t8EuucVniDyne+_yp8eJpg@mail.gmail.com> (raw)
In-Reply-To: <ca733470-b953-d805-110c-2696bb9576ee@microchip.com>
Hi Tudor,
On Tue, Dec 10, 2019 at 11:10 AM <Tudor.Ambarus@microchip.com> wrote:
>
> Hi, Brandon,
>
> On 11/17/19 11:55 PM, Brandon Maier wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > From: Joseph Kust <joseph.kust@rockwellcollins.com>
> >
> > Adds support for sst26vf016b, a smaller variant of the sst26vf064b.
>
> How was this tested, what controller did you use? Did you test the quad read?
This was tested on a sama5d3 SOC using the atmel,at91rm9200-spi
controller. The quad read was not tested.
Kernel versions tested were branched from mainline 4.14.115 and 3.14.79
>
> Thanks,
> ta
>
> >
> > Signed-off-by: Joseph Kust <joseph.kust@rockwellcollins.com>
> > Signed-off-by: Brandon Maier <brandon.maier@rockwellcollins.com>
> > ---
> > drivers/mtd/spi-nor/spi-nor.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> > index f4afe123e9dc..500929903f61 100644
> > --- a/drivers/mtd/spi-nor/spi-nor.c
> > +++ b/drivers/mtd/spi-nor/spi-nor.c
> > @@ -2538,6 +2538,7 @@ static const struct flash_info spi_nor_ids[] = {
> > { "sst25wf080", INFO(0xbf2505, 0, 64 * 1024, 16, SECT_4K | SST_WRITE) },
> > { "sst26wf016b", INFO(0xbf2651, 0, 64 * 1024, 32, SECT_4K |
> > SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
> > + { "sst26vf016b", INFO(0xbf2641, 0, 64 * 1024, 32, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
> > { "sst26vf064b", INFO(0xbf2643, 0, 64 * 1024, 128, SECT_4K | SPI_NOR_DUAL_READ | SPI_NOR_QUAD_READ) },
> >
> > /* ST Microelectronics -- newer production may have feature updates */
> > --
> > 2.23.0
> >
> >
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-12-10 19:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 21:55 [PATCH] mtd: spi-nor: Add support for sst26vf016b Brandon Maier
2019-12-10 17:10 ` Tudor.Ambarus
2019-12-10 19:49 ` Joseph Kust [this message]
2019-12-23 15:34 ` Tudor.Ambarus
2020-01-06 16:33 ` [External] " Joseph Kust
2020-01-16 11:00 ` Tudor.Ambarus
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='CAJzBf2Y55hXOpKAFkVwXx2=cX+36t8EuucVniDyne+_yp8eJpg@mail.gmail.com' \
--to=joseph.kust@rockwellcollins.com \
--cc=Tudor.Ambarus@microchip.com \
--cc=brandon.maier@rockwellcollins.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.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;
as well as URLs for NNTP newsgroup(s).