From: <Tudor.Ambarus@microchip.com>
To: <purna.chandra.mandal@intel.com>, <f.blogs@napier.co.nz>,
<boris.brezillon@bootlin.com>, <richard@nod.at>,
<vigneshr@ti.com>
Cc: <linux-kernel@vger.kernel.org>, <marek.vasut@gmail.com>,
<computersforpeace@gmail.com>, <linux-mtd@lists.infradead.org>,
<dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: spi-nor: cadence-quadspi: write upto 8-bytes data in STIG mode
Date: Sun, 3 Feb 2019 12:20:20 +0000 [thread overview]
Message-ID: <82eafaf8-803e-36a9-49ca-83d84c55537a@microchip.com> (raw)
In-Reply-To: <20190128050229.44965-1-purna.chandra.mandal@intel.com>
+ Vignesh
On 01/28/2019 07:02 AM, Purna Chandra Mandal wrote:
> cadence-quadspi controller allows upto eight bytes of data to
> be written in software Triggered Instruction generator (STIG) mode
> of operation. Lower 4 bytes are written through writedatalower and
> upper 4 bytes by writedataupper register.
>
> This patch allows all the 8 bytes to be written.
>
> Signed-off-by: Purna Chandra Mandal <purna.chandra.mandal@intel.com>
Looks good for me:
Reviewed-by: Tudor Ambarus <tudor.ambarus@microchip.com>
Vignesh, can we have your R-b or T-b tag?
Cheers,
ta
> ---
>
> drivers/mtd/spi-nor/cadence-quadspi.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/mtd/spi-nor/cadence-quadspi.c b/drivers/mtd/spi-nor/cadence-quadspi.c
> index 04cedd3a2bf6..7f78f9409ddd 100644
> --- a/drivers/mtd/spi-nor/cadence-quadspi.c
> +++ b/drivers/mtd/spi-nor/cadence-quadspi.c
> @@ -418,9 +418,10 @@ static int cqspi_command_write(struct spi_nor *nor, const u8 opcode,
> void __iomem *reg_base = cqspi->iobase;
> unsigned int reg;
> unsigned int data;
> + u32 write_len;
> int ret;
>
> - if (n_tx > 4 || (n_tx && !txbuf)) {
> + if (n_tx > CQSPI_STIG_DATA_LEN_MAX || (n_tx && !txbuf)) {
> dev_err(nor->dev,
> "Invalid input argument, cmdlen %d txbuf 0x%p\n",
> n_tx, txbuf);
> @@ -433,10 +434,18 @@ static int cqspi_command_write(struct spi_nor *nor, const u8 opcode,
> reg |= ((n_tx - 1) & CQSPI_REG_CMDCTRL_WR_BYTES_MASK)
> << CQSPI_REG_CMDCTRL_WR_BYTES_LSB;
> data = 0;
> - memcpy(&data, txbuf, n_tx);
> + write_len = (n_tx > 4) ? 4 : n_tx;
> + memcpy(&data, txbuf, write_len);
> + txbuf += write_len;
> writel(data, reg_base + CQSPI_REG_CMDWRITEDATALOWER);
> - }
>
> + if (n_tx > 4) {
> + data = 0;
> + write_len = n_tx - 4;
> + memcpy(&data, txbuf, write_len);
> + writel(data, reg_base + CQSPI_REG_CMDWRITEDATAUPPER);
> + }
> + }
> ret = cqspi_exec_flash_cmd(cqspi, reg);
> return ret;
> }
>
next prev parent reply other threads:[~2019-02-03 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-28 5:02 [PATCH] mtd: spi-nor: cadence-quadspi: write upto 8-bytes data in STIG mode Purna Chandra Mandal
2019-02-03 12:20 ` Tudor.Ambarus [this message]
2019-02-04 13:37 ` Vignesh R
2019-02-05 7:00 ` Mandal, Purna Chandra
2019-02-05 10:00 ` Vignesh R
2019-02-10 18:56 ` Boris Brezillon
-- strict thread matches above, loose matches on Subject: below --
2018-12-14 2:15 [PATCH] " Purna Chandra Mandal
2019-01-21 9:37 ` Tudor.Ambarus
2019-01-28 4:57 ` Mandal, Purna Chandra
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=82eafaf8-803e-36a9-49ca-83d84c55537a@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=f.blogs@napier.co.nz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=purna.chandra.mandal@intel.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).