From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i2c: designware: Add support for AMD Seattle I2C
Date: Sun, 3 Jan 2016 16:54:47 -0600 [thread overview]
Message-ID: <5689A6B7.7010401@amd.com> (raw)
In-Reply-To: <20160103184555.GG1522@katana>
Hi Wolfram,
On 01/03/2016 12:45 PM, Wolfram Sang wrote:
> On Wed, Dec 16, 2015 at 06:49:59PM -0600, Suravee Suthikulanit wrote:
>> Mika,
>>
>> On 12/16/2015 8:54 AM, Mika Westerberg wrote:
>>> On Wed, Dec 16, 2015 at 08:29:38AM -0600, Suravee Suthikulpanit wrote:
>>>>>
>>>>>
>>>>> On 12/16/2015 03:16 AM, Mika Westerberg wrote:
>>>>>>> On Tue, Dec 15, 2015 at 08:14:34PM -0600, Suravee Suthikulpanit wrote:
>>>>>>>>> Hi Mika,
>>>>>>>>>
>>>>>>>>> On 12/15/15 15:55, Suravee Suthikulpanit wrote:
>>>>>>>>>>> Add device HID AMDI0510 to match the I2C controlers on AMD Seattle platform
>>>>>>>>>>>
>>>>>>>>>>> Signed-off-by: Suravee Suthikulpanit<Suravee.Suthikulpanit@amd.com>
>>>>>>>>>>> ---
>>>>>>>>>>> drivers/i2c/busses/i2c-designware-platdrv.c | 1 +
>>>>>>>>>>> 1 file changed, 1 insertion(+)
>>>>>>>>>>>
>>>>>>>>>>> diff --git a/drivers/i2c/busses/i2c-designware-platdrv.c b/drivers/i2c/busses/i2c-designware-platdrv.c
>>>>>>>>>>> index 57f623b..a027154 100644
>>>>>>>>>>> --- a/drivers/i2c/busses/i2c-designware-platdrv.c
>>>>>>>>>>> +++ b/drivers/i2c/busses/i2c-designware-platdrv.c
>>>>>>>>>>> @@ -117,6 +117,7 @@ static const struct acpi_device_id dw_i2c_acpi_match[] = {
>>>>>>>>>>> { "80860F41", 0 },
>>>>>>>>>>> { "808622C1", 0 },
>>>>>>>>>>> { "AMD0010", 0 },
>>>>>>>>>>> + { "AMDI0510", 0 },
>>>>>>>>>>> { }
>>>>>>>>>
>>>>>>>>> Since this driver seems to be used by several SOCs, and we have been adding
>>>>>>>>> the HID from various SOC vendors. Do you think it would be better to assign
>>>>>>>>> a CID so that each SOC vendor can specify in their ACPI DSDT and we can
>>>>>>>>> match them here?
>>>>>>>
>>>>>>> Sure _CID would work here.
>>>>>
>>>>> Do you know if Synopsys has already provided a CID that we can use for this?
>>> No.
>>>
>>>>> If not, who do you think should provide this?
>>> Why can't you make _CID for AMD part only? For Intel we are going to get
>>> new IDs for every major SoC release no matter what.
>>>
>> Actually, after discussed with the team. We have decided to go with the
>> AMDI0510 at this point, and we will reuse this as CID in future SOC if it
>> contains compatible I2C controller.
>
> So, can I take the patch as is?
>
Yes, please pull this as is.
Thank you,
Suravee
next prev parent reply other threads:[~2016-01-03 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 21:55 [PATCH] i2c: designware: Add support for AMD Seattle I2C Suravee Suthikulpanit
2015-12-16 2:14 ` Suravee Suthikulpanit
2015-12-16 9:16 ` Mika Westerberg
2015-12-16 14:29 ` Suravee Suthikulpanit
2015-12-16 14:54 ` Mika Westerberg
2015-12-17 0:49 ` Suravee Suthikulanit
2016-01-03 18:45 ` Wolfram Sang
2016-01-03 22:54 ` Suravee Suthikulpanit [this message]
2016-01-04 19:25 ` Wolfram Sang
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=5689A6B7.7010401@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@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).