[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200529092758.ezuyac2r6vmp6tfs@yadavpratyush.com>
Date: Fri, 29 May 2020 14:57:58 +0530
From: Pratyush Yadav <me@...avpratyush.com>
To: Mason Yang <masonccyang@...c.com.tw>
Cc: broonie@...nel.org, tudor.ambarus@...rochip.com,
miquel.raynal@...tlin.com, richard@....at, vigneshr@...com,
boris.brezillon@...labora.com, matthias.bgg@...il.com,
juliensu@...c.com.tw, linux-kernel@...r.kernel.org,
linux-spi@...r.kernel.org, linux-mtd@...ts.infradead.org,
p.yadav@...com
Subject: Re: [PATCH v4 2/7] mtd: spi-nor: sfdp: parse xSPI Profile 1.0 table
On 29/05/20 03:36PM, Mason Yang wrote:
> JESD251, xSPI profile 1.0 table supports octal DTR mode.
> Extract information like the fast read opcode, dummy cycles for various
> frequencies, the number of dummy cycles needed for a Read Status
> Register command, the number of address bytes needed for a Read
> Status Register command, read volatile register command and write
> volatile register command.
Like I said before, please don't re-introduce the functions. My patch
series already parses the table. Add whatever new feature you want on
top of it.
> According to BFPT 20th DWORD of octal maximum speed, driver get it's
> specific dummy cycles from profile 1.0 table and then could update
> it to device by their fixup hooks.
My patch [0] already find out the dummy cycles from the table as you
suggested, though it doesn't consult the BFPT. Instead, it uses the
dummy cycle fields themselves as indication that a speed is supported or
not.
[0] https://lore.kernel.org/linux-mtd/20200525091544.17270-10-p.yadav@ti.com/
--
Regards,
Pratyush Yadav
Powered by blists - more mailing lists