From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Christian Fetzer <fetzer.ch@gmail.com>, linux-i2c@vger.kernel.org
Cc: jarkko.nikula@linux.intel.com, mika.westerberg@linux.intel.com,
wsa@the-dreams.de, galandilias@gmail.com
Subject: Re: [PATCH v4 0/3] Support multiplexed main SMBus interface on SB800
Date: Mon, 16 Nov 2015 11:26:48 +0200 [thread overview]
Message-ID: <1447666008.31665.140.camel@linux.intel.com> (raw)
In-Reply-To: <1447587184-21965-1-git-send-email-fetzer.ch@gmail.com>
On Sun, 2015-11-15 at 12:33 +0100, Christian Fetzer wrote:
> This is an attempt to upstream the patches created by Thomas Brandon
> and
> Eddi De Pieri to support the multiplexed main SMBus interface on the
> SB800
> chipset. (https://www.mail-archive.com/linux-i2c@vger.kernel.org/msg0
> 6757.html)
>
> I have mainly rebased the latest patch version and tested the driver
> on a
> HP ProLiant MicroServer G7 N54L (where this patch allows to access
> sensor data
> from a w83795adg).
>
> The patched driver is running stable on the machine, given that
> ic2_piix4 is
> loaded before jc42 and w83795. If jc42 is loaded before i2c_piix4
> calling
> sensors triggers some errors:
> ERROR: Can't get value of subfeature temp1_min_alarm: Can't read
>
> While the kernel log shows:
> i2c i2c-1: Transaction (pre): CNT=0c, CMD=05, ADD=31, DAT0=03,
> DAT1=c0
> i2c i2c-1: Error: no response!
> i2c i2c-1: Transaction (post): CNT=0c, CMD=05, ADD=31, DAT0=ff,
> DAT1=ff
> Unfortunately I don't know how to tackle this specific issue.
>
> Please review and let me know required changes in order to get this
> upstream
> finally.
One nitpick in one patch, though it looks okay for me:
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> Eddi, Thomas, it would be great if you could verify the changes on
> your
> machines.
>
> Regards,
> Christian
>
> v4:
> - Incorporated changes requested by Andy
> - added mutex to struct i2c_piix4_adapdata
> - added flag for releasing SMBus index region to struct
> i2c_piix4_adapdata
> - this flag now indicates that the adapter is a sb800 main
> adapter
> - together with the port number it simplifies the adapter
> releasing and the first patch in v3 is no more needed
> - unfortunately patch 3 and 4 in v3 had to be combined as
> only
> the patch introducing multiplexing adds a separate
> add_adapters_sb800
> method that can be used to set the flag.
> - fixed releasing the SMBus index region in case setting up the
> adapter fails
>
> v3:
> - Incorporated changes requested by Mika and Andy
> - main adapter name set to 'main'
> - defined constant idx address
> - block comment style, joined string literals, reworked for loops
> into while loops
>
> v2:
> - Incorporated changes requested by Mika
> - remove adapter in reverse order
> - ERROR label
> - request base address index region only once
>
> Christian Fetzer (3):
> i2c-piix4: Convert piix4_main_adapter to array
> i2c-piix4: Add support for multiplexed main adapter in SB800
> i2c-piix4: Add adapter port name support for SB800 chipset
>
> drivers/i2c/busses/i2c-piix4.c | 194
> +++++++++++++++++++++++++++++++++++------
> 1 file changed, 165 insertions(+), 29 deletions(-)
>
--
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy
prev parent reply other threads:[~2015-11-16 9:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-15 11:33 [PATCH v4 0/3] Support multiplexed main SMBus interface on SB800 Christian Fetzer
2015-11-15 11:33 ` [PATCH v4 1/3] i2c-piix4: Convert piix4_main_adapter to array Christian Fetzer
2015-11-15 11:33 ` [PATCH v4 2/3] i2c-piix4: Add support for multiplexed main adapter in SB800 Christian Fetzer
2015-11-16 9:29 ` Andy Shevchenko
2015-11-16 12:31 ` Mika Westerberg
2015-11-15 11:33 ` [PATCH v4 3/3] i2c-piix4: Add adapter port name support for SB800 chipset Christian Fetzer
2015-11-16 9:26 ` Andy Shevchenko [this message]
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=1447666008.31665.140.camel@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=fetzer.ch@gmail.com \
--cc=galandilias@gmail.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=mika.westerberg@linux.intel.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).