All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@xilinx.com>
To: Jorge Ramirez-Ortiz <jorge@foundries.io>, <sjg@chromium.org>,
	<michal.simek@xilinx.com>
Cc: <bruno.thomsen@gmail.com>, <u-boot@lists.denx.de>
Subject: Re: [PATCHv2] drivers: tpm2: update reset gpio semantics
Date: Tue, 1 Jun 2021 08:43:11 +0200	[thread overview]
Message-ID: <a15cde14-883d-6f10-c6dc-d22815a2bf48@xilinx.com> (raw)
In-Reply-To: <20210601060927.30894-1-jorge@foundries.io>



On 6/1/21 8:09 AM, Jorge Ramirez-Ortiz wrote:
> Use the more generic reset-gpios propery name.
> 
> Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
> ---
>   v2: kept gpio-reset as legacy
> 
>  .../tpm2/tis-tpm2-spi.txt                     |  2 +-
>  drivers/tpm/tpm2_tis_spi.c                    | 21 ++++++++++++-------
>  2 files changed, 14 insertions(+), 9 deletions(-)
> 
> diff --git a/doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt b/doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt
> index 3a2ee4bd17..bbcd12950f 100644
> --- a/doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt
> +++ b/doc/device-tree-bindings/tpm2/tis-tpm2-spi.txt
> @@ -6,7 +6,7 @@ Required properties:
>  - reg			: SPI Chip select
>  
>  Optional properties:
> -- gpio-reset		: Reset GPIO (if not connected to the SoC reset line)

As I said you shouldn't remove this. Just extend description that it is
deprecated and reset-gpios should be used instead.

> +- reset-gpios		: Reset GPIO (if not connected to the SoC reset line)
>  - spi-max-frequency	: See spi-bus.txt
>  
>  Example:
> diff --git a/drivers/tpm/tpm2_tis_spi.c b/drivers/tpm/tpm2_tis_spi.c
> index 4b33ac8fd3..1f9f89f68f 100644
> --- a/drivers/tpm/tpm2_tis_spi.c
> +++ b/drivers/tpm/tpm2_tis_spi.c
> @@ -589,18 +589,23 @@ static int tpm_tis_spi_probe(struct udevice *dev)
>  	if (CONFIG_IS_ENABLED(DM_GPIO)) {
>  		struct gpio_desc reset_gpio;
>  
> -		ret = gpio_request_by_name(dev, "gpio-reset", 0,
> +		ret = gpio_request_by_name(dev, "reset-gpios", 0,
>  					   &reset_gpio, GPIOD_IS_OUT);
>  		if (ret) {
> -			log(LOGC_NONE, LOGL_NOTICE, "%s: missing reset GPIO\n",
> -			    __func__);
> -		} else {
> -			dm_gpio_set_value(&reset_gpio, 1);
> -			mdelay(1);
> -			dm_gpio_set_value(&reset_gpio, 0);
> +			/* legacy reset */
> +			ret = gpio_request_by_name(dev, "gpio-reset", 0,
> +						   &reset_gpio, GPIOD_IS_OUT);
> +			if (ret) {
> +				log(LOGC_NONE, LOGL_NOTICE,
> +				    "%s: missing reset GPIO\n",  __func__);
> +				goto init;
> +			}

And here it is clear that gpio-reset is used which should deprecated
that's why you should print message about it here.


>  		}
> +		dm_gpio_set_value(&reset_gpio, 1);
> +		mdelay(1);
> +		dm_gpio_set_value(&reset_gpio, 0);
>  	}

What about this to remove that goto?

ret = gpio_request_by_name(dev, "reset-gpios", 0,
			   &reset_gpio, GPIOD_IS_OUT);
if (ret) {
	/* trying legacy reset */
	ret = gpio_request_by_name(dev, "gpio-reset", 0,
				   &reset_gpio, GPIOD_IS_OUT);
	if (!ret)
		log(LOGC_NONE, LOGL_NOTICE,
		    "%s: Using deprecated gpio-reset switch to reset-gpios\n",  __func__);
}

if (!ret) {
	dm_gpio_set_value(&reset_gpio, 1);
	mdelay(1);
	dm_gpio_set_value(&reset_gpio, 0);
}

> -
> +init:
>  	/* Ensure a minimum amount of time elapsed since reset of the TPM */
>  	mdelay(drv_data->time_before_first_cmd_ms);
>  
> 

M

  reply	other threads:[~2021-06-01  6:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01  6:09 [PATCHv2] drivers: tpm2: update reset gpio semantics Jorge Ramirez-Ortiz
2021-06-01  6:43 ` Michal Simek [this message]
2021-06-01  7:35   ` Jorge Ramirez-Ortiz, Foundries
2021-06-01 10:20     ` Michal Simek
2021-06-03  9:04       ` Jorge Ramirez-Ortiz, Foundries

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=a15cde14-883d-6f10-c6dc-d22815a2bf48@xilinx.com \
    --to=michal.simek@xilinx.com \
    --cc=bruno.thomsen@gmail.com \
    --cc=jorge@foundries.io \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.