From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: linux-acpi@vger.kernel.org, linux-i2c@vger.kernel.org,
Lee Jones <lee.jones@linaro.org>,
Wolfram Sang <wsa@the-dreams.de>,
"Rafael J . Wysocki" <rjw@rjwysocki.net>,
Mika Westerberg <mika.westerberg@intel.com>,
"Puustinen, Ismo" <ismo.puustinen@intel.com>,
linux-kernel@vger.kernel.org
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Thierry Reding <thierry.reding@gmail.com>
Subject: [PATCH v4 0/5] enable I2C devices behind I2C bus on Gen2
Date: Fri, 23 Oct 2015 12:16:40 +0300 [thread overview]
Message-ID: <1445591805-28886-1-git-send-email-andriy.shevchenko@linux.intel.com> (raw)
There is a board in the wild, i.e. Intel Galileo Gen2, that has ACPI enumerated
devices behind I2C bus. This patch series dedicated to enable those devices.
The MFD framework is also updated to cope with interesting implementation of
the cell descriptions under ACPI MFD (patch 1).
The patches 5 and 6 are pretty independent and could be applied ahead, though
they don't make much sense without previous ones.
Wolfram, since Lee acknowledged patches 1-3, can you pull them to your tree?
Tested on the actual Intel Galileo Gen2 by Ismo (gpio expanders) and me (at24).
Cc: Thierry Reding <thierry.reding@gmail.com>
Changelog v4:
- amend at24 patch to satisfy sparse (Wolfram)
- drop applied patches
Changelog v3:
- append ACKs from Rafael (from ACPI angle)
- drop upstreamed patches (GPIO pca953x)
Changelog v2:
- append tags
- re-make patch 3 (suggested by Lee)
- improve patch 8 (suggested by Thierry)
Andy Shevchenko (5):
mfd: core: redo ACPI matching of the children devices
mfd: intel_quark_i2c_gpio: load gpio driver first
mfd: intel_quark_i2c_gpio: support devices behind i2c bus
at24: enable ACPI device found on Galileo Gen2
pwm-pca9685: enable ACPI device found on Galileo Gen2
Documentation/acpi/enumeration.txt | 11 +++++---
drivers/mfd/intel_quark_i2c_gpio.c | 33 ++++++++++++++++--------
drivers/mfd/mfd-core.c | 52 ++++++++++++++++++++++++++------------
drivers/misc/eeprom/at24.c | 22 +++++++++++++---
drivers/pwm/Kconfig | 2 +-
drivers/pwm/pwm-pca9685.c | 20 ++++++++++++---
include/linux/mfd/core.h | 10 ++++++--
7 files changed, 111 insertions(+), 39 deletions(-)
--
2.6.1
next reply other threads:[~2015-10-23 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 9:16 Andy Shevchenko [this message]
2015-10-23 9:16 ` [PATCH v4 1/5] mfd: core: redo ACPI matching of the children devices Andy Shevchenko
2015-10-23 9:16 ` [PATCH v4 2/5] mfd: intel_quark_i2c_gpio: load gpio driver first Andy Shevchenko
2015-10-23 9:16 ` [PATCH v4 3/5] mfd: intel_quark_i2c_gpio: support devices behind i2c bus Andy Shevchenko
2015-10-23 9:16 ` [PATCH v4 4/5] at24: enable ACPI device found on Galileo Gen2 Andy Shevchenko
2015-10-23 17:20 ` Ben Gardner
2015-10-23 9:16 ` [PATCH v4 5/5] pwm-pca9685: " Andy Shevchenko
2015-11-09 13:53 ` Andy Shevchenko
2015-11-09 17:10 ` Thierry Reding
2015-10-23 12:38 ` [PATCH v4 0/5] enable I2C devices behind I2C bus on Gen2 Wolfram Sang
2015-10-23 13:50 ` Andy Shevchenko
2015-10-26 8:16 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1445591805-28886-1-git-send-email-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=ismo.puustinen@intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@intel.com \
--cc=rjw@rjwysocki.net \
--cc=thierry.reding@gmail.com \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).