From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Chuanhua Han <chuanhua.han@nxp.com>
Cc: cheetah0585@163.com, ran.wang_1@nxp.com, stable@vger.kernel.org
Subject: Re: [PATCH v4] mtd: spi-mem: Add the default transfer length adjustments
Date: Tue, 21 Aug 2018 09:25:07 +0200 [thread overview]
Message-ID: <20180821092507.364ef7ad@bbrezillon> (raw)
In-Reply-To: <1534835298-33043-1-git-send-email-chuanhua.han@nxp.com>
Hi Chuanhua,
On Tue, 21 Aug 2018 15:08:18 +0800
Chuanhua Han <chuanhua.han@nxp.com> wrote:
Seriously?! Still not the right prefix. So I'm giving you the full
subject line:
"spi: spi-mem: Adjust op len based on message/transfer size limitations"
> We need that to adjust the len of the 2nd transfer (called data in spi-mem)
Remove the spaces at the beginning of this line.
> if it's too long to fit in a SPI message or SPI transfer.
>
> Fixes: c36ff266dc82 ("spi: Extend the core to ease integration of SPI memory controllers")
> Cc: <stable@vger.kernel.org>
>
Remove the this blank line.
> Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
Remove my SoB. If you want you can add
Suggested-by: Boris Brezillon <boris.brezillon@bootlin.com>
though I'm not sure this is needed, since all I did was reviewing your
patch.
> Signed-off-by: Chuanhua Han <chuanhua.han@nxp.com>
> ---
> Changes in v4:
> -Rename variable name "opcode_addr_dummy_sum" to "len".
> -The comparison of "spi_max_message_size(mem->spi)" and "len" was removed.
> -Adjust their order when comparing the sizes of "spi_max_message_size(mem->spi)" and "len".
> -Changing the "unsigned long" type in the code to "size_t".
> Changes in v3:
> -Rename variable name "val" to "opcode_addr_dummy_sum".
> -Place the legitimacy of the transfer size(i.e., "spi_max_message_size(mem->spi)" and
> -"opcode_addr_dummy_sum") into "if (! ctlr - > mem_ops | |! ctlr-> mem_ops->exec_op) {"
> structure and add "spi_max_transfer_size(mem->spi) and opcode_addr_dummy_sum".
> -Adjust the formatting alignment of the code.
> -"(unsigned long)op->data.nbytes" was modified to "(unsigned long)(op->data.nbytes)".
> Changes in v2:
> -Place the adjusted transfer bytes code in spi_mem_adjust_op_size() and check
> spi_max_message_size(mem->spi) value before subtracting opcode, addr and dummy bytes.
> -Change the code from fsl-espi controller to generic code(The adjustment of spi transmission
> length was originally modified in the "drivers/spi/spi-fsl-espi.c" file, and now the adjustment
> of transfer length is made in the "drivers/spi/spi-mem.c" file).
>
> drivers/spi/spi-mem.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/drivers/spi/spi-mem.c b/drivers/spi/spi-mem.c
> index 990770d..5374606 100644
> --- a/drivers/spi/spi-mem.c
> +++ b/drivers/spi/spi-mem.c
> @@ -328,10 +328,23 @@ EXPORT_SYMBOL_GPL(spi_mem_exec_op);
> int spi_mem_adjust_op_size(struct spi_mem *mem, struct spi_mem_op *op)
> {
> struct spi_controller *ctlr = mem->spi->controller;
> + size_t len = sizeof(op->cmd.opcode) +
> + op->addr.nbytes +
> + op->dummy.nbytes;
What about David's suggestion to assign len after its declaration so that
it does not exceeds 80 chars?
>
> if (ctlr->mem_ops && ctlr->mem_ops->adjust_op_size)
> return ctlr->mem_ops->adjust_op_size(mem, op);
>
> + if (!ctlr->mem_ops || !ctlr->mem_ops->exec_op) {
> + if (len > spi_max_transfer_size(mem->spi))
> + return -EINVAL;
> +
> + op->data.nbytes = min3((size_t)(op->data.nbytes),
> + spi_max_transfer_size(mem->spi),
> + spi_max_message_size(mem->spi) -
> + len);
You should probably add:
if (!op->data.nbytes)
return -EINVAL;
> + }
> +
> return 0;
> }
> EXPORT_SYMBOL_GPL(spi_mem_adjust_op_size);
Regards,
Boris
next prev parent reply other threads:[~2018-08-21 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 7:08 [PATCH v4] mtd: spi-mem: Add the default transfer length adjustments Chuanhua Han
2018-08-21 7:25 ` Boris Brezillon [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-21 7:15 Chuanhua Han
2018-08-21 7:17 Chuanhua Han
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=20180821092507.364ef7ad@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=cheetah0585@163.com \
--cc=chuanhua.han@nxp.com \
--cc=ran.wang_1@nxp.com \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).