From: Mario Limonciello <mario.limonciello@amd.com>
PIIX4 and compatible controllers are only for X86. As some headers are
being moved into x86 specific headers PIIX4 won't compile on non-x86.
Suggested-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
v5:
* Drop unnecessary tags
---
drivers/i2c/busses/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 83c88c79afe20..bbbd6240fa6ed 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -200,7 +200,7 @@ config I2C_ISMT
config I2C_PIIX4
tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
- depends on PCI && HAS_IOPORT
+ depends on PCI && HAS_IOPORT && X86
select I2C_SMBUS
help
If you say yes to this option, support will be included for the Intel
--
2.43.0
Hi Mario,
CC mips, loongarch
On Wed, 23 Apr 2025 at 01:49, Mario Limonciello <superm1@kernel.org> wrote:
> From: Mario Limonciello <mario.limonciello@amd.com>
>
> PIIX4 and compatible controllers are only for X86. As some headers are
> being moved into x86 specific headers PIIX4 won't compile on non-x86.
>
> Suggested-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Thanks for your patch, which is now commit 7e173eb82ae97175
("i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86")
in v6.16-rc1.
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -200,7 +200,7 @@ config I2C_ISMT
>
> config I2C_PIIX4
> tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
> - depends on PCI && HAS_IOPORT
> + depends on PCI && HAS_IOPORT && X86
Are you sure this south-bridge is not used on non-x86 platforms?
It is enabled in several non-x86 defconfigs:
arch/loongarch/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
arch/mips/configs/ip27_defconfig:CONFIG_I2C_PIIX4=m
arch/mips/configs/loongson2k_defconfig:CONFIG_I2C_PIIX4=y
arch/mips/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
The loongarch and loongson entries are probably bogus, but I wouldn't
be surprised if the SGI Onyx and Origin do use Intel south-bridges.
> select I2C_SMBUS
> help
> If you say yes to this option, support will be included for the Intel
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
On Tue, Jun 10, 2025 at 5:16 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> Hi Mario,
>
> CC mips, loongarch
>
> On Wed, 23 Apr 2025 at 01:49, Mario Limonciello <superm1@kernel.org> wrote:
> > From: Mario Limonciello <mario.limonciello@amd.com>
> >
> > PIIX4 and compatible controllers are only for X86. As some headers are
> > being moved into x86 specific headers PIIX4 won't compile on non-x86.
> >
> > Suggested-by: Ingo Molnar <mingo@kernel.org>
> > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>
> Thanks for your patch, which is now commit 7e173eb82ae97175
> ("i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86")
> in v6.16-rc1.
>
> > --- a/drivers/i2c/busses/Kconfig
> > +++ b/drivers/i2c/busses/Kconfig
> > @@ -200,7 +200,7 @@ config I2C_ISMT
> >
> > config I2C_PIIX4
> > tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
> > - depends on PCI && HAS_IOPORT
> > + depends on PCI && HAS_IOPORT && X86
>
> Are you sure this south-bridge is not used on non-x86 platforms?
> It is enabled in several non-x86 defconfigs:
>
> arch/loongarch/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
> arch/mips/configs/ip27_defconfig:CONFIG_I2C_PIIX4=m
> arch/mips/configs/loongson2k_defconfig:CONFIG_I2C_PIIX4=y
> arch/mips/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>
> The loongarch and loongson entries are probably bogus, but I wouldn't
> be surprised if the SGI Onyx and Origin do use Intel south-bridges.
Loongson can use AMD SB700/SB800 south bridges, which have I2C_PIIX4.
Huacai
>
> > select I2C_SMBUS
> > help
> > If you say yes to this option, support will be included for the Intel
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
On 6/10/2025 2:24 AM, Huacai Chen wrote:
> On Tue, Jun 10, 2025 at 5:16 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>
>> Hi Mario,
>>
>> CC mips, loongarch
>>
>> On Wed, 23 Apr 2025 at 01:49, Mario Limonciello <superm1@kernel.org> wrote:
>>> From: Mario Limonciello <mario.limonciello@amd.com>
>>>
>>> PIIX4 and compatible controllers are only for X86. As some headers are
>>> being moved into x86 specific headers PIIX4 won't compile on non-x86.
>>>
>>> Suggested-by: Ingo Molnar <mingo@kernel.org>
>>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>>
>> Thanks for your patch, which is now commit 7e173eb82ae97175
>> ("i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86")
>> in v6.16-rc1.
>>
>>> --- a/drivers/i2c/busses/Kconfig
>>> +++ b/drivers/i2c/busses/Kconfig
>>> @@ -200,7 +200,7 @@ config I2C_ISMT
>>>
>>> config I2C_PIIX4
>>> tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
>>> - depends on PCI && HAS_IOPORT
>>> + depends on PCI && HAS_IOPORT && X86
>>
>> Are you sure this south-bridge is not used on non-x86 platforms?
>> It is enabled in several non-x86 defconfigs:
>>
>> arch/loongarch/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>> arch/mips/configs/ip27_defconfig:CONFIG_I2C_PIIX4=m
>> arch/mips/configs/loongson2k_defconfig:CONFIG_I2C_PIIX4=y
>> arch/mips/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>>
>> The loongarch and loongson entries are probably bogus, but I wouldn't
>> be surprised if the SGI Onyx and Origin do use Intel south-bridges.
> Loongson can use AMD SB700/SB800 south bridges, which have I2C_PIIX4.
Well we could revert this patch, but it's going to be a compile failure
because of 624b0d5696a89b138408d385899dd35372db324b and other patches
that go on top of that.
My current leaning is we make a dummy fch.h header for these archs with
#defines for 0.
Any thoughts?
>
> Huacai
>
>>
>>> select I2C_SMBUS
>>> help
>>> If you say yes to this option, support will be included for the Intel
>>
>> Gr{oetje,eeting}s,
>>
>> Geert
>>
>> --
>> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>>
>> In personal conversations with technical people, I call myself a hacker. But
>> when I'm talking to journalists I just say "programmer" or something like that.
>> -- Linus Torvalds
>>
Hi,
On 10-Jun-25 16:12, Mario Limonciello wrote:
> On 6/10/2025 2:24 AM, Huacai Chen wrote:
>> On Tue, Jun 10, 2025 at 5:16 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>>
>>> Hi Mario,
>>>
>>> CC mips, loongarch
>>>
>>> On Wed, 23 Apr 2025 at 01:49, Mario Limonciello <superm1@kernel.org> wrote:
>>>> From: Mario Limonciello <mario.limonciello@amd.com>
>>>>
>>>> PIIX4 and compatible controllers are only for X86. As some headers are
>>>> being moved into x86 specific headers PIIX4 won't compile on non-x86.
>>>>
>>>> Suggested-by: Ingo Molnar <mingo@kernel.org>
>>>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>>>
>>> Thanks for your patch, which is now commit 7e173eb82ae97175
>>> ("i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86")
>>> in v6.16-rc1.
>>>
>>>> --- a/drivers/i2c/busses/Kconfig
>>>> +++ b/drivers/i2c/busses/Kconfig
>>>> @@ -200,7 +200,7 @@ config I2C_ISMT
>>>>
>>>> config I2C_PIIX4
>>>> tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
>>>> - depends on PCI && HAS_IOPORT
>>>> + depends on PCI && HAS_IOPORT && X86
>>>
>>> Are you sure this south-bridge is not used on non-x86 platforms?
>>> It is enabled in several non-x86 defconfigs:
>>>
>>> arch/loongarch/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>>> arch/mips/configs/ip27_defconfig:CONFIG_I2C_PIIX4=m
>>> arch/mips/configs/loongson2k_defconfig:CONFIG_I2C_PIIX4=y
>>> arch/mips/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>>>
>>> The loongarch and loongson entries are probably bogus, but I wouldn't
>>> be surprised if the SGI Onyx and Origin do use Intel south-bridges.
>> Loongson can use AMD SB700/SB800 south bridges, which have I2C_PIIX4.
>
> Well we could revert this patch, but it's going to be a compile failure because of 624b0d5696a89b138408d385899dd35372db324b and other patches that go on top of that.
>
> My current leaning is we make a dummy fch.h header for these archs with #defines for 0.
Move "fch.h" to include/linux/platform/x86/ so that it is available on all arches
and if necessary ifdef out anything x86 specific in the C-code referencing it ?
Regards,
Hans
Hi,
On 10-Jun-25 16:53, Hans de Goede wrote:
> Hi,
>
> On 10-Jun-25 16:12, Mario Limonciello wrote:
>> On 6/10/2025 2:24 AM, Huacai Chen wrote:
>>> On Tue, Jun 10, 2025 at 5:16 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>>>
>>>> Hi Mario,
>>>>
>>>> CC mips, loongarch
>>>>
>>>> On Wed, 23 Apr 2025 at 01:49, Mario Limonciello <superm1@kernel.org> wrote:
>>>>> From: Mario Limonciello <mario.limonciello@amd.com>
>>>>>
>>>>> PIIX4 and compatible controllers are only for X86. As some headers are
>>>>> being moved into x86 specific headers PIIX4 won't compile on non-x86.
>>>>>
>>>>> Suggested-by: Ingo Molnar <mingo@kernel.org>
>>>>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>>>>
>>>> Thanks for your patch, which is now commit 7e173eb82ae97175
>>>> ("i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86")
>>>> in v6.16-rc1.
>>>>
>>>>> --- a/drivers/i2c/busses/Kconfig
>>>>> +++ b/drivers/i2c/busses/Kconfig
>>>>> @@ -200,7 +200,7 @@ config I2C_ISMT
>>>>>
>>>>> config I2C_PIIX4
>>>>> tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
>>>>> - depends on PCI && HAS_IOPORT
>>>>> + depends on PCI && HAS_IOPORT && X86
>>>>
>>>> Are you sure this south-bridge is not used on non-x86 platforms?
>>>> It is enabled in several non-x86 defconfigs:
>>>>
>>>> arch/loongarch/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>>>> arch/mips/configs/ip27_defconfig:CONFIG_I2C_PIIX4=m
>>>> arch/mips/configs/loongson2k_defconfig:CONFIG_I2C_PIIX4=y
>>>> arch/mips/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>>>>
>>>> The loongarch and loongson entries are probably bogus, but I wouldn't
>>>> be surprised if the SGI Onyx and Origin do use Intel south-bridges.
>>> Loongson can use AMD SB700/SB800 south bridges, which have I2C_PIIX4.
>>
>> Well we could revert this patch, but it's going to be a compile failure because of 624b0d5696a89b138408d385899dd35372db324b and other patches that go on top of that.
>>
>> My current leaning is we make a dummy fch.h header for these archs with #defines for 0.
>
> Move "fch.h" to include/linux/platform/x86/ so that it is available on all arches
> and if necessary ifdef out anything x86 specific in the C-code referencing it ?
Correction that should be include/linux/platform_data/x86/
Regards,
Hans
Hi Hans,
On Tue, 10 Jun 2025 at 16:55, Hans de Goede <hansg@kernel.org> wrote:
> On 10-Jun-25 16:53, Hans de Goede wrote:
> > On 10-Jun-25 16:12, Mario Limonciello wrote:
> >> On 6/10/2025 2:24 AM, Huacai Chen wrote:
> >>> On Tue, Jun 10, 2025 at 5:16 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >>>> On Wed, 23 Apr 2025 at 01:49, Mario Limonciello <superm1@kernel.org> wrote:
> >>>>> From: Mario Limonciello <mario.limonciello@amd.com>
> >>>>>
> >>>>> PIIX4 and compatible controllers are only for X86. As some headers are
> >>>>> being moved into x86 specific headers PIIX4 won't compile on non-x86.
> >>>>>
> >>>>> Suggested-by: Ingo Molnar <mingo@kernel.org>
> >>>>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> >>>>
> >>>> Thanks for your patch, which is now commit 7e173eb82ae97175
> >>>> ("i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86")
> >>>> in v6.16-rc1.
> >>>>
> >>>>> --- a/drivers/i2c/busses/Kconfig
> >>>>> +++ b/drivers/i2c/busses/Kconfig
> >>>>> @@ -200,7 +200,7 @@ config I2C_ISMT
> >>>>>
> >>>>> config I2C_PIIX4
> >>>>> tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
> >>>>> - depends on PCI && HAS_IOPORT
> >>>>> + depends on PCI && HAS_IOPORT && X86
> >>>>
> >>>> Are you sure this south-bridge is not used on non-x86 platforms?
> >>>> It is enabled in several non-x86 defconfigs:
> >>>>
> >>>> arch/loongarch/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
> >>>> arch/mips/configs/ip27_defconfig:CONFIG_I2C_PIIX4=m
> >>>> arch/mips/configs/loongson2k_defconfig:CONFIG_I2C_PIIX4=y
> >>>> arch/mips/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
> >>>>
> >>>> The loongarch and loongson entries are probably bogus, but I wouldn't
> >>>> be surprised if the SGI Onyx and Origin do use Intel south-bridges.
> >>> Loongson can use AMD SB700/SB800 south bridges, which have I2C_PIIX4.
> >>
> >> Well we could revert this patch, but it's going to be a compile failure because of 624b0d5696a89b138408d385899dd35372db324b and other patches that go on top of that.
> >>
> >> My current leaning is we make a dummy fch.h header for these archs with #defines for 0.
> >
> > Move "fch.h" to include/linux/platform/x86/ so that it is available on all arches
> > and if necessary ifdef out anything x86 specific in the C-code referencing it ?
>
> Correction that should be include/linux/platform_data/x86/
Is that a good location?
It is not x86-specific, and I see no platform_data (struct) definitions in
arch/x86/include/asm/amd/fch.h?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Hi Geert,
On 10-Jun-25 18:59, Geert Uytterhoeven wrote:
> Hi Hans,
>
> On Tue, 10 Jun 2025 at 16:55, Hans de Goede <hansg@kernel.org> wrote:
>> On 10-Jun-25 16:53, Hans de Goede wrote:
>>> On 10-Jun-25 16:12, Mario Limonciello wrote:
>>>> On 6/10/2025 2:24 AM, Huacai Chen wrote:
>>>>> On Tue, Jun 10, 2025 at 5:16 PM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>>>>>> On Wed, 23 Apr 2025 at 01:49, Mario Limonciello <superm1@kernel.org> wrote:
>>>>>>> From: Mario Limonciello <mario.limonciello@amd.com>
>>>>>>>
>>>>>>> PIIX4 and compatible controllers are only for X86. As some headers are
>>>>>>> being moved into x86 specific headers PIIX4 won't compile on non-x86.
>>>>>>>
>>>>>>> Suggested-by: Ingo Molnar <mingo@kernel.org>
>>>>>>> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
>>>>>>
>>>>>> Thanks for your patch, which is now commit 7e173eb82ae97175
>>>>>> ("i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86")
>>>>>> in v6.16-rc1.
>>>>>>
>>>>>>> --- a/drivers/i2c/busses/Kconfig
>>>>>>> +++ b/drivers/i2c/busses/Kconfig
>>>>>>> @@ -200,7 +200,7 @@ config I2C_ISMT
>>>>>>>
>>>>>>> config I2C_PIIX4
>>>>>>> tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
>>>>>>> - depends on PCI && HAS_IOPORT
>>>>>>> + depends on PCI && HAS_IOPORT && X86
>>>>>>
>>>>>> Are you sure this south-bridge is not used on non-x86 platforms?
>>>>>> It is enabled in several non-x86 defconfigs:
>>>>>>
>>>>>> arch/loongarch/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>>>>>> arch/mips/configs/ip27_defconfig:CONFIG_I2C_PIIX4=m
>>>>>> arch/mips/configs/loongson2k_defconfig:CONFIG_I2C_PIIX4=y
>>>>>> arch/mips/configs/loongson3_defconfig:CONFIG_I2C_PIIX4=y
>>>>>>
>>>>>> The loongarch and loongson entries are probably bogus, but I wouldn't
>>>>>> be surprised if the SGI Onyx and Origin do use Intel south-bridges.
>>>>> Loongson can use AMD SB700/SB800 south bridges, which have I2C_PIIX4.
>>>>
>>>> Well we could revert this patch, but it's going to be a compile failure because of 624b0d5696a89b138408d385899dd35372db324b and other patches that go on top of that.
>>>>
>>>> My current leaning is we make a dummy fch.h header for these archs with #defines for 0.
>>>
>>> Move "fch.h" to include/linux/platform/x86/ so that it is available on all arches
>>> and if necessary ifdef out anything x86 specific in the C-code referencing it ?
>>
>> Correction that should be include/linux/platform_data/x86/
>
> Is that a good location?
It is a location typically used for x86 headers which we want to be
available when not building on x86 too.
> It is not x86-specific, and I see no platform_data (struct) definitions in
> arch/x86/include/asm/amd/fch.h?
If it is not x86 specific then maybe just include/linux/amd_fch.h ?
Anyways I don't really give much about the exact name, the essence of
my suggestion is that we can fix this by moving fch.h to some place
(and maybe a new name) under include/linux so that the header is also
available when not building for x86.
Regards,
Hans
>
> Gr{oetje,eeting}s,
>
> Geert
>
Hi, On Tue, Apr 22, 2025 at 06:48:27PM -0500, Mario Limonciello wrote: > From: Mario Limonciello <mario.limonciello@amd.com> > > PIIX4 and compatible controllers are only for X86. As some headers are > being moved into x86 specific headers PIIX4 won't compile on non-x86. > > Suggested-by: Ingo Molnar <mingo@kernel.org> > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com> OK, so these are going through x86, at the end. Acked-by: Andi Shyti <andi.shyti@kernel.org> Thanks, Andi
* Andi Shyti <andi.shyti@kernel.org> wrote: > Hi, > > On Tue, Apr 22, 2025 at 06:48:27PM -0500, Mario Limonciello wrote: > > From: Mario Limonciello <mario.limonciello@amd.com> > > > > PIIX4 and compatible controllers are only for X86. As some headers are > > being moved into x86 specific headers PIIX4 won't compile on non-x86. > > > > Suggested-by: Ingo Molnar <mingo@kernel.org> > > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com> > > OK, so these are going through x86, at the end. Yeah, if you don't mind. There's a later x86 patch (5/5) that depends on the new header. > Acked-by: Andi Shyti <andi.shyti@kernel.org> Thanks! I've added your acks to the commits. Ingo
On Sat, Apr 26, 2025 at 11:42:21AM +0200, Ingo Molnar wrote: > * Andi Shyti <andi.shyti@kernel.org> wrote: > > On Tue, Apr 22, 2025 at 06:48:27PM -0500, Mario Limonciello wrote: > > > From: Mario Limonciello <mario.limonciello@amd.com> > > > > > > PIIX4 and compatible controllers are only for X86. As some headers are > > > being moved into x86 specific headers PIIX4 won't compile on non-x86. > > > > > > Suggested-by: Ingo Molnar <mingo@kernel.org> > > > Signed-off-by: Mario Limonciello <mario.limonciello@amd.com> > > > > OK, so these are going through x86, at the end. > > Yeah, if you don't mind. There's a later x86 patch (5/5) that depends > on the new header. sure! > > Acked-by: Andi Shyti <andi.shyti@kernel.org> > > Thanks! I've added your acks to the commits. Thanks! Andi
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 7e173eb82ae97175fd1ae8390259227f1a76a41f
Gitweb: https://git.kernel.org/tip/7e173eb82ae97175fd1ae8390259227f1a76a41f
Author: Mario Limonciello <mario.limonciello@amd.com>
AuthorDate: Tue, 22 Apr 2025 18:48:27 -05:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Sat, 26 Apr 2025 11:40:46 +02:00
i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86
PIIX4 and compatible controllers are only for X86. As some headers are
being moved into x86 specific headers PIIX4 won't compile on non-x86.
Suggested-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Andi Shyti <andi.shyti@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Sanket Goswami <Sanket.Goswami@amd.com>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: linux-i2c@vger.kernel.org
Link: https://lore.kernel.org/r/20250422234830.2840784-3-superm1@kernel.org
---
drivers/i2c/busses/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 83c88c7..bbbd624 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -200,7 +200,7 @@ config I2C_ISMT
config I2C_PIIX4
tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
- depends on PCI && HAS_IOPORT
+ depends on PCI && HAS_IOPORT && X86
select I2C_SMBUS
help
If you say yes to this option, support will be included for the Intel
The following commit has been merged into the x86/platform branch of tip:
Commit-ID: 0e695391f0a33490d8faa5b5e750069230a14c78
Gitweb: https://git.kernel.org/tip/0e695391f0a33490d8faa5b5e750069230a14c78
Author: Mario Limonciello <mario.limonciello@amd.com>
AuthorDate: Tue, 22 Apr 2025 18:48:27 -05:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Thu, 24 Apr 2025 17:55:18 +02:00
i2c: piix4: Make CONFIG_I2C_PIIX4 dependent on CONFIG_X86
PIIX4 and compatible controllers are only for X86. As some headers are
being moved into x86 specific headers PIIX4 won't compile on non-x86.
Suggested-by: Ingo Molnar <mingo@kernel.org>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Cc: Andi Shyti <andi.shyti@kernel.org>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Sanket Goswami <Sanket.Goswami@amd.com>
Cc: Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Cc: Yazen Ghannam <yazen.ghannam@amd.com>
Cc: linux-i2c@vger.kernel.org
Link: https://lore.kernel.org/r/20250422234830.2840784-3-superm1@kernel.org
---
drivers/i2c/busses/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 83c88c7..bbbd624 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -200,7 +200,7 @@ config I2C_ISMT
config I2C_PIIX4
tristate "Intel PIIX4 and compatible (ATI/AMD/Serverworks/Broadcom/SMSC)"
- depends on PCI && HAS_IOPORT
+ depends on PCI && HAS_IOPORT && X86
select I2C_SMBUS
help
If you say yes to this option, support will be included for the Intel
© 2016 - 2026 Red Hat, Inc.