All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 22 Jul 2015 15:41:46 +0200	[thread overview]
Message-ID: <201507221541.46135.marex@denx.de> (raw)
In-Reply-To: <036f143509fed3f303508d1688d68012790f835a.1437569902.git.cyrille.pitchen@atmel.com>

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 ?

> + */
> +static inline int spi_nor_set_protocol(struct spi_nor *nor,
> +				       enum spi_protocol proto)
> +{
> +	if (nor->set_protocol)
> +		return nor->set_protocol(nor, proto);
> +
> +	return 0;
> +}
> +
>  static inline struct spi_nor *mtd_to_spi_nor(struct mtd_info *mtd)
>  {
>  	return mtd->priv;

[...]

Best regards,
Marek Vasut

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: Wed, 22 Jul 2015 15:41:46 +0200	[thread overview]
Message-ID: <201507221541.46135.marex@denx.de> (raw)
In-Reply-To: <036f143509fed3f303508d1688d68012790f835a.1437569902.git.cyrille.pitchen@atmel.com>

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 ?

> + */
> +static inline int spi_nor_set_protocol(struct spi_nor *nor,
> +				       enum spi_protocol proto)
> +{
> +	if (nor->set_protocol)
> +		return nor->set_protocol(nor, proto);
> +
> +	return 0;
> +}
> +
>  static inline struct spi_nor *mtd_to_spi_nor(struct mtd_info *mtd)
>  {
>  	return mtd->priv;

[...]

Best regards,
Marek Vasut

  reply	other threads:[~2015-07-22 13:41 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 [this message]
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
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=201507221541.46135.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.