From: Akshay Gupta <akshay.gupta@amd.com>
To: <linux-hwmon@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <linux@roeck-us.net>, <gregkh@linuxfoundation.org>,
<arnd@arndb.de>, <shyam-sundar.s-k@amd.com>,
<gautham.shenoy@amd.com>, <mario.limonciello@amd.com>,
<naveenkrishna.chatradhi@amd.com>, <anand.umarji@amd.com>,
Akshay Gupta <akshay.gupta@amd.com>
Subject: [PATCH v7 09/10] misc: amd-sbi: Add support for register xfer
Date: Wed, 2 Apr 2025 05:58:39 +0000 [thread overview]
Message-ID: <20250402055840.1346384-10-akshay.gupta@amd.com> (raw)
In-Reply-To: <20250402055840.1346384-1-akshay.gupta@amd.com>
- Provide user register access over IOCTL.
Both register read and write are supported.
- APML interface does not provide a synchronization method. By defining,
a register access path, we use APML modules and library for
all APML transactions. Without having to use external tools such as
i2c-tools, which may cause race conditions.
Reviewed-by: Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>
Signed-off-by: Akshay Gupta <akshay.gupta@amd.com>
---
Changes since v6:
- Rebased patch, previously patch 10
Changes since v5:
- Patch rebased
Changes since v4:
- Previously patch 8
- Address review comment for documentation warning
Changes since v3:
- Add ioctl description comment
Changes since v2:
- update the MACROS name as per feedback
Changes since v1:
- bifurcated from previous patch 5
drivers/misc/amd-sbi/rmi-core.c | 25 +++++++++++++++++++++++++
include/uapi/misc/amd-apml.h | 4 ++++
2 files changed, 29 insertions(+)
diff --git a/drivers/misc/amd-sbi/rmi-core.c b/drivers/misc/amd-sbi/rmi-core.c
index 463bfc18dc22..6d092e0f4b48 100644
--- a/drivers/misc/amd-sbi/rmi-core.c
+++ b/drivers/misc/amd-sbi/rmi-core.c
@@ -349,6 +349,27 @@ int rmi_mailbox_xfer(struct sbrmi_data *data,
return ret;
}
+static int rmi_register_xfer(struct sbrmi_data *data,
+ struct apml_message *msg)
+{
+ int ret;
+
+ if (WARN_ON(!msg))
+ return -EINVAL;
+
+ mutex_lock(&data->lock);
+ if (msg->data_in.reg_in[AMD_SBI_RD_FLAG_INDEX])
+ ret = regmap_read(data->regmap,
+ msg->data_in.reg_in[AMD_SBI_REG_OFF_INDEX],
+ &msg->data_out.mb_out[AMD_SBI_RD_WR_DATA_INDEX]);
+ else
+ ret = regmap_write(data->regmap,
+ msg->data_in.reg_in[AMD_SBI_REG_OFF_INDEX],
+ msg->data_in.reg_in[AMD_SBI_REG_VAL_INDEX]);
+ mutex_unlock(&data->lock);
+ return ret;
+}
+
static long sbrmi_ioctl(struct file *fp, unsigned int cmd, unsigned long arg)
{
struct apml_message msg = { 0 };
@@ -382,6 +403,10 @@ static long sbrmi_ioctl(struct file *fp, unsigned int cmd, unsigned long arg)
/* MCAMSR protocol */
ret = rmi_mca_msr_read(data, &msg);
break;
+ case APML_REG:
+ /* REG R/W */
+ ret = rmi_register_xfer(data, &msg);
+ break;
default:
return -EINVAL;
}
diff --git a/include/uapi/misc/amd-apml.h b/include/uapi/misc/amd-apml.h
index 9993fa49460e..9e44621b0dfe 100644
--- a/include/uapi/misc/amd-apml.h
+++ b/include/uapi/misc/amd-apml.h
@@ -10,6 +10,7 @@
enum apml_protocol {
APML_CPUID = 0x1000,
APML_MCA_MSR,
+ APML_REG,
};
/* These are byte indexes into data_in and data_out arrays */
@@ -27,6 +28,7 @@ struct apml_message {
/*
* [0]...[3] mailbox 32bit input
* cpuid & mca msr,
+ * rmi rd/wr: reg_offset
* [4][5] cpuid & mca msr: thread
* [4] rmi reg wr: value
* [6] cpuid: ext function & read eax/ebx or ecx/edx
@@ -53,6 +55,7 @@ struct apml_message {
* Mailbox Messages: 0x0 ... 0x999
* APML_CPUID: 0x1000
* APML_MCA_MSR: 0x1001
+ * APML_REG: 0x1002
*/
__u32 cmd;
/*
@@ -85,6 +88,7 @@ struct apml_message {
* - Mailbox message read/write(0x0~0x999)
* - CPUID read(0x1000)
* - MCAMSR read(0x1001)
+ * - Register read/write(0x1002)
* - returning "-EFAULT" if none of the above
* "-EPROTOTYPE" error is returned to provide additional error details
*/
--
2.25.1
next prev parent reply other threads:[~2025-04-02 5:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 5:58 [PATCH v7 00/10] misc: Move AMD side band interface(SBI) functionality Akshay Gupta
2025-04-02 5:58 ` [PATCH v7 01/10] hwmon/misc: amd-sbi: Move core sbrmi from hwmon to misc Akshay Gupta
2025-04-02 5:58 ` [PATCH v7 02/10] misc: amd-sbi: Move protocol functionality to core file Akshay Gupta
2025-04-02 5:58 ` [PATCH v7 03/10] misc: amd-sbi: Move hwmon device sensor as separate entity Akshay Gupta
2025-04-02 11:03 ` Arnd Bergmann
2025-04-07 11:31 ` Gupta, Akshay
2025-04-02 5:58 ` [PATCH v7 04/10] misc: amd-sbi: Use regmap subsystem Akshay Gupta
2025-04-02 5:58 ` [PATCH v7 05/10] misc: amd-sbi: Optimize the wait condition for mailbox command completion Akshay Gupta
2025-04-02 5:58 ` [PATCH v7 06/10] misc: amd-sbi: Add support for AMD_SBI IOCTL Akshay Gupta
2025-04-02 5:58 ` [PATCH v7 07/10] misc: amd-sbi: Add support for CPUID protocol Akshay Gupta
2025-04-02 12:13 ` Arnd Bergmann
2025-04-02 12:16 ` Greg Kroah-Hartman
2025-04-07 11:31 ` Gupta, Akshay
2025-04-02 5:58 ` [PATCH v7 08/10] misc: amd-sbi: Add support for read MCA register protocol Akshay Gupta
2025-04-02 5:58 ` Akshay Gupta [this message]
2025-04-02 5:58 ` [PATCH v7 10/10] misc: amd-sbi: Add document for AMD SB IOCTL description Akshay Gupta
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=20250402055840.1346384-10-akshay.gupta@amd.com \
--to=akshay.gupta@amd.com \
--cc=anand.umarji@amd.com \
--cc=arnd@arndb.de \
--cc=gautham.shenoy@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mario.limonciello@amd.com \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=shyam-sundar.s-k@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