devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: andi.shyti@kernel.org, digetx@gmail.com, jonathanh@nvidia.com,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-tegra@vger.kernel.org, p.zabel@pengutronix.de,
	thierry.reding@gmail.com, conor+dt@kernel.org,
	devicetree@vger.kernel.org, krzk+dt@kernel.org,
	ldewangan@nvidia.com, robh@kernel.org
Subject: Re: [PATCH v5 1/3] i2c: tegra: Fix reset error handling with ACPI
Date: Wed, 2 Jul 2025 18:04:44 +0300	[thread overview]
Message-ID: <aGVKjIwRjMOMlZRF@smile.fi.intel.com> (raw)
In-Reply-To: <20250702133450.64257-1-akhilrajeev@nvidia.com>

On Wed, Jul 02, 2025 at 07:04:47PM +0530, Akhil R wrote:
> The acpi_evaluate_object() returns an ACPI error code and not the
> Linux one. For the some platforms the error will have positive code
> which may be interpreted incorrectly. Use ACPI_FAILURE() to determine
> the failure and return the error. Also move the reset to a separate
> function to handle this better.

...

> +static int tegra_i2c_reset(struct tegra_i2c_dev *i2c_dev)
> +{
> +	acpi_handle handle = ACPI_HANDLE(i2c_dev->dev);
> +	int err;
> +
> +	if (handle) {
> +		err = acpi_evaluate_object(handle, "_RST", NULL, NULL);
> +		if (ACPI_FAILURE(err))
> +			return -EIO;
> +
> +		return 0;
> +	}
> +
> +	return reset_control_reset(i2c_dev->rst);


It's better to be written other way around:

	acpi_handle handle;
	int err;

	handle = ACPI_HANDLE(i2c_dev->dev);
	if (!handle)
		return reset_control_reset(i2c_dev->rst);

	err = acpi_evaluate_object(handle, "_RST", NULL, NULL);
	if (ACPI_FAILURE(err))
		return -EIO;

	return 0;

> +}

Other than that, LGTM,

Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

...

> +	err = tegra_i2c_reset(i2c_dev);
>  	WARN_ON_ONCE(err);

Suggestion to improve in a separate change in the future:

Add a comment explaining why we WARN() here. I.o.w. why this condition
is so critical that we need to WARN().

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2025-07-02 15:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02 13:34 [PATCH v5 1/3] i2c: tegra: Fix reset error handling with ACPI Akhil R
2025-07-02 13:34 ` [PATCH v5 2/3] i2c: tegra: make reset an optional property Akhil R
2025-07-02 15:11   ` Andy Shevchenko
2025-07-03 16:02   ` kernel test robot
2025-07-02 13:34 ` [PATCH v5 3/3] i2c: tegra: Remove dma_sync_*() calls Akhil R
2025-07-02 15:24   ` Andy Shevchenko
2025-07-02 15:04 ` Andy Shevchenko [this message]
2025-07-02 15:13   ` [PATCH v5 1/3] i2c: tegra: Fix reset error handling with ACPI Andy Shevchenko
2025-07-02 17:10     ` Akhil R
2025-07-03  8:31       ` Philipp Zabel
2025-07-03 14:11         ` Andy Shevchenko
2025-07-04  6:47           ` Akhil R

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=aGVKjIwRjMOMlZRF@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=akhilrajeev@nvidia.com \
    --cc=andi.shyti@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.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;
as well as URLs for NNTP newsgroup(s).