From: Andrew Cooks <andrew.cooks@opengear.com>
To: Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-i2c@vger.kernel.org (open list:I2C/SMBUS CONTROLLER
DRIVERS FOR PC), linux-kernel@vger.kernel.org (open list)
Cc: Andrew Cooks <andrew.cooks@opengear.com>
Subject: [PATCH v4 0/3] Enable ACPI-defined peripherals on i2c-piix4 SMBus
Date: Wed, 31 Jan 2018 07:40:27 +1000 [thread overview]
Message-ID: <cover.1517285239.git.andrew.cooks@opengear.com> (raw)
These patches fix a couple of issues with the i2c-piix4 driver on
AMD Family 16h Model 30h SoCs and add ACPI-based enumeration to the
i2c-piix4 driver.
Some I2C peripherals, eg. PCA953x IO expander, are not discovered by the
probe or detect mechanisms when attached to an SMBus controller that uses
the i2c-piix4 SMBus driver.
ACPI provides a mechanism to define these peripherals and the controller
port that they're attached to.
Changes:
v4:
remove unnecessary SB800_MAIN_PORTS constant
reduce piix4_remove change
v3:
take chip revision into account when determining port selection register
v2:
count the adapters, instead of misusing port numbers
Andrew Cooks (3):
i2c: piix4: Fix port selection for AMD Family 16h Model 30h
i2c: piix4: fix probing of reserved ports on AMD
i2c: piix4: add ACPI support
drivers/i2c/busses/i2c-piix4.c | 37 ++++++++++++++++++++++++++-----------
1 file changed, 26 insertions(+), 11 deletions(-)
--
2.7.4
next reply other threads:[~2018-01-30 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 21:40 Andrew Cooks [this message]
2018-01-30 21:40 ` [PATCH v4 1/3] i2c: piix4: Fix port selection for AMD Family 16h Model 30h Andrew Cooks
2018-02-19 20:41 ` Andrew Cooks
2018-01-30 21:40 ` [PATCH v4 2/3] i2c: piix4: fix probing of reserved ports on AMD Andrew Cooks
2018-01-30 21:40 ` [PATCH v4 3/3] i2c: piix4: add ACPI support Andrew Cooks
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=cover.1517285239.git.andrew.cooks@opengear.com \
--to=andrew.cooks@opengear.com \
--cc=jdelvare@suse.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome