From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: m25p80: Use CFI to identify unknown flash chips
Date: Thu, 12 May 2011 14:49:17 +0300 [thread overview]
Message-ID: <1305200957.2713.99.camel@localhost> (raw)
In-Reply-To: <97ed2bb63176b59ee2b283be69f0c6a4@localhost>
On Sun, 2011-05-08 at 16:16 -0700, Kevin Cernekee wrote:
> Many of the newer SPI flash devices support both JEDEC and CFI queries.
> While JEDEC RDID only returns the device ID, CFI provides the device
> size, eraseblock size, and other information. In some cases this may
> allow previously unknown devices to be supported without adding yet
> another entry to m25p_ids[].
>
> This patch replaces jedec_probe() with a new cfi_probe() function. The
> existing JEDEC probe/match logic is attempted first, and CFI is only used
> if no match is found.
>
> Additionally, platform_data.type may now specify "auto", which instructs
> m25p80.c to autodetect the chip type rather than trying to match a
> specific entry. In some situations, board manufacturers have multiple
> sources for flash parts (usually with identical geometries), but do not
> know in advance which specific part will be used on a given board. The
> "auto" parameter allows the BSP to indicate this to the driver, so that
> the driver does not warn the user about a flash device mismatch.
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
> drivers/mtd/devices/m25p80.c | 181 ++++++++++++++++++++++++++++--------------
> 1 files changed, 121 insertions(+), 60 deletions(-)
Could you please send a patch which cleanly applies to l2-mtd-2.6.git?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Kevin Cernekee <cernekee@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mtd: m25p80: Use CFI to identify unknown flash chips
Date: Thu, 12 May 2011 14:49:17 +0300 [thread overview]
Message-ID: <1305200957.2713.99.camel@localhost> (raw)
In-Reply-To: <97ed2bb63176b59ee2b283be69f0c6a4@localhost>
On Sun, 2011-05-08 at 16:16 -0700, Kevin Cernekee wrote:
> Many of the newer SPI flash devices support both JEDEC and CFI queries.
> While JEDEC RDID only returns the device ID, CFI provides the device
> size, eraseblock size, and other information. In some cases this may
> allow previously unknown devices to be supported without adding yet
> another entry to m25p_ids[].
>
> This patch replaces jedec_probe() with a new cfi_probe() function. The
> existing JEDEC probe/match logic is attempted first, and CFI is only used
> if no match is found.
>
> Additionally, platform_data.type may now specify "auto", which instructs
> m25p80.c to autodetect the chip type rather than trying to match a
> specific entry. In some situations, board manufacturers have multiple
> sources for flash parts (usually with identical geometries), but do not
> know in advance which specific part will be used on a given board. The
> "auto" parameter allows the BSP to indicate this to the driver, so that
> the driver does not warn the user about a flash device mismatch.
>
> Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
> ---
> drivers/mtd/devices/m25p80.c | 181 ++++++++++++++++++++++++++++--------------
> 1 files changed, 121 insertions(+), 60 deletions(-)
Could you please send a patch which cleanly applies to l2-mtd-2.6.git?
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-05-12 11:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-08 23:16 [PATCH] mtd: m25p80: Use CFI to identify unknown flash chips Kevin Cernekee
2011-05-08 23:16 ` Kevin Cernekee
2011-05-12 11:49 ` Artem Bityutskiy [this message]
2011-05-12 11:49 ` Artem Bityutskiy
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=1305200957.2713.99.camel@localhost \
--to=dedekind1@gmail.com \
--cc=cernekee@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
/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.