[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YxvngIKCXUieZfxC@google.com>
Date: Fri, 9 Sep 2022 18:25:20 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Raul Rangel <rrangel@...omium.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Hans de Goede <hdegoede@...hat.com>,
Linux ACPI <linux-acpi@...r.kernel.org>,
linux-input <linux-input@...r.kernel.org>,
"Limonciello, Mario" <mario.limonciello@....com>,
Tim Van Patten <timvp@...gle.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Wolfram Sang <wsa@...nel.org>,
"open list:I2C SUBSYSTEM HOST DRIVERS" <linux-i2c@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 4/8] i2c: acpi: Use ACPI GPIO wake capability bit to set
wake_irq
On Fri, Sep 09, 2022 at 12:47:11PM -0600, Raul Rangel wrote:
> It looks like `i2c_acpi_get_irq` and `platform_get_irq_optional` are
> doing pretty much the same thing. Can we replace `i2c_acpi_get_irq`
> and switch over to `platform_get_irq_optional`? Is it possible to get
> a `platform_device` from an `i2c_client`?
No, they are completely different objects.
struct device
/ | \
platform_device i2c_client spi_device ...
Also, please no top-posting on kernel mailing lists.
Thanks.
--
Dmitry
Powered by blists - more mailing lists