[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YfuxcTFnWQ4MLxvp@smile.fi.intel.com>
Date: Thu, 3 Feb 2022 12:41:53 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: "Limonciello, Mario" <mario.limonciello@....com>
Cc: Jan Dabros <jsd@...ihalf.com>, linux-kernel@...r.kernel.org,
linux-i2c@...r.kernel.org, jarkko.nikula@...ux.intel.com,
mika.westerberg@...ux.intel.com, hdegoede@...hat.com,
wsa@...nel.org, rrangel@...omium.org, mw@...ihalf.com,
jaz@...ihalf.com, upstream@...ihalf.com, thomas.lendacky@....com,
alexander.deucher@....com, Nimesh.Easow@....com
Subject: Re: [PATCH v3 2/2] i2c: designware: Add AMD PSP I2C bus support
On Wed, Feb 02, 2022 at 04:49:40PM -0600, Limonciello, Mario wrote:
> On 2/2/2022 08:43, Jan Dabros wrote:
...
> > + { "AMDI0019", APD_ADDR(wt_i2c_desc) },
>
> Did you already check with anyone in AMD about reserving this ID?
Oh, it's a very good point! I was under impression that Jan operates on
allocated IDs...
> Considering this design is specific to arbitration used for Chromebooks I
> wonder if it is better to be GOOG ID?
>
> I can see it both ways, but if you didn't already talk to anyone and the
> consensus is for it to be AMDI****, I will ask around internally about
> reserving it / making sure there are no future or existing conflicts.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists