From: Boris Brezillon <boris.brezillon@collabora.com>
To: <patrice.chotard@foss.st.com>
Cc: Mark Brown <broonie@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>
Subject: Re: [PATCH v2 1/3] spi: spi-mem: add automatic poll status functions
Date: Mon, 17 May 2021 09:41:40 +0200 [thread overview]
Message-ID: <20210517094140.53cb643a@collabora.com> (raw)
In-Reply-To: <20210507131756.17028-2-patrice.chotard@foss.st.com>
On Fri, 7 May 2021 15:17:54 +0200
<patrice.chotard@foss.st.com> wrote:
> +/**
> + * spi_mem_poll_status() - Poll memory device status
> + * @mem: SPI memory device
> + * @op: the memory operation to execute
> + * @mask: status bitmask to ckeck
> + * @match: (status & mask) expected value
> + * @timeout_ms: timeout in milliseconds
> + *
> + * This function send a polling status request to the controller driver
> + *
> + * Return: 0 in case of success, -ETIMEDOUT in case of error,
> + * -EOPNOTSUPP if not supported.
> + */
> +int spi_mem_poll_status(struct spi_mem *mem,
> + const struct spi_mem_op *op,
> + u16 mask, u16 match, u16 timeout_ms)
Maybe you should pass a delay_us too, to poll the status at the right
rate in the SW-based case (can also be used by drivers if they need to
configure the polling rate). You could also add an initial_delay_us to
avoid polling the status too early: an erase operation will take longer
than a write which will take longer than a read. No need to check the
status just after issuing the command, especially if the polling is
done in SW. Those 2 arguments should also be passed to the driver.
> +{
> + struct spi_controller *ctlr = mem->spi->controller;
> + unsigned long ms;
> + int ret = -EOPNOTSUPP;
> + int exec_op_ret;
> + u16 *status;
> +
> + if (!spi_mem_supports_op(mem, op))
> + return ret;
> +
> + if (ctlr->mem_ops && ctlr->mem_ops->poll_status) {
> + ret = spi_mem_access_start(mem);
> + if (ret)
> + return ret;
> +
> + reinit_completion(&ctlr->xfer_completion);
> +
> + ret = ctlr->mem_ops->poll_status(mem, op, mask, match,
> + timeout_ms);
> +
> + ms = wait_for_completion_timeout(&ctlr->xfer_completion,
> + msecs_to_jiffies(timeout_ms));
> +
> + spi_mem_access_end(mem);
> + if (!ms)
> + return -ETIMEDOUT;
> + } else {
> + status = (u16 *)op->data.buf.in;
> + ret = read_poll_timeout(spi_mem_exec_op, exec_op_ret,
> + ((*status) & mask) == match, 20,
> + timeout_ms * 1000, false, mem, op);
> + if (exec_op_ret)
> + return exec_op_ret;
> + }
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(spi_mem_poll_status);
> +
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: <patrice.chotard@foss.st.com>
Cc: Mark Brown <broonie@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>
Subject: Re: [PATCH v2 1/3] spi: spi-mem: add automatic poll status functions
Date: Mon, 17 May 2021 09:41:40 +0200 [thread overview]
Message-ID: <20210517094140.53cb643a@collabora.com> (raw)
In-Reply-To: <20210507131756.17028-2-patrice.chotard@foss.st.com>
On Fri, 7 May 2021 15:17:54 +0200
<patrice.chotard@foss.st.com> wrote:
> +/**
> + * spi_mem_poll_status() - Poll memory device status
> + * @mem: SPI memory device
> + * @op: the memory operation to execute
> + * @mask: status bitmask to ckeck
> + * @match: (status & mask) expected value
> + * @timeout_ms: timeout in milliseconds
> + *
> + * This function send a polling status request to the controller driver
> + *
> + * Return: 0 in case of success, -ETIMEDOUT in case of error,
> + * -EOPNOTSUPP if not supported.
> + */
> +int spi_mem_poll_status(struct spi_mem *mem,
> + const struct spi_mem_op *op,
> + u16 mask, u16 match, u16 timeout_ms)
Maybe you should pass a delay_us too, to poll the status at the right
rate in the SW-based case (can also be used by drivers if they need to
configure the polling rate). You could also add an initial_delay_us to
avoid polling the status too early: an erase operation will take longer
than a write which will take longer than a read. No need to check the
status just after issuing the command, especially if the polling is
done in SW. Those 2 arguments should also be passed to the driver.
> +{
> + struct spi_controller *ctlr = mem->spi->controller;
> + unsigned long ms;
> + int ret = -EOPNOTSUPP;
> + int exec_op_ret;
> + u16 *status;
> +
> + if (!spi_mem_supports_op(mem, op))
> + return ret;
> +
> + if (ctlr->mem_ops && ctlr->mem_ops->poll_status) {
> + ret = spi_mem_access_start(mem);
> + if (ret)
> + return ret;
> +
> + reinit_completion(&ctlr->xfer_completion);
> +
> + ret = ctlr->mem_ops->poll_status(mem, op, mask, match,
> + timeout_ms);
> +
> + ms = wait_for_completion_timeout(&ctlr->xfer_completion,
> + msecs_to_jiffies(timeout_ms));
> +
> + spi_mem_access_end(mem);
> + if (!ms)
> + return -ETIMEDOUT;
> + } else {
> + status = (u16 *)op->data.buf.in;
> + ret = read_poll_timeout(spi_mem_exec_op, exec_op_ret,
> + ((*status) & mask) == match, 20,
> + timeout_ms * 1000, false, mem, op);
> + if (exec_op_ret)
> + return exec_op_ret;
> + }
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(spi_mem_poll_status);
> +
WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <boris.brezillon@collabora.com>
To: <patrice.chotard@foss.st.com>
Cc: Mark Brown <broonie@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-mtd@lists.infradead.org>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
<linux-spi@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <christophe.kerello@foss.st.com>
Subject: Re: [PATCH v2 1/3] spi: spi-mem: add automatic poll status functions
Date: Mon, 17 May 2021 09:41:40 +0200 [thread overview]
Message-ID: <20210517094140.53cb643a@collabora.com> (raw)
In-Reply-To: <20210507131756.17028-2-patrice.chotard@foss.st.com>
On Fri, 7 May 2021 15:17:54 +0200
<patrice.chotard@foss.st.com> wrote:
> +/**
> + * spi_mem_poll_status() - Poll memory device status
> + * @mem: SPI memory device
> + * @op: the memory operation to execute
> + * @mask: status bitmask to ckeck
> + * @match: (status & mask) expected value
> + * @timeout_ms: timeout in milliseconds
> + *
> + * This function send a polling status request to the controller driver
> + *
> + * Return: 0 in case of success, -ETIMEDOUT in case of error,
> + * -EOPNOTSUPP if not supported.
> + */
> +int spi_mem_poll_status(struct spi_mem *mem,
> + const struct spi_mem_op *op,
> + u16 mask, u16 match, u16 timeout_ms)
Maybe you should pass a delay_us too, to poll the status at the right
rate in the SW-based case (can also be used by drivers if they need to
configure the polling rate). You could also add an initial_delay_us to
avoid polling the status too early: an erase operation will take longer
than a write which will take longer than a read. No need to check the
status just after issuing the command, especially if the polling is
done in SW. Those 2 arguments should also be passed to the driver.
> +{
> + struct spi_controller *ctlr = mem->spi->controller;
> + unsigned long ms;
> + int ret = -EOPNOTSUPP;
> + int exec_op_ret;
> + u16 *status;
> +
> + if (!spi_mem_supports_op(mem, op))
> + return ret;
> +
> + if (ctlr->mem_ops && ctlr->mem_ops->poll_status) {
> + ret = spi_mem_access_start(mem);
> + if (ret)
> + return ret;
> +
> + reinit_completion(&ctlr->xfer_completion);
> +
> + ret = ctlr->mem_ops->poll_status(mem, op, mask, match,
> + timeout_ms);
> +
> + ms = wait_for_completion_timeout(&ctlr->xfer_completion,
> + msecs_to_jiffies(timeout_ms));
> +
> + spi_mem_access_end(mem);
> + if (!ms)
> + return -ETIMEDOUT;
> + } else {
> + status = (u16 *)op->data.buf.in;
> + ret = read_poll_timeout(spi_mem_exec_op, exec_op_ret,
> + ((*status) & mask) == match, 20,
> + timeout_ms * 1000, false, mem, op);
> + if (exec_op_ret)
> + return exec_op_ret;
> + }
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(spi_mem_poll_status);
> +
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-05-17 7:42 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 13:17 [PATCH v2 0/3] MTD: spinand: Add spi_mem_poll_status() support patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-07 13:17 ` [PATCH v2 1/3] spi: spi-mem: add automatic poll status functions patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-08 7:55 ` Boris Brezillon
2021-05-08 7:55 ` Boris Brezillon
2021-05-08 7:55 ` Boris Brezillon
2021-05-10 8:46 ` Patrice CHOTARD
2021-05-10 8:46 ` Patrice CHOTARD
2021-05-10 8:46 ` Patrice CHOTARD
2021-05-10 9:22 ` Boris Brezillon
2021-05-10 9:22 ` Boris Brezillon
2021-05-10 9:22 ` Boris Brezillon
2021-05-17 7:29 ` Patrice CHOTARD
2021-05-17 7:29 ` Patrice CHOTARD
2021-05-17 7:29 ` Patrice CHOTARD
2021-05-17 7:41 ` Boris Brezillon [this message]
2021-05-17 7:41 ` Boris Brezillon
2021-05-17 7:41 ` Boris Brezillon
2021-05-17 9:24 ` Patrice CHOTARD
2021-05-17 9:24 ` Patrice CHOTARD
2021-05-17 9:24 ` Patrice CHOTARD
2021-05-17 11:25 ` Boris Brezillon
2021-05-17 11:25 ` Boris Brezillon
2021-05-17 11:25 ` Boris Brezillon
2021-05-17 11:59 ` Patrice CHOTARD
2021-05-17 11:59 ` Patrice CHOTARD
2021-05-17 11:59 ` Patrice CHOTARD
2021-05-17 12:24 ` Boris Brezillon
2021-05-17 12:24 ` Boris Brezillon
2021-05-17 12:24 ` Boris Brezillon
2021-05-17 12:04 ` Patrice CHOTARD
2021-05-17 12:04 ` Patrice CHOTARD
2021-05-17 12:04 ` Patrice CHOTARD
2021-05-07 13:17 ` [PATCH v2 2/3] mtd: spinand: use the spi-mem poll status APIs patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-07 13:17 ` [PATCH v2 3/3] spi: stm32-qspi: add automatic poll status feature patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-07 13:17 ` patrice.chotard
2021-05-07 19:29 ` kernel test robot
2021-05-07 19:29 ` kernel test robot
2021-05-07 19:29 ` kernel test robot
2021-05-07 19:29 ` kernel test robot
2021-05-07 22:16 ` kernel test robot
2021-05-07 22:16 ` kernel test robot
2021-05-07 22:16 ` kernel test robot
2021-05-07 22:16 ` kernel test robot
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=20210517094140.53cb643a@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=christophe.kerello@foss.st.com \
--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=linux-stm32@st-md-mailman.stormreply.com \
--cc=miquel.raynal@bootlin.com \
--cc=patrice.chotard@foss.st.com \
--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 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.