diff options
| author | Evan Green <evgreen@chromium.org> | 2020-11-18 15:40:25 -0800 |
|---|---|---|
| committer | Wolfram Sang <wsa@kernel.org> | 2021-01-17 12:52:58 +0100 |
| commit | 98b2b712bc8592c4ad212449162e36e47761a46c (patch) | |
| tree | dd89ea28a8d16d6ca29ba0a3bc18a2fcf719c6fa /drivers/i2c/i2c-stub.c | |
| parent | 19eb29b05cc6dd6842ddc475a45da6723428e927 (diff) | |
| download | linux-98b2b712bc8592c4ad212449162e36e47761a46c.tar.gz linux-98b2b712bc8592c4ad212449162e36e47761a46c.tar.bz2 linux-98b2b712bc8592c4ad212449162e36e47761a46c.zip | |
i2c: i2c-mux-gpio: Enable this driver in ACPI land
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>
Diffstat (limited to 'drivers/i2c/i2c-stub.c')
0 files changed, 0 insertions, 0 deletions