All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	Richard Weinberger <richard@nod.at>, Marek Vasut <marex@denx.de>,
	Brian Norris <computersforpeace@gmail.com>
Subject: Re: mtd layer: support of hybrid flash(W25M161AW) having both NOR and NAND flash
Date: Thu, 4 Jan 2018 18:47:22 +0100	[thread overview]
Message-ID: <20180104184722.551ca6aa@bbrezillon> (raw)
In-Reply-To: <HE1PR04MB1241937FF43AAA64AE7EE776971F0@HE1PR04MB1241.eurprd04.prod.outlook.com>

+MTD maintainers.

On Thu, 4 Jan 2018 14:08:42 +0000
Prabhakar Kushwaha <prabhakar.kushwaha@nxp.com> wrote:

> Hi All,
> 
> Winbond has come up with special flash i.e.  W25M161AW. It consist of Serial NOR(Die #0) and Serial NAND(Die #1) flash. 
> Means both NOR, NAND flashes are placed in W25M161AW controlled by single chip-select. 
> 
> "Software Die Select (C2h)" command is being used to switch die or flash.

Why are they so mean to us?! :-)
 
>  
> It looks to be quite unique chip and wondering if any kind framework or work in progress available to handle it. 
> I know that SPI-NAND framework discussions is still in progress.

Well, nothing impossible to handle, we just need to declare 2 MTD
devices (one NAND and one NOR). This being said, it looks like we'll
need this spi-flash abstraction we have been talking about with Marek
and Cyrille to properly support these use cases: flash devices will be
exposed through different sub-layers (spi-nor or spi-nand), but we need
a common way to detect those spi-flash chips. I looked at a few SPI
NAND and SPI NOR chips, and from what I've seen so far they were quite
different (the opcodes and CMD+ADDR+DATA sequences were quite
different) so I thought we were safe to start with a completely
unconnected SPI NAND framework and merge some bits in a spi-flash layer
afterwards, but this chip proves me wrong :-/.

  reply	other threads:[~2018-01-04 17:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04 14:08 mtd layer: support of hybrid flash(W25M161AW) having both NOR and NAND flash Prabhakar Kushwaha
2018-01-04 17:47 ` Boris Brezillon [this message]
2018-01-05 10:21   ` Prabhakar Kushwaha
2018-01-05 13:35     ` Boris Brezillon
2018-01-05 13:38     ` Jonas Gorski
2018-01-05 13:44       ` Boris Brezillon
2018-01-05 13:58         ` Jonas Gorski
2018-01-08  8:42           ` Prabhakar Kushwaha
2018-01-08  9:14             ` Boris Brezillon
2018-01-08  9:39               ` Jonas Gorski
2018-01-08  9:47                 ` Boris Brezillon
2018-01-08 11:02               ` Frieder Schrempf
2018-01-08 12:31                 ` Boris Brezillon
2018-01-08 13:14                   ` Frieder Schrempf
2018-01-08 13:43                   ` Jonas Gorski
2018-01-08 14:32                     ` Boris Brezillon
2018-01-08 15:18                       ` Jonas Gorski
2018-01-08 15:45                         ` Boris Brezillon

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=20180104184722.551ca6aa@bbrezillon \
    --to=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.de \
    --cc=prabhakar.kushwaha@nxp.com \
    --cc=richard@nod.at \
    /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.