Messages in this thread | | | Date | Sun, 17 Jan 2021 12:54:26 +0100 | From | Wolfram Sang <> | Subject | Re: [RESEND PATCH v3 2/2] i2c: i2c-mux-gpio: Enable this driver in ACPI land |
| |
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.
[unhandled content-type:application/pgp-signature] | |