mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Akhil R <akhilrajeev@nvidia.com>
To: <andi.shyti@kernel.org>
Cc: <akhilrajeev@nvidia.com>, <andriy.shevchenko@linux.intel.com>,
	<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<digetx@gmail.com>, <jonathanh@nvidia.com>, <krzk+dt@kernel.org>,
	<ldewangan@nvidia.com>, <linux-i2c@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<p.zabel@pengutronix.de>, <robh@kernel.org>,
	<thierry.reding@gmail.com>
Subject: Re: [PATCH v6 2/3] i2c: tegra: Use internal reset when reset property is not available
Date: Mon, 14 Jul 2025 10:52:25 +0530	[thread overview]
Message-ID: <20250714052226.72876-1-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <iqx5wzywy2x66n2y36mx4fckrr7wy4lqu3dsejcovghjtmgoz7@zwslylpivy3q>

On Fri, 11 Jul 2025 18:00:45 +0200, Andi Shyti wrote:

...

>> I would perhaps expand the comment here to explain ENOENT check and what do we
>> do in this case. (Note, no rewriting of the existing, just adding a paragraph)
>> 
>> 	*
>> 	* In case ... we compare with -ENOENT ...
>> 	* ...
>> 	*/
>
> If you write it here I can expand your comment before merging.
>
> Or if you prefer sending a v7 is still fine.

Hi Andi,

I thought to update the comments as below. Please let me know if this can be
folded in. I can send a v7 if that is easier to merge.

	/*
	 * Reset the controller before initializing it.
	 * In case if device_reset() returns -ENOENT, i.e. when the reset is
	 * not available, the internal software reset will be used if it is
	 * supported by the controller.
	 */
	err = device_reset(i2c_dev->dev);
	if (err == -ENOENT)
		err = tegra_i2c_master_reset(i2c_dev);

	/*
	 * The reset shouldn't ever fail in practice. The failure will be a
	 * sign of a severe problem that needs to be resolved. Still we don't
	 * want to fail the initialization completely because this may break
	 * kernel boot up since voltage regulators use I2C. Hence, we will
	 * emit a noisy warning on error, which won't stay unnoticed and
	 * won't hose machine entirely.
	 */
	WARN_ON_ONCE(err);


Thanks & Regards,
Akhil

  reply	other threads:[~2025-07-14  5:22 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
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 [this message]
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=20250714052226.72876-1-akhilrajeev@nvidia.com \
    --to=akhilrajeev@nvidia.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --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®