From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Masahiko Iwamoto <iwamoto@allied-telesis.co.jp>,
Jagan Teki <jagan@openedev.com>, Marek Vasut <marex@denx.de>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Sascha Hauer <kernel@pengutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: add dt support for Everspin MRAMs
Date: Mon, 16 Jan 2017 20:41:54 +0100 [thread overview]
Message-ID: <20170116194154.v2p2gbyvvfb5bwe6@pengutronix.de> (raw)
In-Reply-To: <CACna6ryLDwr0S=e-uUt+ZGcY8mNDnUtBPg_RmqtSVBziJkZd5w@mail.gmail.com>
On Mon, Jan 16, 2017 at 02:55:01PM +0100, Rafał Miłecki wrote:
> On 16 January 2017 at 14:35, Uwe Kleine-König
> <u.kleine-koenig@pengutronix.de> wrote:
> > The MR25 family doesn't support JEDEC, so they need explicit mentioning
> > in the list of supported spi IDs. This makes it possible to add these
> > using for example:
> >
> > compatible = "everspin,mr25h40";
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > ---
> > Hello,
> >
> > independent of the decision if -nonjedec is ok for m25p, this is needed
> > to make Everspin's MRAMs work.
> >
> > Best regards
> > Uwe
> >
> > drivers/mtd/devices/m25p80.c | 5 +++++
> > 1 file changed, 5 insertions(+)
> >
> > diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c
> > --- a/drivers/mtd/devices/m25p80.c
> > +++ b/drivers/mtd/devices/m25p80.c
> > @@ -305,6 +305,11 @@ static const struct spi_device_id m25p_ids[] = {
> > {"m25p40-nonjedec"}, {"m25p80-nonjedec"}, {"m25p16-nonjedec"},
> > {"m25p32-nonjedec"}, {"m25p64-nonjedec"}, {"m25p128-nonjedec"},
> >
> > + /* Everspin MRAMs without JEDEC support */
> > + { "mr25h256" }, /* 256 kib, 40 MHz */
>
> A trivial thing: I think it should be Kib
> https://en.wikipedia.org/wiki/Binary_prefix
Oh, really? 10^3 = k and 2^10 = Ki, stange. Should I resend for that?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2017-01-16 19:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 13:35 [PATCH] mtd: spi-nor: add dt support for Everspin MRAMs Uwe Kleine-König
2017-01-16 13:55 ` Rafał Miłecki
2017-01-16 16:08 ` Marek Vasut
2017-01-16 19:41 ` Uwe Kleine-König [this message]
2017-01-16 20:45 ` Rafał Miłecki
2017-01-16 21:00 ` [PATCH v2] " Uwe Kleine-König
2017-01-16 21:02 ` Rafał Miłecki
2017-01-16 21:24 ` Marek Vasut
2017-01-17 9:48 ` Cyrille Pitchen
2017-01-17 10:32 ` Cyrille Pitchen
2017-01-17 11:03 ` [PATCH v3] " Uwe Kleine-König
2017-01-17 13:04 ` Cyrille Pitchen
2017-01-17 13:16 ` Rafał Miłecki
2017-01-17 13:57 ` Cyrille Pitchen
2017-01-17 15:49 ` Rafał Miłecki
2017-01-18 13:51 ` Marek Vasut
2017-01-19 17:54 ` Rob Herring
2017-01-19 17:56 ` Rob Herring
2017-01-20 12:57 ` Cyrille Pitchen
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=20170116194154.v2p2gbyvvfb5bwe6@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=iwamoto@allied-telesis.co.jp \
--cc=jagan@openedev.com \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=zajec5@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