Re: [PATCH 2/2] i2c: add ACPI support for I2C mux ports

2015-10-13 Thread Mika Westerberg
On Mon, Oct 12, 2015 at 11:32:31AM -0700, Dustin Byford wrote: > I've been trying to consider the options, perhaps you can help my > understanding. Using the i801 driver as an example, the device is PCI > and the companion is associated with the PCI dev. The driver creates > another device for th

Re: [PATCH 2/2] i2c: add ACPI support for I2C mux ports

2015-10-12 Thread Dustin Byford
Hi Mika, On Mon Oct 12 13:50, Mika Westerberg wrote: > On Fri, Oct 09, 2015 at 05:41:47PM -0700, Dustin Byford wrote: > > Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or > > device property compatible string match) enumerating I2C client devices > > connected through a I2C

Re: [PATCH 2/2] i2c: add ACPI support for I2C mux ports

2015-10-12 Thread Mika Westerberg
On Fri, Oct 09, 2015 at 05:41:47PM -0700, Dustin Byford wrote: > Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or > device property compatible string match) enumerating I2C client devices > connected through a I2C mux device requires a little extra work. > > This change impl

Re: [PATCH 2/2] i2c: add ACPI support for I2C mux ports

2015-10-09 Thread kbuild test robot
Hi Dustin, [auto build test ERROR on wsa/i2c/for-next -- if it's inappropriate base, please ignore] config: xtensa-allyesconfig (attached as .config) reproduce: wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross chmod +

[PATCH 2/2] i2c: add ACPI support for I2C mux ports

2015-10-09 Thread Dustin Byford
Although I2C mux devices are easily enumerated using ACPI (_HID/_CID or device property compatible string match) enumerating I2C client devices connected through a I2C mux device requires a little extra work. This change implements a method for describing an I2C device hierarchy that includes mux