From: Wolfram Sang <wsa@kernel.org>
To: Evan Green <evgreen@chromium.org>
Cc: Peter Rosin <peda@axentia.se>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Peter Korsgaard <peter.korsgaard@barco.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v3 2/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land
Date: Sun, 17 Jan 2021 12:54:26 +0100 [thread overview]
Message-ID: <20210117115426.GH1983@ninjato> (raw)
In-Reply-To: <20201118153951.RESEND.v3.2.Idef164c23d326f5e5edecfc5d3eb2a68fcf18be1@changeid>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
On Wed, Nov 18, 2020 at 03:40:25PM -0800, Evan Green wrote:
> Enable i2c-mux-gpio devices to be defined via ACPI. The idle-state
> property translates directly to a fwnode_property_*() call. The child
> reg property translates naturally into _ADR in ACPI.
>
> The i2c-parent binding is a relic from the days when the bindings
> dictated that all direct children of an I2C controller had to be I2C
> devices. These days that's no longer required. The i2c-mux can sit as a
> direct child of its parent controller, which is where it makes the most
> sense from a hardware description perspective. For the ACPI
> implementation we'll assume that's always how the i2c-mux-gpio is
> instantiated.
>
> Signed-off-by: Evan Green <evgreen@chromium.org>
Applied to for-next, thanks! The code Andy mentioned can still be
refactored later if new ACPI helpers appear in the future.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-01-17 11:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 23:40 [RESEND PATCH v3 0/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land Evan Green
2020-11-18 23:40 ` [RESEND PATCH v3 1/2] i2c: i2c-mux-gpio: Factor out pdev->dev in _probe_dt() Evan Green
2021-01-15 9:30 ` Peter Rosin
2021-01-17 11:53 ` Wolfram Sang
2020-11-18 23:40 ` [RESEND PATCH v3 2/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land Evan Green
2020-11-19 15:25 ` Andy Shevchenko
2020-11-20 18:59 ` Evan Green
2020-11-30 19:11 ` Evan Green
2020-12-09 23:03 ` Evan Green
2021-01-05 10:25 ` Wolfram Sang
2021-01-14 18:17 ` Evan Green
2021-01-14 19:53 ` Wolfram Sang
2021-01-15 9:29 ` Peter Rosin
2021-01-19 12:10 ` Andy Shevchenko
2021-01-17 11:54 ` Wolfram Sang [this message]
2021-01-17 17:15 ` Evan Green
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=20210117115426.GH1983@ninjato \
--to=wsa@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=evgreen@chromium.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--cc=peter.korsgaard@barco.com \
--cc=rdunlap@infradead.org \
/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).