From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Limonciello, Mario" <mario.limonciello@amd.com>
Cc: Jan Dabros <jsd@semihalf.com>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org,
jarkko.nikula@linux.intel.com, mika.westerberg@linux.intel.com,
hdegoede@redhat.com, wsa@kernel.org, rrangel@chromium.org,
mw@semihalf.com, jaz@semihalf.com, upstream@semihalf.com,
thomas.lendacky@amd.com, alexander.deucher@amd.com,
Nimesh.Easow@amd.com
Subject: Re: [PATCH v3 2/2] i2c: designware: Add AMD PSP I2C bus support
Date: Thu, 3 Feb 2022 12:41:53 +0200 [thread overview]
Message-ID: <YfuxcTFnWQ4MLxvp@smile.fi.intel.com> (raw)
In-Reply-To: <724bbaef-8ee5-0904-d871-750643b4ff89@amd.com>
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
next prev parent reply other threads:[~2022-02-03 10:43 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 0:16 [PATCH 0/2] i2c-designware: Add support for AMD PSP semaphore Jan Dabros
2022-01-20 0:16 ` [PATCH 1/2] i2c: designware: Add missing locks Jan Dabros
2022-01-20 11:25 ` Hans de Goede
2022-01-24 10:33 ` Jan Dąbroś
2022-01-28 14:48 ` [PATCH v2 0/2] i2c-designware: Add support for AMD PSP semaphore Jan Dabros
2022-01-28 14:48 ` [PATCH v2 1/2] i2c: designware: Add missing locks Jan Dabros
2022-01-28 14:48 ` [PATCH v2 2/2] i2c: designware: Add AMD PSP I2C bus support Jan Dabros
2022-01-28 14:59 ` Jan Dąbroś
2022-01-28 15:49 ` Andy Shevchenko
2022-01-31 12:10 ` Jan Dąbroś
[not found] ` <CAOtMz3Oryr7mmRKf+secix_6=ZD_Lq+pMUoP=5T6AS6BPoqyQw@mail.gmail.com>
2022-01-31 13:31 ` Andy Shevchenko
2022-02-02 14:42 ` Jan Dąbroś
2022-01-28 14:58 ` [PATCH v2 0/2] i2c-designware: Add support for AMD PSP semaphore Jan Dąbroś
2022-02-02 14:43 ` [PATCH v3 " Jan Dabros
2022-02-02 14:43 ` [PATCH v3 2/2] i2c: designware: Add AMD PSP I2C bus support Jan Dabros
2022-02-02 16:13 ` Andy Shevchenko
2022-02-07 8:27 ` Jan Dąbroś
2022-02-07 11:41 ` Andy Shevchenko
2022-02-08 14:15 ` Jan Dąbroś
2022-02-07 14:25 ` Wolfram Sang
2022-02-08 14:13 ` Jan Dąbroś
2022-02-02 22:49 ` Limonciello, Mario
2022-02-03 10:41 ` Andy Shevchenko [this message]
2022-02-03 11:52 ` Jan Dąbroś
2022-01-20 0:16 ` [PATCH " Jan Dabros
2022-01-20 11:44 ` kernel test robot
2022-01-20 11:44 ` kernel test robot
2022-01-20 11:51 ` Hans de Goede
2022-01-21 9:59 ` Jan Dąbroś
2022-01-21 10:32 ` Hans de Goede
2022-01-21 17:38 ` Limonciello, Mario
2022-01-21 19:18 ` Tom Lendacky
2022-01-24 13:42 ` Jan Dąbroś
2022-01-26 19:36 ` Limonciello, Mario
2022-01-28 14:47 ` Jan Dąbroś
2022-01-24 12:35 ` Jan Dąbroś
2022-01-24 14:27 ` Hans de Goede
2022-01-20 14:20 ` Andy Shevchenko
2022-01-21 10:20 ` Jan Dąbroś
2022-01-21 17:51 ` Andy Shevchenko
2022-01-28 14:46 ` Jan Dąbroś
2022-01-20 15:33 ` kernel test robot
2022-01-20 15:33 ` kernel test robot
2022-01-20 17:09 ` Andy Shevchenko
2022-01-20 17:09 ` Andy Shevchenko
2022-01-28 14:39 ` Jan Dąbroś
2022-01-28 14:39 ` Jan Dąbroś
2022-01-20 11:15 ` [PATCH 0/2] i2c-designware: Add support for AMD PSP semaphore Hans de Goede
2022-01-20 12:29 ` Jan Dąbroś
2022-01-20 15:57 ` Hans de Goede
2022-01-21 10:27 ` Jan Dąbroś
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=YfuxcTFnWQ4MLxvp@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Nimesh.Easow@amd.com \
--cc=alexander.deucher@amd.com \
--cc=hdegoede@redhat.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jaz@semihalf.com \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mika.westerberg@linux.intel.com \
--cc=mw@semihalf.com \
--cc=rrangel@chromium.org \
--cc=thomas.lendacky@amd.com \
--cc=upstream@semihalf.com \
--cc=wsa@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.