From: Srinivas Pandruvada <srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org
Cc: mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Srinivas Pandruvada
<srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
Subject: [PATCH v2 0/2] i2c/acpi: Support for multiple serial bus addresses
Date: Fri, 5 Sep 2014 08:21:04 -0700 [thread overview]
Message-ID: <1409930466-31746-1-git-send-email-srinivas.pandruvada@linux.intel.com> (raw)
The ACPI spec allows multiple i2c addresses for a single device. This
series addresses the implementation of this support in core i2c for ACPI
enumeration.
v2
Restructured based on 3.17.rc3 as acpi i2c part has been moved out of i2c-core.
v1
Create an i2c device for the first valid i2c address which is not a
SMBus reserved address and let the first enumerated driver use the other
defined addresses by providing helper function to retrieve them.
v0
Sent on Mar 6, 2014
This patchset create an i2c device at every specified i2c serial bus
address.
[PATCH 1/2] i2c/ACPI: Support for multiple serial bus addresses
Mika Westerberg (1):
i2c / ACPI: Add support for extracting multiple I2C addresses
Srinivas Pandruvada (1):
i2c / ACPI: Create device on a valid first address
drivers/i2c/i2c-acpi.c | 143 +++++++++++++++++++++++++++++++++++++++++++++++++
drivers/i2c/i2c-core.c | 61 +++++++++++++++++++++
include/linux/i2c.h | 8 +++
3 files changed, 212 insertions(+)
--
1.9.3
next reply other threads:[~2014-09-05 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 15:21 Srinivas Pandruvada [this message]
[not found] ` <1409930466-31746-1-git-send-email-srinivas.pandruvada-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2014-09-05 15:21 ` [PATCH v2 1/2] i2c / ACPI: Create device on a valid first address Srinivas Pandruvada
2014-09-05 15:21 ` [PATCH v2 2/2] i2c / ACPI: Add support for extracting multiple I2C addresses Srinivas Pandruvada
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=1409930466-31746-1-git-send-email-srinivas.pandruvada@linux.intel.com \
--to=srinivas.pandruvada-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mika.westerberg-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
--cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
/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).