All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>,
	tudor.ambarus@microchip.com, p.yadav@ti.com, michael@walle.cc,
	miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
	broonie@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org
Cc: <linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>,
	<linux-mips@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <aidanmacdonald.0x0@gmail.com>,
	<tmn505@gmail.com>, <paul@crapouillou.net>,
	<dongsheng.qiu@ingenic.com>, <aric.pzqi@ingenic.com>,
	<rick.tyliu@ingenic.com>, <jinghui.liu@ingenic.com>,
	<sernia.zhou@foxmail.com>, <reimu@sudomaker.com>
Subject: Re: [PATCH 1/3] mtd: spi-nor: Use the spi-mem poll status APIs.
Date: Sat, 23 Jul 2022 11:30:16 +0300	[thread overview]
Message-ID: <1926ce77-6de0-0d87-d676-6ae93fa5c527@omp.ru> (raw)
In-Reply-To: <1658508510-15400-2-git-send-email-zhouyanjie@wanyeetech.com>

Hello!

On 7/22/22 7:48 PM, 周琰杰 (Zhou Yanjie) wrote:

> With advanced controllers (such as Ingenic SFC), it is possible to poll
> the status register of the device. This could be done to offload the CPU
> during a erase or write operation. Make use of spi-mem poll status APIs
> to handle this feature.
> 
> Previously, when erasing large area (e.g. 32MiB), in non-offload case,
> CPU load could reach ~90% and would generate ~3.92 million interrupts,
> now it decrease to ~15% CPU load and 0.15 million interrupts.
> 
> This should also fix the high CPU usage for system which don't have a
> dedicated poll status block logic (decrease to ~80% CPU load and ~1.61
> million interrupts.).
> 
> Signed-off-by: 周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com>
> ---
>  drivers/mtd/spi-nor/core.c | 42 ++++++++++++++++++++++++++++++++----------
>  1 file changed, 32 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/mtd/spi-nor/core.c b/drivers/mtd/spi-nor/core.c
> index 502967c..6a31132 100644
> --- a/drivers/mtd/spi-nor/core.c
> +++ b/drivers/mtd/spi-nor/core.c
> @@ -617,19 +617,41 @@ static int spi_nor_wait_till_ready_with_timeout(struct spi_nor *nor,
>  	unsigned long deadline;
>  	int timeout = 0, ret;
>  
> -	deadline = jiffies + timeout_jiffies;
> +	if (nor->spimem && !nor->params->ready) {
> +		struct spi_mem_op op = SPI_MEM_OP(SPI_MEM_OP_CMD(SPINOR_OP_RDSR, 0),
> +						       SPI_MEM_OP_NO_ADDR,
> +						       SPI_MEM_OP_NO_DUMMY,
> +						       SPI_MEM_OP_DATA_IN(1, nor->bouncebuf, 0));

   Strange indentation...

[...]
> +		return spi_mem_poll_status(nor->spimem, &op, SR_WIP, 0, 0, 10,
> +						       jiffies_to_msecs(timeout_jiffies));

   Here as well...

[...]

MBR, Sergey

WARNING: multiple messages have this Message-ID (diff)
From: Sergey Shtylyov <s.shtylyov@omp.ru>
To: "周琰杰 (Zhou Yanjie)" <zhouyanjie@wanyeetech.com>,
	tudor.ambarus@microchip.com, p.yadav@ti.com, michael@walle.cc,
	miquel.raynal@bootlin.com, richard@nod.at, vigneshr@ti.com,
	broonie@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org
Cc: <linux-mtd@lists.infradead.org>, <linux-spi@vger.kernel.org>,
	<linux-mips@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <aidanmacdonald.0x0@gmail.com>,
	<tmn505@gmail.com>, <paul@crapouillou.net>,
	<dongsheng.qiu@ingenic.com>, <aric.pzqi@ingenic.com>,
	<rick.tyliu@ingenic.com>, <jinghui.liu@ingenic.com>,
	<sernia.zhou@foxmail.com>, <reimu@sudomaker.com>
Subject: Re: [PATCH 1/3] mtd: spi-nor: Use the spi-mem poll status APIs.
Date: Sat, 23 Jul 2022 11:30:16 +0300	[thread overview]
Message-ID: <1926ce77-6de0-0d87-d676-6ae93fa5c527@omp.ru> (raw)
In-Reply-To: <1658508510-15400-2-git-send-email-zhouyanjie@wanyeetech.com>

Hello!

On 7/22/22 7:48 PM, 周琰杰 (Zhou Yanjie) wrote:

> With advanced controllers (such as Ingenic SFC), it is possible to poll
> the status register of the device. This could be done to offload the CPU
> during a erase or write operation. Make use of spi-mem poll status APIs
> to handle this feature.
> 
> Previously, when erasing large area (e.g. 32MiB), in non-offload case,
> CPU load could reach ~90% and would generate ~3.92 million interrupts,
> now it decrease to ~15% CPU load and 0.15 million interrupts.
> 
> This should also fix the high CPU usage for system which don't have a
> dedicated poll status block logic (decrease to ~80% CPU load and ~1.61
> million interrupts.).
> 
> Signed-off-by: 周琰杰 (Zhou Yanjie) <zhouyanjie@wanyeetech.com>
> ---
>  drivers/mtd/spi-nor/core.c | 42 ++++++++++++++++++++++++++++++++----------
>  1 file changed, 32 insertions(+), 10 deletions(-)
> 
> diff --git a/drivers/mtd/spi-nor/core.c b/drivers/mtd/spi-nor/core.c
> index 502967c..6a31132 100644
> --- a/drivers/mtd/spi-nor/core.c
> +++ b/drivers/mtd/spi-nor/core.c
> @@ -617,19 +617,41 @@ static int spi_nor_wait_till_ready_with_timeout(struct spi_nor *nor,
>  	unsigned long deadline;
>  	int timeout = 0, ret;
>  
> -	deadline = jiffies + timeout_jiffies;
> +	if (nor->spimem && !nor->params->ready) {
> +		struct spi_mem_op op = SPI_MEM_OP(SPI_MEM_OP_CMD(SPINOR_OP_RDSR, 0),
> +						       SPI_MEM_OP_NO_ADDR,
> +						       SPI_MEM_OP_NO_DUMMY,
> +						       SPI_MEM_OP_DATA_IN(1, nor->bouncebuf, 0));

   Strange indentation...

[...]
> +		return spi_mem_poll_status(nor->spimem, &op, SR_WIP, 0, 0, 10,
> +						       jiffies_to_msecs(timeout_jiffies));

   Here as well...

[...]

MBR, Sergey

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2022-07-23  8:30 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 16:48 [PATCH 0/3] Add SFC support for Ingenic SoCs 周琰杰 (Zhou Yanjie)
2022-07-22 16:48 ` 周琰杰 (Zhou Yanjie)
2022-07-22 16:48 ` [PATCH 1/3] mtd: spi-nor: Use the spi-mem poll status APIs 周琰杰 (Zhou Yanjie)
2022-07-22 16:48   ` 周琰杰 (Zhou Yanjie)
2022-07-23  8:30   ` Sergey Shtylyov [this message]
2022-07-23  8:30     ` Sergey Shtylyov
2022-07-22 16:48 ` [PATCH 2/3] dt-bindings: SPI: Add Ingenic SFC bindings 周琰杰 (Zhou Yanjie)
2022-07-22 16:48   ` 周琰杰 (Zhou Yanjie)
2022-07-22 17:46   ` Krzysztof Kozlowski
2022-07-22 17:46     ` Krzysztof Kozlowski
2022-07-23 16:50     ` Zhou Yanjie
2022-07-23 16:50       ` Zhou Yanjie
2022-07-23 17:43       ` Krzysztof Kozlowski
2022-07-23 17:43         ` Krzysztof Kozlowski
2022-07-23 18:47         ` Mike Yang
2022-07-23 18:47           ` Mike Yang
2022-07-23 19:27           ` Mark Brown
2022-07-23 19:27             ` Mark Brown
2022-07-23 20:07             ` Krzysztof Kozlowski
2022-07-23 20:07               ` Krzysztof Kozlowski
2022-07-23 20:49               ` Mike Yang
2022-07-23 20:49                 ` Mike Yang
2022-07-24 15:33                 ` Zhou Yanjie
2022-07-24 15:33                   ` Zhou Yanjie
2022-07-25 18:30                 ` Rob Herring
2022-07-25 18:30                   ` Rob Herring
2022-07-23 20:05           ` Krzysztof Kozlowski
2022-07-23 20:05             ` Krzysztof Kozlowski
2022-07-24 14:52             ` Zhou Yanjie
2022-07-24 14:52               ` Zhou Yanjie
2022-07-22 22:44   ` Rob Herring
2022-07-22 22:44     ` Rob Herring
2022-07-22 16:48 ` [PATCH 3/3] SPI: Ingenic: Add SFC support for Ingenic SoCs 周琰杰 (Zhou Yanjie)
2022-07-22 16:48   ` 周琰杰 (Zhou Yanjie)
2022-07-22 18:07   ` Krzysztof Kozlowski
2022-07-22 18:07     ` Krzysztof Kozlowski
2022-07-23 16:53     ` Zhou Yanjie
2022-07-23 16:53       ` Zhou Yanjie
2022-07-22 18:38   ` Mark Brown
2022-07-22 18:38     ` Mark Brown
2022-07-23 17:06     ` Zhou Yanjie
2022-07-23 17:06       ` Zhou Yanjie
2022-07-23 19:32       ` Mark Brown
2022-07-23 19:32         ` Mark Brown
2022-07-24  1:24         ` Zhou Yanjie
2022-07-24  1:24           ` Zhou Yanjie
2022-07-22 20:03   ` Paul Cercueil
2022-07-22 20:03     ` Paul Cercueil
2022-07-23 17:26     ` Zhou Yanjie
2022-07-23 17:26       ` Zhou Yanjie
2022-07-23 20:24       ` Paul Cercueil
2022-07-23 20:24         ` Paul Cercueil
2022-07-24 15:29         ` Zhou Yanjie
2022-07-24 15:29           ` Zhou Yanjie
2022-07-23 15:15   ` Christophe JAILLET
2022-07-23 15:15     ` Christophe JAILLET
2022-07-23 15:15     ` Christophe JAILLET
2022-07-24  1:22     ` Zhou Yanjie
2022-07-24  1:22       ` Zhou Yanjie
2022-07-24  0:43   ` kernel test robot
2022-07-24  0:43     ` kernel test robot
2022-07-24  1:28     ` Vanessa Page
2022-07-24  1:28       ` Vanessa Page
2022-07-25 16:58     ` Vanessa Page
2022-07-23 14:47 ` [PATCH 0/3] " Tomasz Maciej Nowak
2022-07-23 14:47   ` Tomasz Maciej Nowak
2022-07-24  1:25   ` Zhou Yanjie
2022-07-24  1:25     ` Zhou Yanjie
2022-07-24  1:28     ` Vanessa Page
2022-07-24  1:28       ` Vanessa Page
2022-07-24  1:28     ` Vanessa Page
2022-07-24  1:28       ` Vanessa Page
2022-07-24  1:30     ` Vanessa Page
2022-07-24  1:30       ` Vanessa Page
2022-07-24  1:32       ` Vee Page
2022-07-24  1:32         ` Vee Page
2022-07-26  6:13         ` Vee Page
2022-07-26  6:13           ` Vee Page

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=1926ce77-6de0-0d87-d676-6ae93fa5c527@omp.ru \
    --to=s.shtylyov@omp.ru \
    --cc=aidanmacdonald.0x0@gmail.com \
    --cc=aric.pzqi@ingenic.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dongsheng.qiu@ingenic.com \
    --cc=jinghui.liu@ingenic.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=p.yadav@ti.com \
    --cc=paul@crapouillou.net \
    --cc=reimu@sudomaker.com \
    --cc=richard@nod.at \
    --cc=rick.tyliu@ingenic.com \
    --cc=robh+dt@kernel.org \
    --cc=sernia.zhou@foxmail.com \
    --cc=tmn505@gmail.com \
    --cc=tudor.ambarus@microchip.com \
    --cc=vigneshr@ti.com \
    --cc=zhouyanjie@wanyeetech.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.