public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <sai.krishna.potthuri@amd.com>, <pratyush@kernel.org>,
	<michael@walle.cc>, <miquel.raynal@bootlin.com>, <richard@nod.at>,
	<vigneshr@ti.com>, <robh+dt@kernel.org>,
	<krzysztof.kozlowski+dt@linaro.org>
Cc: <devicetree@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <saikrishna12468@gmail.com>,
	<git@amd.com>
Subject: Re: [PATCH v3 2/2] mtd: spi-nor: Add support for flash reset
Date: Mon, 3 Oct 2022 09:43:14 +0000	[thread overview]
Message-ID: <7777b2fc-8c22-22dd-1ffd-dfe8a21ea0d4@microchip.com> (raw)
In-Reply-To: <20220908064428.2962-3-sai.krishna.potthuri@amd.com>

On 9/8/22 09:44, Sai Krishna Potthuri wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> Add support for spi-nor flash reset via GPIO controller by reading the
> reset-gpio property. If there is a valid GPIO specifier then reset will
> be performed by asserting and deasserting the GPIO using gpiod APIs
> otherwise it will not perform any operation.
> 
> Signed-off-by: Sai Krishna Potthuri <sai.krishna.potthuri@amd.com>
> Reviewed-by: Michael Walle <michael@walle.cc>
> ---
>  drivers/mtd/spi-nor/core.c | 25 +++++++++++++++++++++++++
>  1 file changed, 25 insertions(+)
> 
> diff --git a/drivers/mtd/spi-nor/core.c b/drivers/mtd/spi-nor/core.c
> index f2c64006f8d7..a78ab9bae2be 100644
> --- a/drivers/mtd/spi-nor/core.c
> +++ b/drivers/mtd/spi-nor/core.c
> @@ -2933,6 +2933,27 @@ static void spi_nor_set_mtd_info(struct spi_nor *nor)
>         mtd->_put_device = spi_nor_put_device;
>  }
> 
> +static int spi_nor_hw_reset(struct spi_nor *nor)
> +{
> +       struct gpio_desc *reset;
> +
> +       reset = devm_gpiod_get_optional(nor->dev, "reset", GPIOD_OUT_LOW);
> +       if (IS_ERR_OR_NULL(reset))
> +               return PTR_ERR_OR_ZERO(reset);
> +
> +       /*
> +        * Experimental delay values by looking at different flash device
> +        * vendors datasheets.
> +        */
> +       usleep_range(1, 5);
> +       gpiod_set_value_cansleep(reset, 1);
> +       usleep_range(100, 150);
> +       gpiod_set_value_cansleep(reset, 0);
> +       usleep_range(1000, 1200);
> +
> +       return 0;
> +}
> +
>  int spi_nor_scan(struct spi_nor *nor, const char *name,
>                  const struct spi_nor_hwcaps *hwcaps)
>  {
> @@ -2965,6 +2986,10 @@ int spi_nor_scan(struct spi_nor *nor, const char *name,
>         if (!nor->bouncebuf)
>                 return -ENOMEM;
> 
> +       ret = spi_nor_hw_reset(nor);

Should we condition the calling of this method by the absence of the "broken-flash-reset"
dt prop?

> +       if (ret)
> +               return ret;
> +
>         info = spi_nor_get_flash_info(nor, name);
>         if (IS_ERR(info))
>                 return PTR_ERR(info);
> --
> 2.17.1
> 


-- 
Cheers,
ta

  reply	other threads:[~2022-10-03  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08  6:44 [PATCH v3 0/2] mtd: spi-nor: Add flash device reset support Sai Krishna Potthuri
2022-09-08  6:44 ` [PATCH v3 1/2] dt-bindings: mtd: spi-nor: Add reset-gpios property Sai Krishna Potthuri
2022-09-08 11:05   ` Krzysztof Kozlowski
2022-09-08  6:44 ` [PATCH v3 2/2] mtd: spi-nor: Add support for flash reset Sai Krishna Potthuri
2022-10-03  9:43   ` Tudor.Ambarus [this message]
2022-10-03 10:06     ` Potthuri, Sai Krishna
2022-10-05  5:48       ` Tudor.Ambarus
2022-10-25  2:32 ` [PATCH v3 0/2] mtd: spi-nor: Add flash device reset support Tudor Ambarus
2022-10-25  2:40   ` Tudor Ambarus

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=7777b2fc-8c22-22dd-1ffd-dfe8a21ea0d4@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=git@amd.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=miquel.raynal@bootlin.com \
    --cc=pratyush@kernel.org \
    --cc=richard@nod.at \
    --cc=robh+dt@kernel.org \
    --cc=sai.krishna.potthuri@amd.com \
    --cc=saikrishna12468@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox