Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-09-30 Thread Dustin Byford
On Wed Sep 30 16:57, Mika Westerberg wrote: > On Wed, Sep 30, 2015 at 02:52:28PM +0200, Rafael J. Wysocki wrote: > > > > Device (CH00) { > > > > Name (_ADR, 0x0) > > > > > > > > Device (TMP0) { > > > > Name (_ADR, 0x50) > > > > > > ... and this are not needed. I2cS

Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-09-30 Thread Mika Westerberg
On Wed, Sep 30, 2015 at 02:52:28PM +0200, Rafael J. Wysocki wrote: > > > Device (CH00) { > > > Name (_ADR, 0x0) > > > > > > Device (TMP0) { > > > Name (_ADR, 0x50) > > > > ... and this are not needed. I2cSerialBus already contains the address. > > > > Also I think

Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-09-30 Thread Rafael J. Wysocki
On Wednesday, September 30, 2015 12:43:36 PM Mika Westerberg wrote: > On Tue, Sep 29, 2015 at 04:19:12PM -0700, Dustin Byford wrote: > > Hi Mika, > > > > On Mon Aug 17 15:03, Mika Westerberg wrote: > > > I think the current code in I2C core is not actually doing the right > > > thing according the

Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-09-30 Thread Mika Westerberg
On Tue, Sep 29, 2015 at 04:19:12PM -0700, Dustin Byford wrote: > Hi Mika, > > On Mon Aug 17 15:03, Mika Westerberg wrote: > > I think the current code in I2C core is not actually doing the right > > thing according the ACPI spec at least. To my understanding you can have > > device with I2cSerialB

Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-09-29 Thread Dustin Byford
Hi Mika, On Mon Aug 17 15:03, Mika Westerberg wrote: > I think the current code in I2C core is not actually doing the right > thing according the ACPI spec at least. To my understanding you can have > device with I2cSerialBus resource _anywhere_ in the namespace, not just > directly below the host

Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-08-17 Thread Dustin Byford
Hi Mika, Thanks for taking a look. On Mon Aug 17 15:03, Mika Westerberg wrote: > On Fri, Aug 14, 2015 at 12:31:32PM -0700, Dustin Byford wrote: > > Name (_DSD, Package () > > { > > ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"), > > Package () { > > Package (2

Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-08-17 Thread Mika Westerberg
On Fri, Aug 14, 2015 at 12:31:32PM -0700, Dustin Byford wrote: > > (v2 corrects cc: list) > > I would like to add support for scanning I2C devices connected to ACPI > OF compatible muxes described in ASL like this: > > Device (MUX0) > { > Name (_ADR, 0x70) > Name (_HID, "PRP0001") >

Re: [RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-08-15 Thread Wolfram Sang
On Fri, Aug 14, 2015 at 12:31:32PM -0700, Dustin Byford wrote: > > (v2 corrects cc: list) And adding Mika to the cc-list who is our I2C and ACPI expert. Mika can you have a look at this and the other patches Dustin sent recently to the i2c list? Thanks, Wolfram > > I would like to add supp

[RFC v2 0/1] i2c: acpi: scan ACPI enumerated I2C mux channels

2015-08-14 Thread Dustin Byford
(v2 corrects cc: list) I would like to add support for scanning I2C devices connected to ACPI OF compatible muxes described in ASL like this: Device (MUX0) { Name (_ADR, 0x70) Name (_HID, "PRP0001") Name (_CRS, ResourceTemplate() { I2cSerialBus (0x70, ControllerInitiated,