linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Wei Huang <wei.huang2@amd.com>, Borislav Petkov <bp@alien8.de>,
	David Bartley <andareed@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-x86_64@vger.kernel.org
Subject: Re: [PATCH] x86/amd_nb: add AMD family 19h model 50h PCI ids
Date: Fri, 21 May 2021 10:45:53 -0700	[thread overview]
Message-ID: <13e9db0f-a1d7-8699-a7d9-90246c7df553@roeck-us.net> (raw)
In-Reply-To: <2ba654b5-1c08-85da-b932-9d5a92d5c930@amd.com>

On 5/21/21 9:05 AM, Wei Huang wrote:
> 
> 
> On 5/21/21 5:10 AM, Borislav Petkov wrote:
>> On Thu, May 20, 2021 at 10:41:30AM -0700, David Bartley wrote:
>>> This is required to support Zen3 APUs in k10temp.
>>>
>>> Signed-off-by: David Bartley <andareed@gmail.com>
>>> ---
>>>   arch/x86/kernel/amd_nb.c | 3 +++
>>>   include/linux/pci_ids.h  | 1 +
>>>   2 files changed, 4 insertions(+)
>>>
>>> diff --git a/arch/x86/kernel/amd_nb.c b/arch/x86/kernel/amd_nb.c
>>> index 09083094eb57..23dda362dc0f 100644
>>> --- a/arch/x86/kernel/amd_nb.c
>>> +++ b/arch/x86/kernel/amd_nb.c
>>> @@ -25,6 +25,7 @@
>>>   #define PCI_DEVICE_ID_AMD_17H_M60H_DF_F4 0x144c
>>>   #define PCI_DEVICE_ID_AMD_17H_M70H_DF_F4 0x1444
>>>   #define PCI_DEVICE_ID_AMD_19H_DF_F4    0x1654
>>> +#define PCI_DEVICE_ID_AMD_19H_M50H_DF_F4 0x166e
>>>   /* Protect the PCI config register pairs used for SMN and DF indirect access. */
>>>   static DEFINE_MUTEX(smn_mutex);
>>> @@ -57,6 +58,7 @@ static const struct pci_device_id amd_nb_misc_ids[] = {
>>>       { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_CNB17H_F3) },
>>>       { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_17H_M70H_DF_F3) },
>>>       { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_19H_DF_F3) },
>>> +    { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_19H_M50H_DF_F3) },
>>>       {}
>>>   };
>>> @@ -72,6 +74,7 @@ static const struct pci_device_id amd_nb_link_ids[] = {
>>>       { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_17H_M60H_DF_F4) },
>>>       { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_17H_M70H_DF_F4) },
>>>       { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_19H_DF_F4) },
>>> +    { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_19H_M50H_DF_F4) },
>>>       { PCI_DEVICE(PCI_VENDOR_ID_AMD, PCI_DEVICE_ID_AMD_CNB17H_F4) },
>>>       {}
>>>   };
>>> diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
>>> index 4c3fa5293d76..5356ccf1c275 100644
>>> --- a/include/linux/pci_ids.h
>>> +++ b/include/linux/pci_ids.h
>>> @@ -555,6 +555,7 @@
>>>   #define PCI_DEVICE_ID_AMD_17H_M60H_DF_F3 0x144b
>>>   #define PCI_DEVICE_ID_AMD_17H_M70H_DF_F3 0x1443
>>>   #define PCI_DEVICE_ID_AMD_19H_DF_F3    0x1653
>>> +#define PCI_DEVICE_ID_AMD_19H_M50H_DF_F3 0x166d
>>
>> I don't see this define used anywhere else besides amd_nb.c. If there's
>> no use for it outside of that file, I'm moving it there...?
>>
>> Or does it need to get added to that k10temp_id_table in k10temp.c too?
> 
> [+Guenter]
> 
> I think it needs to be added to k10temp.c as well. In the meanwhile, k10temp_probe() shall be extended with support for family 19h, model 0x5x.
> 

Yes, it does [1]. Fine with me though to define it locally there.
I personally find that easier since it would avoid the recurring
"I don't see this define used anywhere else besides xxx".
Someone else can clean that up later if so desired.

Thanks,
Guenter

---
[1] https://patchwork.kernel.org/project/linux-hwmon/patch/20210517064131.4369-1-andareed@gmail.com/

  reply	other threads:[~2021-05-21 17:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20 17:41 [PATCH] x86/amd_nb: add AMD family 19h model 50h PCI ids David Bartley
2021-05-20 21:36 ` Wei Huang
2021-05-20 22:45   ` Borislav Petkov
2021-05-20 22:47     ` Wei Huang
2021-05-21 10:10 ` Borislav Petkov
2021-05-21 16:05   ` Wei Huang
2021-05-21 17:45     ` Guenter Roeck [this message]
2021-05-21 18:43       ` Borislav Petkov
2021-05-25 12:52 ` [tip: x86/cpu] x86/amd_nb: Add " tip-bot2 for David Bartley

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=13e9db0f-a1d7-8699-a7d9-90246c7df553@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=andareed@gmail.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-x86_64@vger.kernel.org \
    --cc=wei.huang2@amd.com \
    /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;
as well as URLs for NNTP newsgroup(s).