forked from Minki/linux
98b2b712bc
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> Acked-by: Peter Rosin <peda@axentia.se> Signed-off-by: Wolfram Sang <wsa@kernel.org> |
||
|---|---|---|
| .. | ||
| i2c-arb-gpio-challenge.c | ||
| i2c-demux-pinctrl.c | ||
| i2c-mux-gpio.c | ||
| i2c-mux-gpmux.c | ||
| i2c-mux-ltc4306.c | ||
| i2c-mux-mlxcpld.c | ||
| i2c-mux-pca954x.c | ||
| i2c-mux-pca9541.c | ||
| i2c-mux-pinctrl.c | ||
| i2c-mux-reg.c | ||
| Kconfig | ||
| Makefile | ||