[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aYKG5k5-6ll_RzQz@smile.fi.intel.com>
Date: Wed, 4 Feb 2026 01:38:14 +0200
From: Andy Shevchenko <andriy.shevchenko@...el.com>
To: Abdurrahman Hussain <abdurrahman@...thop.ai>
Cc: Michal Simek <michal.simek@....com>, Andi Shyti <andi.shyti@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
linux-arm-kernel@...ts.infradead.org, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v9 7/7] i2c: xiic: skip input clock setup on non-OF
systems
On Tue, Feb 03, 2026 at 10:38:51AM -0800, Abdurrahman Hussain wrote:
> > On Feb 3, 2026, at 7:46 AM, Andy Shevchenko <andriy.shevchenko@...el.com> wrote:
> > On Mon, Feb 02, 2026 at 08:37:24PM +0000, Abdurrahman Hussain via B4 Relay wrote:
> >> Currently Linux does not implement ACPI ClockInput to describe clock
> >
> > ClockInput() resource
> >
> >> resources, unlike DT. However the xiic driver is happy if something
> >> magically enables the clock before the driver probes, and does not
> >> turn it off again. The clock should always be considered optional for
> >> ACPI.
>
> I just used the wording provided earlier by Andrew verbatim. But can change
> to the following if you insist:
I do not alter the wording, I correct the mention of the respective resource.
And yes, I insist.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists