[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHyZL-dgrGu3z4ySy_EdG7KdZwU+DHdo8nH=+Go_nGZUZYFq_A@mail.gmail.com>
Date: Wed, 10 Aug 2022 16:14:09 +0100
From: Sudip Mukherjee <sudip.mukherjee@...ive.com>
To: Tudor Ambarus <Tudor.Ambarus@...rochip.com>
Cc: Pratyush Yadav <pratyush@...nel.org>,
Michael Walle <michael@...le.cc>,
Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>,
Vignesh Raghavendra <vigneshr@...com>,
Greentime Hu <greentime.hu@...ive.com>,
Jude Onyenegecha <jude.onyenegecha@...ive.com>,
William Salmon <william.salmon@...ive.com>,
Adnan Chowdhury <adnan.chowdhury@...ive.com>,
Ben Dooks <ben.dooks@...ive.com>,
linux-mtd@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/3] mtd: spi-nor: add SFDP fixups for Quad Page Program
On Wed, Aug 10, 2022 at 9:06 AM <Tudor.Ambarus@...rochip.com> wrote:
>
> On 8/9/22 23:14, Sudip Mukherjee wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > SFDP table of some flash chips do not advertise support of Quad Input
> > Page Program even though it has support. Use fixup flags and add hardware
> > cap for these chips.
> >
<snip>
> > @@ -520,6 +521,7 @@ struct flash_info {
> > u8 fixup_flags;
> > #define SPI_NOR_4B_OPCODES BIT(0)
> > #define SPI_NOR_IO_MODE_EN_VOLATILE BIT(1)
> > +#define SPI_NOR_QUAD_PP BIT(2)
>
> No, as I previously said, SPI_NOR_QUAD_PP should be declared as a
> info->flags, not as info->fixup_flags.
Sorry, I was confused as info->fixup_flags says "it indicates support
that can be discovered via SFDP ideally, but can not be discovered
for this particular flash because the SFDP table that indicates this
support is not defined by the flash."
--
Regards
Sudip
Powered by blists - more mailing lists