From: Marek Vasut <marex@denx.de>
To: Cyrille Pitchen <cyrille.pitchen@atmel.com>
Cc: nicolas.ferre@atmel.com, broonie@kernel.org,
linux-spi@vger.kernel.org, dwmw2@infradead.org,
computersforpeace@gmail.com, zajec5@gmail.com,
beanhuo@micron.com, juhosg@openwrt.org, shijie.huang@intel.com,
ben@decadent.org.uk, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 1/5] mtd: spi-nor: notify (Q)SPI controller about protocol change
Date: Thu, 23 Jul 2015 09:00:50 +0200 [thread overview]
Message-ID: <201507230900.50570.marex@denx.de> (raw)
In-Reply-To: <55AFC3F0.5050002@atmel.com>
On Wednesday, July 22, 2015 at 06:25:20 PM, Cyrille Pitchen wrote:
> Hi Marek,
>
> Le 22/07/2015 15:41, Marek Vasut a écrit :
> > On Wednesday, July 22, 2015 at 03:17:06 PM, Cyrille Pitchen wrote:
> >> Once the Quad SPI mode has been enabled on a Micron flash memory, this
> >> device expects ALL the following commands to use the SPI 4-4-4 protocol.
> >> The (Q)SPI controller needs to be notified about the protocol change so
> >> it can adapt and keep on dialoging with the Micron memory.
> >>
> >> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
> >> ---
> >>
> >> drivers/mtd/spi-nor/spi-nor.c | 17 +++++++++++++++++
> >> include/linux/mtd/spi-nor.h | 13 +++++++++++++
> >> 2 files changed, 30 insertions(+)
> >>
> >> diff --git a/drivers/mtd/spi-nor/spi-nor.c
> >> b/drivers/mtd/spi-nor/spi-nor.c index d78831b4422b..93627d4e6be8 100644
> >> --- a/drivers/mtd/spi-nor/spi-nor.c
> >> +++ b/drivers/mtd/spi-nor/spi-nor.c
> >> @@ -163,6 +163,18 @@ static inline int write_disable(struct spi_nor
> >> *nor)
> >>
> >> return nor->write_reg(nor, SPINOR_OP_WRDI, NULL, 0, 0);
> >>
> >> }
> >>
> >> +/*
> >> + * Notify the (Q)SPI controller about the new protocol to be used.
> >
> > Hi!
> >
> > Can you please just reword this a little, so that it is absolutelly clear
> > even to the less bright of us (like me) that this is a notification
> > coming from the upper layers (ie. the spi-nor framework) toward the
> > hardware ?
>
> Sure, no problem! what about the following?
>
> /*
> * Let the spi-nor framework notify lower layers, especially the driver of
> the * (Q)SPI controller, about the new protocol to be used. Indeed, once
> the * spi-nor framework has sent manufacturer specific commands to a
> memory to * enable its Quad SPI mode, it should immediately after tell the
> QSPI * controller to use the very same Quad SPI protocol as expected by
> the memory. */
Sure, excellent, thanks ! :-)
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex-ynQEQJNshbs@public.gmane.org>
To: Cyrille Pitchen
<cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
Cc: nicolas.ferre-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org,
broonie-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-spi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
computersforpeace-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
zajec5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
beanhuo-AL4WhLSQfzjQT0dZR+AlfA@public.gmane.org,
juhosg-p3rKhJxN3npAfugRpC6u6w@public.gmane.org,
shijie.huang-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
ben-/+tVBieCtBitmTQ+vhA3Yw@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
robh+dt-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
pawel.moll-5wv7dgnIgG8@public.gmane.org,
mark.rutland-5wv7dgnIgG8@public.gmane.org,
ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
galak-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org,
linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 1/5] mtd: spi-nor: notify (Q)SPI controller about protocol change
Date: Thu, 23 Jul 2015 09:00:50 +0200 [thread overview]
Message-ID: <201507230900.50570.marex@denx.de> (raw)
In-Reply-To: <55AFC3F0.5050002-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
On Wednesday, July 22, 2015 at 06:25:20 PM, Cyrille Pitchen wrote:
> Hi Marek,
>
> Le 22/07/2015 15:41, Marek Vasut a écrit :
> > On Wednesday, July 22, 2015 at 03:17:06 PM, Cyrille Pitchen wrote:
> >> Once the Quad SPI mode has been enabled on a Micron flash memory, this
> >> device expects ALL the following commands to use the SPI 4-4-4 protocol.
> >> The (Q)SPI controller needs to be notified about the protocol change so
> >> it can adapt and keep on dialoging with the Micron memory.
> >>
> >> Signed-off-by: Cyrille Pitchen <cyrille.pitchen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
> >> ---
> >>
> >> drivers/mtd/spi-nor/spi-nor.c | 17 +++++++++++++++++
> >> include/linux/mtd/spi-nor.h | 13 +++++++++++++
> >> 2 files changed, 30 insertions(+)
> >>
> >> diff --git a/drivers/mtd/spi-nor/spi-nor.c
> >> b/drivers/mtd/spi-nor/spi-nor.c index d78831b4422b..93627d4e6be8 100644
> >> --- a/drivers/mtd/spi-nor/spi-nor.c
> >> +++ b/drivers/mtd/spi-nor/spi-nor.c
> >> @@ -163,6 +163,18 @@ static inline int write_disable(struct spi_nor
> >> *nor)
> >>
> >> return nor->write_reg(nor, SPINOR_OP_WRDI, NULL, 0, 0);
> >>
> >> }
> >>
> >> +/*
> >> + * Notify the (Q)SPI controller about the new protocol to be used.
> >
> > Hi!
> >
> > Can you please just reword this a little, so that it is absolutelly clear
> > even to the less bright of us (like me) that this is a notification
> > coming from the upper layers (ie. the spi-nor framework) toward the
> > hardware ?
>
> Sure, no problem! what about the following?
>
> /*
> * Let the spi-nor framework notify lower layers, especially the driver of
> the * (Q)SPI controller, about the new protocol to be used. Indeed, once
> the * spi-nor framework has sent manufacturer specific commands to a
> memory to * enable its Quad SPI mode, it should immediately after tell the
> QSPI * controller to use the very same Quad SPI protocol as expected by
> the memory. */
Sure, excellent, thanks ! :-)
--
To unsubscribe from this list: send the line "unsubscribe linux-spi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: marex@denx.de (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/5] mtd: spi-nor: notify (Q)SPI controller about protocol change
Date: Thu, 23 Jul 2015 09:00:50 +0200 [thread overview]
Message-ID: <201507230900.50570.marex@denx.de> (raw)
In-Reply-To: <55AFC3F0.5050002@atmel.com>
On Wednesday, July 22, 2015 at 06:25:20 PM, Cyrille Pitchen wrote:
> Hi Marek,
>
> Le 22/07/2015 15:41, Marek Vasut a ?crit :
> > On Wednesday, July 22, 2015 at 03:17:06 PM, Cyrille Pitchen wrote:
> >> Once the Quad SPI mode has been enabled on a Micron flash memory, this
> >> device expects ALL the following commands to use the SPI 4-4-4 protocol.
> >> The (Q)SPI controller needs to be notified about the protocol change so
> >> it can adapt and keep on dialoging with the Micron memory.
> >>
> >> Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
> >> ---
> >>
> >> drivers/mtd/spi-nor/spi-nor.c | 17 +++++++++++++++++
> >> include/linux/mtd/spi-nor.h | 13 +++++++++++++
> >> 2 files changed, 30 insertions(+)
> >>
> >> diff --git a/drivers/mtd/spi-nor/spi-nor.c
> >> b/drivers/mtd/spi-nor/spi-nor.c index d78831b4422b..93627d4e6be8 100644
> >> --- a/drivers/mtd/spi-nor/spi-nor.c
> >> +++ b/drivers/mtd/spi-nor/spi-nor.c
> >> @@ -163,6 +163,18 @@ static inline int write_disable(struct spi_nor
> >> *nor)
> >>
> >> return nor->write_reg(nor, SPINOR_OP_WRDI, NULL, 0, 0);
> >>
> >> }
> >>
> >> +/*
> >> + * Notify the (Q)SPI controller about the new protocol to be used.
> >
> > Hi!
> >
> > Can you please just reword this a little, so that it is absolutelly clear
> > even to the less bright of us (like me) that this is a notification
> > coming from the upper layers (ie. the spi-nor framework) toward the
> > hardware ?
>
> Sure, no problem! what about the following?
>
> /*
> * Let the spi-nor framework notify lower layers, especially the driver of
> the * (Q)SPI controller, about the new protocol to be used. Indeed, once
> the * spi-nor framework has sent manufacturer specific commands to a
> memory to * enable its Quad SPI mode, it should immediately after tell the
> QSPI * controller to use the very same Quad SPI protocol as expected by
> the memory. */
Sure, excellent, thanks ! :-)
next prev parent reply other threads:[~2015-07-23 7:00 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 13:17 [PATCH v2 0/5] add driver for Atmel QSPI controller Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` [PATCH v2 1/5] mtd: spi-nor: notify (Q)SPI controller about protocol change Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:41 ` Marek Vasut
2015-07-22 13:41 ` Marek Vasut
2015-07-22 16:25 ` Cyrille Pitchen
2015-07-22 16:25 ` Cyrille Pitchen
2015-07-22 16:25 ` Cyrille Pitchen
2015-07-22 16:25 ` Cyrille Pitchen
2015-07-23 7:00 ` Marek Vasut [this message]
2015-07-23 7:00 ` Marek Vasut
2015-07-23 7:00 ` Marek Vasut
2015-07-22 13:17 ` [PATCH v2 2/5] Documentation: mtd: add a DT property to set the number of dummy cycles Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:43 ` Marek Vasut
2015-07-22 13:43 ` Marek Vasut
2015-07-22 13:43 ` Marek Vasut
2015-07-22 16:59 ` Cyrille Pitchen
2015-07-22 16:59 ` Cyrille Pitchen
2015-07-22 16:59 ` Cyrille Pitchen
2015-07-22 16:59 ` Cyrille Pitchen
2015-07-23 7:02 ` Marek Vasut
2015-07-23 7:02 ` Marek Vasut
2015-07-23 7:02 ` Marek Vasut
2015-07-22 13:17 ` [PATCH v2 3/5] mtd: spi-nor: allow to tune " Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` [PATCH v2 4/5] Documentation: atmel-quadspi: add binding file for Atmel QSPI driver Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` [PATCH v2 5/5] mtd: atmel-quadspi: add driver for Atmel QSPI controller Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:17 ` Cyrille Pitchen
2015-07-22 13:50 ` Marek Vasut
2015-07-22 13:50 ` Marek Vasut
2015-07-22 13:50 ` Marek Vasut
2015-07-27 8:41 ` Cyrille Pitchen
2015-07-27 8:41 ` Cyrille Pitchen
2015-07-27 8:41 ` Cyrille Pitchen
2015-07-27 8:41 ` Cyrille Pitchen
2015-07-27 10:53 ` Marek Vasut
2015-07-27 10:53 ` Marek Vasut
2015-07-27 10:53 ` Marek Vasut
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=201507230900.50570.marex@denx.de \
--to=marex@denx.de \
--cc=beanhuo@micron.com \
--cc=ben@decadent.org.uk \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=juhosg@openwrt.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nicolas.ferre@atmel.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=shijie.huang@intel.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.