From: Basavaraj Natikar <bnatikar@amd.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Basavaraj Natikar <Basavaraj.Natikar@amd.com>,
benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH hid-next] HID: amd_sfh: Fix build error without x86 kconfig
Date: Wed, 28 Feb 2024 16:29:32 +0530 [thread overview]
Message-ID: <085813e1-3001-49cc-b9fd-6a09961a0797@amd.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.2402281156370.21798@cbobk.fhfr.pm>
On 2/28/2024 4:27 PM, Jiri Kosina wrote:
> On Wed, 28 Feb 2024, Basavaraj Natikar wrote:
>
>>>> diff --git a/drivers/hid/amd-sfh-hid/amd_sfh_pcie.c b/drivers/hid/amd-sfh-hid/amd_sfh_pcie.c
>>>> index 9e97c26c4482..c815f2f54321 100644
>>>> --- a/drivers/hid/amd-sfh-hid/amd_sfh_pcie.c
>>>> +++ b/drivers/hid/amd-sfh-hid/amd_sfh_pcie.c
>>>> @@ -410,8 +410,10 @@ static int amd_mp2_pci_probe(struct pci_dev *pdev, const struct pci_device_id *i
>>>>
>>>> privdata->sfh1_1_ops = (const struct amd_sfh1_1_ops *)id->driver_data;
>>>> if (privdata->sfh1_1_ops) {
>>>> +#ifdef CONFIG_X86
>>>> if (boot_cpu_data.x86 >= 0x1A)
>>>> privdata->rver = 1;
>>>> +#endif
>>> Does it even make sense to build this driver outside of x86 architecture?
>> Do you mean to say just add depends on X86 like below ?
>> "
>> config AMD_SFH_HID
>> tristate "AMD Sensor Fusion Hub"
>> depends on HID
>> + depends on X86
>> help
>> If you say yes to this option, support will be included for the
>> AMD Sensor Fusion Hub.
>> "
> Yeah, that was my idea; as far as I understand, there is no way this
> driver would ever have any use outside of x86 architecture, right?
Yes that correct this driver is only for x86, I will send V2 with this change.
Thanks,
--
BAsavaraj
>
> Thanks,
>
prev parent reply other threads:[~2024-02-28 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 7:51 [PATCH hid-next] HID: amd_sfh: Fix build error without x86 kconfig Basavaraj Natikar
2024-02-28 9:03 ` Jiri Kosina
2024-02-28 10:52 ` Basavaraj Natikar
2024-02-28 10:57 ` Jiri Kosina
2024-02-28 10:59 ` Basavaraj Natikar [this message]
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=085813e1-3001-49cc-b9fd-6a09961a0797@amd.com \
--to=bnatikar@amd.com \
--cc=Basavaraj.Natikar@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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