Re: [PATCH v6 4/4] platform/x86: Add ACPI i2c-multi-instantiate pseudo driver

2018-08-12 Thread Rafael J. Wysocki
On Thursday, August 9, 2018 2:08:41 PM CEST Hans de Goede wrote: > Hi, > > On 09-08-18 13:55, Rafael J. Wysocki wrote: > > On Thu, Aug 9, 2018 at 1:40 PM, Hans de Goede wrote: > >> On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node > >> per i2c-device and that fw-node cont

Re: [PATCH v6 4/4] platform/x86: Add ACPI i2c-multi-instantiate pseudo driver

2018-08-09 Thread Hans de Goede
Hi, On 09-08-18 13:55, Rafael J. Wysocki wrote: On Thu, Aug 9, 2018 at 1:40 PM, Hans de Goede wrote: On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1 i2c-device. But in some rare cases the ma

Re: [PATCH v6 4/4] platform/x86: Add ACPI i2c-multi-instantiate pseudo driver

2018-08-09 Thread Rafael J. Wysocki
On Thu, Aug 9, 2018 at 1:40 PM, Hans de Goede wrote: > On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node > per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1 > i2c-device. > > But in some rare cases the manufacturer has decided to describe multiple

[PATCH v6 4/4] platform/x86: Add ACPI i2c-multi-instantiate pseudo driver

2018-08-09 Thread Hans de Goede
On systems with ACPI instantiated i2c-clients, normally there is 1 fw_node per i2c-device and that fw-node contains 1 I2cSerialBus resource for that 1 i2c-device. But in some rare cases the manufacturer has decided to describe multiple i2c-devices in a single ACPI fwnode with multiple I2cSerialBus