linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: linux-crypto@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linus.walleij@linaro.org,
	joakim.bech@linaro.org,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH 1/5] i2c: acpi: permit bus speed to be discovered after enumeration
Date: Thu, 2 May 2019 11:08:18 +0300	[thread overview]
Message-ID: <20190502080818.GT26516@lahna.fi.intel.com> (raw)
In-Reply-To: <20190430162910.16771-2-ard.biesheuvel@linaro.org>

On Tue, Apr 30, 2019 at 06:29:05PM +0200, Ard Biesheuvel wrote:
> Currently, the I2C ACPI enumeration code only permits the max bus rate
> to be discovered before enumerating the slaves on the bus. In some
> cases, drivers for slave devices may require this information, e.g.,
> some ATmel crypto drivers need to generate a so-called wake token
> of a fixed duration, regardless of the bus rate.
> 
> So tweak the code so i2c_acpi_lookup_speed() is able to obtain this
> information after enumeration as well.
> 
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>

Looks fine by me,

Acked-by: Mika Westerberg <mika.westerberg@linux.intel.com>

Adding Jarkko just in case I missed something.

> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
>  drivers/i2c/i2c-core-acpi.c | 6 ++++--
>  1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/i2c/i2c-core-acpi.c b/drivers/i2c/i2c-core-acpi.c
> index 272800692088..7240cc07abb4 100644
> --- a/drivers/i2c/i2c-core-acpi.c
> +++ b/drivers/i2c/i2c-core-acpi.c
> @@ -115,8 +115,7 @@ static int i2c_acpi_do_lookup(struct acpi_device *adev,
>  	struct list_head resource_list;
>  	int ret;
>  
> -	if (acpi_bus_get_status(adev) || !adev->status.present ||
> -	    acpi_device_enumerated(adev))
> +	if (acpi_bus_get_status(adev) || !adev->status.present)
>  		return -EINVAL;
>  
>  	if (acpi_match_device_ids(adev, i2c_acpi_ignored_device_ids) == 0)
> @@ -151,6 +150,9 @@ static int i2c_acpi_get_info(struct acpi_device *adev,
>  	lookup.info = info;
>  	lookup.index = -1;
>  
> +	if (acpi_device_enumerated(adev))
> +		return -EINVAL;
> +
>  	ret = i2c_acpi_do_lookup(adev, &lookup);
>  	if (ret)
>  		return ret;
> -- 
> 2.20.1

  reply	other threads:[~2019-05-02  8:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-30 16:29 [PATCH 0/5] synquacer - wire up Atmel SHA204A as RNG in DT and ACPI mode Ard Biesheuvel
2019-04-30 16:29 ` [PATCH 1/5] i2c: acpi: permit bus speed to be discovered after enumeration Ard Biesheuvel
2019-05-02  8:08   ` Mika Westerberg [this message]
2019-04-30 16:29 ` [PATCH 2/5] crypto: atmel-ecc: add support for ACPI probing on non-AT91 platforms Ard Biesheuvel
2019-04-30 16:29 ` [PATCH 3/5] crypto: atmel-ecc: factor out code that can be shared Ard Biesheuvel
2019-05-09 20:42   ` Linus Walleij
2019-04-30 16:29 ` [PATCH 4/5] crypto: atmel-i2c: add support for SHA204A random number generator Ard Biesheuvel
2019-05-09 20:44   ` Linus Walleij
2019-04-30 16:29 ` [PATCH 5/5] dt-bindings: add Atmel SHA204A I2C crypto processor Ard Biesheuvel
2019-05-09 20:44   ` Linus Walleij
2019-05-16 16:06   ` Ard Biesheuvel
2019-05-24 13:12   ` Rob Herring
2019-05-24 13:15     ` Ard Biesheuvel
2019-05-24 13:36       ` Rob Herring

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=20190502080818.GT26516@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=joakim.bech@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@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).