From: Yazen Ghannam <yazen.ghannam@amd.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: yazen.ghannam@amd.com, x86@kernel.org,
linux-kernel@vger.kernel.org,
platform-driver-x86@vger.kernel.org, markgross@kernel.org,
hdegoede@redhat.com, Shyam-sundar.S-k@amd.com,
linux-edac@vger.kernel.org, clemens@ladisch.de,
jdelvare@suse.com, linux-hwmon@vger.kernel.org,
mario.limonciello@amd.com, babu.moger@amd.com
Subject: Re: [PATCH 5/6] hwmon: (k10temp) Define helper function to read CCD temp
Date: Wed, 17 May 2023 10:09:12 -0400 [thread overview]
Message-ID: <485dbd08-7616-09e3-c9eb-de0a1f78572b@amd.com> (raw)
In-Reply-To: <f61f548b-0007-404e-9c9d-d84a2a657983@roeck-us.net>
On 5/17/23 8:30 AM, Guenter Roeck wrote:
> On Tue, May 16, 2023 at 03:24:29PM -0500, Yazen Ghannam wrote:
>> The CCD temperature register is read in two places. These reads are done
>> using an AMD SMN access, and a number of parameters are needed for the
>> operation.
>>
>> Move the SMN access and parameter gathering into a helper function in
>> order to simply the code flow. This also has a benefit of centralizing
>> the hardware register access in a single place in case fixes or special
>> decoding is required.
>>
>> Signed-off-by: Yazen Ghannam <yazen.ghannam@amd.com>
>> ---
>> drivers/hwmon/k10temp.c | 19 ++++++++++++++-----
>> 1 file changed, 14 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/hwmon/k10temp.c b/drivers/hwmon/k10temp.c
>> index 6ea1fa62b7c1..06af1fe38af7 100644
>> --- a/drivers/hwmon/k10temp.c
>> +++ b/drivers/hwmon/k10temp.c
>> @@ -150,6 +150,18 @@ static void read_tempreg_nb_zen(struct pci_dev *pdev, u32 *regval)
>> *regval = 0;
>> }
>>
>> +static int read_ccd_temp_reg(struct k10temp_data *data, int ccd, u32 *regval)
>> +{
>> + u16 node_id = amd_pci_dev_to_node_id(data->pdev);
>> + u32 tmp;
>> +
>> + if (amd_smn_read(node_id, ZEN_CCD_TEMP(data->ccd_offset, ccd), &tmp))
>> + return -EINVAL;
>
> As mentioned before, this is not appropriate. The error code
> from amd_smn_read() should be returned.
>
Okay, will do.
>> +
>> + *regval = tmp;
>
> This seems pointless. Why not just pass regval as parameter
> to amd_smn_read() ?
>
> This function should be reduced to
>
> return amd_smn_read(node_id, ZEN_CCD_TEMP(data->ccd_offset, ccd), regval));
>
Yes, will do. I think I got carried away with the "don't save invalid
value" idea. But this isn't necessary if the caller checks the return
code and avoids using the value.
>> + return 0;
>> +}
>> +
>> static long get_raw_temp(struct k10temp_data *data)
>> {
>> u32 regval;
>> @@ -214,9 +226,7 @@ static int k10temp_read_temp(struct device *dev, u32 attr, int channel,
>> *val = 0;
>> break;
>> case 2 ... 13: /* Tccd{1-12} */
>> - if (amd_smn_read(amd_pci_dev_to_node_id(data->pdev),
>> - ZEN_CCD_TEMP(data->ccd_offset, channel - 2),
>> - ®val))
>> + if (read_ccd_temp_reg(data, channel - 2, ®val))
>> return -EINVAL;
>
> Now this is really wrong, no matter what. Why bother replacing the
> error code in read_ccd_temp_reg() only to replace it again ?
>
Understood. Will fix like the other places.
Thanks,
Yazen
next prev parent reply other threads:[~2023-05-17 14:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-16 20:24 [PATCH 0/6] Enhance AMD SMN Error Checking Yazen Ghannam
2023-05-16 20:24 ` [PATCH 1/6] EDAC/amd64: Remove unused register accesses Yazen Ghannam
2023-05-16 20:24 ` [PATCH 2/6] EDAC/amd64: Check return value of amd_smn_read() Yazen Ghannam
2023-05-16 20:24 ` [PATCH 3/6] hwmon: (k10temp) " Yazen Ghannam
2023-05-17 12:25 ` Guenter Roeck
2023-05-17 14:04 ` Yazen Ghannam
2023-05-16 20:24 ` [PATCH 4/6] x86/amd_nb: Enhance SMN access error checking Yazen Ghannam
2023-05-16 20:24 ` [PATCH 5/6] hwmon: (k10temp) Define helper function to read CCD temp Yazen Ghannam
2023-05-17 12:30 ` Guenter Roeck
2023-05-17 14:09 ` Yazen Ghannam [this message]
2023-05-16 20:24 ` [PATCH 6/6] hwmon: (k10temp) Reduce k10temp_get_ccd_support() parameters Yazen Ghannam
2023-05-17 12:33 ` 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=485dbd08-7616-09e3-c9eb-de0a1f78572b@amd.com \
--to=yazen.ghannam@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=babu.moger@amd.com \
--cc=clemens@ladisch.de \
--cc=hdegoede@redhat.com \
--cc=jdelvare@suse.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mario.limonciello@amd.com \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=x86@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
all inboxes | Powered by JetHome®