[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151023084013.GS1526@lahna.fi.intel.com>
Date: Fri, 23 Oct 2015 11:40:13 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Dustin Byford <dustin@...ulusnetworks.com>
Cc: Wolfram Sang <wsa@...-dreams.de>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Jean Delvare <jdelvare@...e.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-i2c@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org, rjw@...ysocki.net,
"Puustinen, Ismo" <ismo.puustinen@...el.com>
Subject: Re: [PATCH v4 2/2] i2c: add ACPI support for I2C mux ports
On Thu, Oct 22, 2015 at 02:17:42AM -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 an I2C mux needs a little extra work.
>
> This change implements a method for describing an I2C device hierarchy that
> includes mux devices by using an ACPI Device() for each mux channel along
> with an _ADR to set the channel number for the device. See
> Documentation/acpi/i2c-muxes.txt for a simple example.
>
> To make this work the ismt, i801, and designware pci/platform devs now
> share an ACPI companion with their I2C adapter dev similar to how it's done
> in OF. This is done on the assumption that power management functions will
> not be called directly on the I2C dev that is sharing the ACPI node.
>
> Signed-off-by: Dustin Byford <dustin@...ulusnetworks.com>
This looks good to me.
You did also some stylistic changes to the drivers in question which I
think should be placed to a separate patches.
Regardless of that,
Acked-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
I'll leave this up to Rafael and Wolfram to decide how to go forward
with this patch.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists