Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Clemens Ladisch <clemens@ladisch.de>,
	Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	"open list:K10TEMP HARDWARE MONITORING DRIVER" 
	<linux-hwmon@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Cc: <linux-hwmon@vger.kernel.org>, <babu.moger@amd.com>,
	<yazen.ghannam@amd.com>, <linux-kernel@vger.kernel.org>,
	<x86@kernel.org>, Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v2 6/6] hwmon: (k10temp): Add support for family 19h models 60h-6Fh
Date: Thu, 2 Jun 2022 15:11:37 -0500	[thread overview]
Message-ID: <20220602201137.1415-7-mario.limonciello@amd.com> (raw)
In-Reply-To: <20220602201137.1415-1-mario.limonciello@amd.com>

Add the support for CCD offsets used on family 19h models 60h-6Fh.

Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
---
 drivers/hwmon/k10temp.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/hwmon/k10temp.c b/drivers/hwmon/k10temp.c
index 5f37e2e7833e..5a9d47a229e4 100644
--- a/drivers/hwmon/k10temp.c
+++ b/drivers/hwmon/k10temp.c
@@ -449,6 +449,7 @@ static int k10temp_probe(struct pci_dev *pdev, const struct pci_device_id *id)
 			data->ccd_offset = 0x300;
 			k10temp_get_ccd_support(pdev, data, 8);
 			break;
+		case 0x60 ... 0x6f:
 		case 0x70 ... 0x7f:
 			data->ccd_offset = 0x308;
 			k10temp_get_ccd_support(pdev, data, 8);
@@ -502,6 +503,7 @@ static const struct pci_device_id k10temp_id_table[] = {
 	{ PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_19H_M10H_DF_F3) },
 	{ PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_19H_M40H_DF_F3) },
 	{ PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_19H_M50H_DF_F3) },
+	{ PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_19H_M60H_DF_F3) },
 	{ PCI_VDEVICE(AMD, PCI_DEVICE_ID_AMD_19H_M70H_DF_F3) },
 	{ PCI_VDEVICE(HYGON, PCI_DEVICE_ID_AMD_17H_DF_F3) },
 	{}
-- 
2.34.1


  parent reply	other threads:[~2022-06-02 20:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-02 20:11 [PATCH v2 0/6] Add support for upcoming chips to k10temp and amd_nb Mario Limonciello
2022-06-02 20:11 ` [PATCH v2 1/6] x86/amd_nb: Add AMD Family 17h A0-AF IDs Mario Limonciello
2022-06-07 13:00   ` Guenter Roeck
2022-06-08 20:13   ` Bjorn Helgaas
2022-06-10 16:37   ` Yazen Ghannam
2022-06-02 20:11 ` [PATCH v2 2/6] x86/amd_nb: Add Family 19h model 70h-7Fh IDs Mario Limonciello
2022-06-02 21:05   ` Guenter Roeck
2022-06-10 16:46   ` Yazen Ghannam
2022-06-02 20:11 ` [PATCH v2 3/6] x86/amd_nb: Add Family 19h model 60h-6Fh IDs Mario Limonciello
2022-06-10 16:49   ` Yazen Ghannam
2022-06-02 20:11 ` [PATCH v2 4/6] hwmon: (k10temp): Add support for family 17h models A0h-AFh Mario Limonciello
2022-06-02 21:06   ` Guenter Roeck
2022-06-02 20:11 ` [PATCH v2 5/6] hwmon: (k10temp): Add support for family 19h models 70h-7Fh Mario Limonciello
2022-06-02 21:06   ` Guenter Roeck
2022-06-02 20:11 ` Mario Limonciello [this message]
2022-06-02 21:06   ` [PATCH v2 6/6] hwmon: (k10temp): Add support for family 19h models 60h-6Fh Guenter Roeck

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=20220602201137.1415-7-mario.limonciello@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=babu.moger@amd.com \
    --cc=clemens@ladisch.de \
    --cc=jdelvare@suse.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=x86@kernel.org \
    --cc=yazen.ghannam@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