public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Haikun Wang <haikun.wang@freescale.com>
Cc: linux-mtd@lists.infradead.org, han.xu@freescale.com, dwmw2@infradead.org
Subject: Re: [PATCH 1/5 v1] mtd: spi-nor: fsl-quadspi: Add a variable in 'fsl_qspi_devtype_data' to enable platform specail feature
Date: Mon, 6 Jul 2015 15:32:33 -0700	[thread overview]
Message-ID: <20150706223233.GD18370@brian-ubuntu> (raw)
In-Reply-To: <1435656518-14022-1-git-send-email-haikun.wang@freescale.com>

Hi Haikun,

On Tue, Jun 30, 2015 at 05:28:34PM +0800, Haikun Wang wrote:
> Add a variable in struct fsl_qspi_devtype_data.
> Add big endian registers flag.
> Enable big endian registers flag for LS1021A.
> 
> Signed-off-by: Haikun Wang <haikun.wang@freescale.com>
> ---
>  drivers/mtd/spi-nor/fsl-quadspi.c | 7 ++++++-
>  1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/mtd/spi-nor/fsl-quadspi.c b/drivers/mtd/spi-nor/fsl-quadspi.c
> index 6cd14e4..40c7953 100644
> --- a/drivers/mtd/spi-nor/fsl-quadspi.c
> +++ b/drivers/mtd/spi-nor/fsl-quadspi.c
> @@ -191,6 +191,9 @@
>  #define SEQID_EN4B		10
>  #define SEQID_BRWR		11
>  
> +/* Controller needs swap endian when access registers */
> +#define QUADSPI_QUIRK_REGMAP_BE    (1 << 5)
> +
>  enum fsl_qspi_devtype {
>  	FSL_QUADSPI_VYBRID,
>  	FSL_QUADSPI_IMX6SX,
> @@ -202,6 +205,7 @@ struct fsl_qspi_devtype_data {
>  	int rxfifo;
>  	int txfifo;
>  	int ahb_buf_size;
> +	int driver_data;
>  };
>  
>  static struct fsl_qspi_devtype_data vybrid_data = {
> @@ -222,7 +226,8 @@ static struct fsl_qspi_devtype_data ls1_data = {
>  	.devtype = FSL_QUADSPI_LS1,
>  	.rxfifo = 128,
>  	.txfifo = 64,
> -	.ahb_buf_size = 1024
> +	.ahb_buf_size = 1024,
> +	.driver_data = QUADSPI_QUIRK_REGMAP_BE
>  };
>  
>  #define FSL_QSPI_MAX_CHIP	4

This patch series appears to be based on an unreviewed, unapplied series
you sent a few weeks ago. But you didn't note the dependency. In the
future, please make note of such dependencies (e.g., by providing a
cover letter which explains this), to help reviewers like myself. If we
can't apply your patches, we can't really review them.

Thanks,
Brian

  parent reply	other threads:[~2015-07-06 22:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-30  9:28 [PATCH 1/5 v1] mtd: spi-nor: fsl-quadspi: Add a variable in 'fsl_qspi_devtype_data' to enable platform specail feature Haikun Wang
2015-06-30  9:28 ` [PATCH 2/5 v1] mtd: spi-nor: fsl-quadspi: Wrap writel/readl with qspi_writel/qspi_readl Haikun Wang
2015-06-30  9:28 ` [PATCH 3/5 v4] mtd: spi-nor: fsl-quadspi: Enable support big endian registers Haikun Wang
2015-06-30  9:28 ` [PATCH 4/5 v1] mtd: spi-nor: fsl-quadspi: Add QSPI dts node for LS1021A Haikun Wang
2015-06-30  9:28 ` [PATCH 5/5 v1] mtd: spi-nor: fsl-quadspi: Update bindings documentation Haikun Wang
2015-07-06 22:32 ` Brian Norris [this message]
2015-07-07  3:00   ` [PATCH 1/5 v1] mtd: spi-nor: fsl-quadspi: Add a variable in 'fsl_qspi_devtype_data' to enable platform specail feature Wang Haikun

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=20150706223233.GD18370@brian-ubuntu \
    --to=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=haikun.wang@freescale.com \
    --cc=han.xu@freescale.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox