From: Andrew Cooks <andrew.cooks@opengear.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
Wolfram Sang <wsa@the-dreams.de>,
"open list:I2C/SMBUS CONTROLLER DRIVERS FOR PC"
<linux-i2c@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] i2c: add ACPI support for i2c-piix4
Date: Tue, 30 Jan 2018 11:43:46 +1000 [thread overview]
Message-ID: <56310e2c-eedc-a71a-3247-d418ec10052d@opengear.com> (raw)
In-Reply-To: <CAHp75VeZ6fXJsRAj=4ozhLe=X=yL8y3pBVk1c4H7_niQ88Gfhw@mail.gmail.com>
Hi Andy
On 29/01/18 23:30, Andy Shevchenko wrote:
> On Mon, Jan 29, 2018 at 5:54 AM, Andrew Cooks <andrew.cooks@opengear.com> wrote:
>> This enables the i2c-piix4 SMBus controller driver to enumerate I2C
>> slave devices using ACPI. It builds on the related I2C mux device work
>> in commit 8eb5c87a92c0 ("i2c: add ACPI support for I2C mux ports")
>>
>> In the i2c-piix4 driver the adapters are enumerated as:
>> Main SMBus adapter Port 0, Port 2, ..., aux port (i.e., ASF adapter)
>>
>> However, in the AMD BKDG documentation[1], the implied order of ports is:
>> Main SMBus adapter Port 0, ASF adapter, Port 2, Port 3, ...
>>
>> This ordering difference is unfortunate, and we assume that ACPI
>> developers will use the Linux ordering.
>>
>> [1] 52740 BIOS and Kernel Developer's Guide (BKDG) for AMD Family 16h
>> Models 30h-3Fh Processors
>
>> + if (has_acpi_companion(&dev->dev)) {
>> + acpi_preset_companion(&adap->dev,
>> + ACPI_COMPANION(&dev->dev),
>> + piix4_adapter_count++);
>> + }
>
> Wouldn't be enough just following:
>
> ACPI_COMPANION_SET(&adap->dev, ACPI_COMPANION(&dev->dev));
In the ACPI DSDT, I've modeled the topology as follows:
Device(SBUS) {
Name(_ADR, 0x00140000)
Name(_HID, "SMB0001") // SMBus CMI spec uses (invalid hid) "SMBUS01"
Device(CH00) {
Name(_ADR, 0) // main SMBus adapter, Port 0
Name (_STR, Unicode ("Main SMBus adapter, Port 0"))
}
Device(CH01) {
Name(_ADR, 1) // main SMBus Port 2 (Port 1 label is undefined)
Name (_STR, Unicode ("Main SMBus adapter, Port 2"))
}
Device (CH02) {
Name(_ADR, 2) // ASF adapter (what Linux calls 'aux port')
Name (_STR, Unicode ("AUX / ASF SMBus adapter"))
}
}
That is why each piix4 adapter matches a CH0? device that is descendant from the SBUS device in ACPI.
It is similar to the topology shown in commit 8eb5c87a ("i2c: add ACPI support for I2C mux ports")
>
> ?
>
> Or if this increment is needed:
>
> struct acpi_device *adev = ACPI_COMPANION(&dev->dev);
>
> if (adev) {
> ACPI_COMPANION_SET(&adap->dev, adev);
> piix4_adapter_count++);
> }
>
Thanks!
a.
next prev parent reply other threads:[~2018-01-30 1:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1517195327.git.andrew.cooks@opengear.com>
2018-01-29 3:54 ` [PATCH 1/3] i2c: piix4: Fix port selection for AMD Family 16h Model 30h Andrew Cooks
2018-01-29 3:54 ` [PATCH 2/3] i2c: piix4: fix number of ports on " Andrew Cooks
2018-01-29 5:58 ` [2/3] " Guenter Roeck
2018-01-29 23:30 ` Andrew Cooks
2018-01-29 3:54 ` [PATCH 3/3] i2c: add ACPI support for i2c-piix4 Andrew Cooks
2018-01-29 13:30 ` Andy Shevchenko
2018-01-30 1:13 ` Andrew Cooks
2018-01-30 1:43 ` Andrew Cooks [this message]
2018-01-30 18:22 ` Andy Shevchenko
2018-01-30 18:23 ` Andy Shevchenko
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=56310e2c-eedc-a71a-3247-d418ec10052d@opengear.com \
--to=andrew.cooks@opengear.com \
--cc=andy.shevchenko@gmail.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;
as well as URLs for NNTP newsgroup(s).