From: Jarkko Nikula <jarkko.nikula@linux.intel.com>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-i2c@vger.kernel.org, Wolfram Sang <wsa@kernel.org>
Subject: Re: [PATCH 2/2] i2c: i801: Add support for Intel Meteor Lake PCH-S
Date: Tue, 4 Apr 2023 10:55:55 +0300 [thread overview]
Message-ID: <0046bbc0-27dc-2eb4-eadf-9632a6a0730b@linux.intel.com> (raw)
In-Reply-To: <20230403180357.500a8867@endymion.delvare>
On 4/3/23 19:03, Jean Delvare wrote:
> Hi Jarkko,
>
> On Thu, 30 Mar 2023 13:55:02 +0300, Jarkko Nikula wrote:
>> Add SMBus PCI ID on Intel Meteor Lake PCH-S. Also called as Meteor
>> Point-S which is used in the code to distinguish from Meteor Lake-S SoC
>> but call both as Meteor Lake in documentation and Kconfig.
>>
>> Signed-off-by: Jarkko Nikula <jarkko.nikula@linux.intel.com>
>> ---
>> Documentation/i2c/busses/i2c-i801.rst | 2 +-
>> drivers/i2c/busses/Kconfig | 2 +-
>> drivers/i2c/busses/i2c-i801.c | 3 +++
>> 3 files changed, 5 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/i2c/busses/i2c-i801.rst b/Documentation/i2c/busses/i2c-i801.rst
>> index ab9e850e8fe0..e62a62323f36 100644
>> --- a/Documentation/i2c/busses/i2c-i801.rst
>> +++ b/Documentation/i2c/busses/i2c-i801.rst
>> @@ -46,7 +46,7 @@ Supported adapters:
>> * Intel Emmitsburg (PCH)
>> * Intel Alder Lake (PCH)
>> * Intel Raptor Lake (PCH)
>> - * Intel Meteor Lake (SOC)
>> + * Intel Meteor Lake (SOC/PCH)
>
> I'm confused. The patch actually adds support for Meteor Point (S). So
> shouldn't you add:
> * Intel Meteor Point (PCH)
>
> instead of modifying the existing line?
>
Idea was to follow my earlier commit 80d943ab19e9 ("i2c: i801:
Consolidate chipset names in documentation and Kconfig") to use single
name for the same family instead of listing all possible variants.
Like here we have already support for Meteor Lake -P SoC and now adding
support for Meteor Lake -S that will have both in SoC SMBus and PCH
SMBus controllers.
I realized actually Alder Lake (PCH) above may not be correct. True for
Alder Lake -S PCH but now thinking -P and -M variants may be actually SoCs.
Confusing, yes I agree :-)
next prev parent reply other threads:[~2023-04-04 7:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 10:55 [PATCH 1/2] i2c: i801: Add support for Intel Meteor Lake-S SoC Jarkko Nikula
2023-03-30 10:55 ` [PATCH 2/2] i2c: i801: Add support for Intel Meteor Lake PCH-S Jarkko Nikula
2023-04-03 16:03 ` Jean Delvare
2023-04-04 7:55 ` Jarkko Nikula [this message]
2023-04-03 15:34 ` [PATCH 1/2] i2c: i801: Add support for Intel Meteor Lake-S SoC Jean Delvare
2023-04-04 7:30 ` Jarkko Nikula
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=0046bbc0-27dc-2eb4-eadf-9632a6a0730b@linux.intel.com \
--to=jarkko.nikula@linux.intel.com \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox