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,
ldewangan@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, robh@kernel.org
Subject: Re: [PATCH v6 1/3] i2c: tegra: Fix reset error handling with ACPI
Date: Thu, 10 Jul 2025 16:50:29 +0300 [thread overview]
Message-ID: <aG_FJZQjNbV-OnGc@smile.fi.intel.com> (raw)
In-Reply-To: <20250710131206.2316-2-akhilrajeev@nvidia.com>
On Thu, Jul 10, 2025 at 06:42:04PM +0530, Akhil R wrote:
> The acpi_evaluate_object() returns an ACPI error code and not
> Linux one. For the some platforms the err will have positive code
> which may be interpreted incorrectly. Use device_reset for reset
device_reset()
> control which handles it correctly.
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-07-10 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 13:12 [PATCH v6 0/3] i2c: tegra: Improve reset and DMA operations Akhil R
2025-07-10 13:12 ` [PATCH v6 1/3] i2c: tegra: Fix reset error handling with ACPI Akhil R
2025-07-10 13:50 ` Andy Shevchenko [this message]
2025-07-11 15:59 ` Andi Shyti
2025-07-10 13:12 ` [PATCH v6 2/3] i2c: tegra: Use internal reset when reset property is not available Akhil R
2025-07-10 13:53 ` Andy Shevchenko
2025-07-11 16:00 ` Andi Shyti
2025-07-14 5:22 ` Akhil R
2025-07-14 8:19 ` Andy Shevchenko
2025-07-10 13:12 ` [PATCH v6 3/3] i2c: tegra: Remove dma_sync_*() calls Akhil R
2025-07-14 20:19 ` [PATCH v6 0/3] i2c: tegra: Improve reset and DMA operations Andi Shyti
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=aG_FJZQjNbV-OnGc@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
all inboxes | Powered by JetHome®