From: Brian Norris <computersforpeace@gmail.com>
To: Joachim Eastwood <manabian@gmail.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org,
zajec5@gmail.com, linux-arm-kernel@lists.infradead.org,
ezequiel@vanguardiasur.com.ar
Subject: Re: [PATCH v5] mtd: spi-nor: add driver for NXP SPI Flash Interface (SPIFI)
Date: Thu, 13 Aug 2015 14:47:39 -0700 [thread overview]
Message-ID: <20150813214739.GH60523@google.com> (raw)
In-Reply-To: <1439486380-17720-1-git-send-email-manabian@gmail.com>
On Thu, Aug 13, 2015 at 07:19:40PM +0200, Joachim Eastwood wrote:
> Add SPI-NOR driver for the SPI Flash Interface (SPIFI)
> controller that is found on newer NXP MCU devices.
>
> The controller supports serial SPI Flash devices with 1-, 2-
> and 4-bit width in either SPI mode 0 or 3. The controller
> can operate in either command or memory mode. In memory mode
> the Flash is exposed as normal memory and can be directly
> accessed by the CPU.
>
> Signed-off-by: Joachim Eastwood <manabian@gmail.com>
> Reviewed-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> ---
> Hi Brian,
>
> I skipped the cover letter since you already applied the 2nd
> of patch of the original set and using a cover letter for
> just one patch seemed a bit useless. Cover letter for v4 can
> be found here: http://marc.info/?l=devicetree&m=143647330431908&w=2
>
> This version address all comments from Brian Norris except
> for two things noted below.
>
> If the line below is removed the kernel opses on jffs2 mount.
> spifi->mtd.priv = &spifi->nor;
> It seems like spi-nor.c doesn't setup this field. fsl-quadspi
> also assigns this field, btw.
Sorry, I overlooked that. But that code's pretty dumb. I'll take yours
as-is, but I'll send a patch to fix both.
> The read/wait ordering in nxp_spifi_read_reg is correct. I
> don't really have a good explaination for the ordering. The
> user manual doesn't document the SPIFI in detail, but the
> offcial NXP spifilib has the same ordering.
OK, no problem.
> Changes since v4:
> - spifi: always autodetect SPI Flash
> - s/spi/SPI on dev_* output
> - add parentheses to SPIFI_CMD_DATALEN macro
> - rebase on mtd-master
>
> Changes since v3:
> - fix bug in write function
> - rebase on 4.2-rc1
>
> Changes since v2:
> - default to auto detection unless chip is specified
> - update doc with reference to jedec,spi-nor.txt
>
> Test on the following boards.
> Hitex board boots on SPIFI Flash with JFFS2.
>
> Hitex LPC4350 Eval board:
> [ 2.093956] nxp-spifi 40003000.spifi: s25sl064p (8192 Kbytes)
>
> Embedded Artists' LPC4357 Developer's Kit:
> [ 3.051627] nxp-spifi 40003000.spifi: s25fl016k (2048 Kbytes)
Applied to l2-mtd.git, thanks!
BTW, is this driver worth a MAINTAINERS entry? It's nice to always have
someone on CC that has the hardware. The git history should probably
pick you up anyway when running get_maintainers.pl, so it may not be
absolutely necessary.
> Both s25fl016k and s25sl064p support dual/quad mode, but this
> is not flagged in spi-nor.c. I have sent a patch for s25fl016k
> and will send a patch s25sl064p please apply when you get them.
I'll see if I can dig these out of the mailing list eventually. I have a
sizable backlog.
Brian
WARNING: multiple messages have this Message-ID (diff)
From: computersforpeace@gmail.com (Brian Norris)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5] mtd: spi-nor: add driver for NXP SPI Flash Interface (SPIFI)
Date: Thu, 13 Aug 2015 14:47:39 -0700 [thread overview]
Message-ID: <20150813214739.GH60523@google.com> (raw)
In-Reply-To: <1439486380-17720-1-git-send-email-manabian@gmail.com>
On Thu, Aug 13, 2015 at 07:19:40PM +0200, Joachim Eastwood wrote:
> Add SPI-NOR driver for the SPI Flash Interface (SPIFI)
> controller that is found on newer NXP MCU devices.
>
> The controller supports serial SPI Flash devices with 1-, 2-
> and 4-bit width in either SPI mode 0 or 3. The controller
> can operate in either command or memory mode. In memory mode
> the Flash is exposed as normal memory and can be directly
> accessed by the CPU.
>
> Signed-off-by: Joachim Eastwood <manabian@gmail.com>
> Reviewed-by: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
> ---
> Hi Brian,
>
> I skipped the cover letter since you already applied the 2nd
> of patch of the original set and using a cover letter for
> just one patch seemed a bit useless. Cover letter for v4 can
> be found here: http://marc.info/?l=devicetree&m=143647330431908&w=2
>
> This version address all comments from Brian Norris except
> for two things noted below.
>
> If the line below is removed the kernel opses on jffs2 mount.
> spifi->mtd.priv = &spifi->nor;
> It seems like spi-nor.c doesn't setup this field. fsl-quadspi
> also assigns this field, btw.
Sorry, I overlooked that. But that code's pretty dumb. I'll take yours
as-is, but I'll send a patch to fix both.
> The read/wait ordering in nxp_spifi_read_reg is correct. I
> don't really have a good explaination for the ordering. The
> user manual doesn't document the SPIFI in detail, but the
> offcial NXP spifilib has the same ordering.
OK, no problem.
> Changes since v4:
> - spifi: always autodetect SPI Flash
> - s/spi/SPI on dev_* output
> - add parentheses to SPIFI_CMD_DATALEN macro
> - rebase on mtd-master
>
> Changes since v3:
> - fix bug in write function
> - rebase on 4.2-rc1
>
> Changes since v2:
> - default to auto detection unless chip is specified
> - update doc with reference to jedec,spi-nor.txt
>
> Test on the following boards.
> Hitex board boots on SPIFI Flash with JFFS2.
>
> Hitex LPC4350 Eval board:
> [ 2.093956] nxp-spifi 40003000.spifi: s25sl064p (8192 Kbytes)
>
> Embedded Artists' LPC4357 Developer's Kit:
> [ 3.051627] nxp-spifi 40003000.spifi: s25fl016k (2048 Kbytes)
Applied to l2-mtd.git, thanks!
BTW, is this driver worth a MAINTAINERS entry? It's nice to always have
someone on CC that has the hardware. The git history should probably
pick you up anyway when running get_maintainers.pl, so it may not be
absolutely necessary.
> Both s25fl016k and s25sl064p support dual/quad mode, but this
> is not flagged in spi-nor.c. I have sent a patch for s25fl016k
> and will send a patch s25sl064p please apply when you get them.
I'll see if I can dig these out of the mailing list eventually. I have a
sizable backlog.
Brian
next prev parent reply other threads:[~2015-08-13 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 17:19 [PATCH v5] mtd: spi-nor: add driver for NXP SPI Flash Interface (SPIFI) Joachim Eastwood
2015-08-13 17:19 ` Joachim Eastwood
2015-08-13 21:47 ` Brian Norris [this message]
2015-08-13 21:47 ` Brian Norris
2015-08-13 22:10 ` Joachim Eastwood
2015-08-13 22:10 ` Joachim Eastwood
2015-08-13 22:13 ` Brian Norris
2015-08-13 22:13 ` Brian Norris
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=20150813214739.GH60523@google.com \
--to=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel@vanguardiasur.com.ar \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=manabian@gmail.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 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.