From: "Gupta, Akshay" <Akshay.Gupta@amd.com>
To: Arnd Bergmann <arnd@arndb.de>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Guenter Roeck <linux@roeck-us.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
shyam-sundar.s-k@amd.com, gautham.shenoy@amd.com,
Mario Limonciello <mario.limonciello@amd.com>,
naveenkrishna.chatradhi@amd.com, anand.umarji@amd.com
Subject: Re: [PATCH v8 00/10] misc: Move AMD side band interface(SBI) functionality
Date: Tue, 15 Apr 2025 15:05:16 +0530 [thread overview]
Message-ID: <42ef1aaa-014a-4201-ba47-e7350d2989a6@amd.com> (raw)
In-Reply-To: <06b76e0f-0b47-47ea-a48f-2bf09ac4a62c@app.fastmail.com>
On 4/11/2025 7:21 PM, Arnd Bergmann wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> On Fri, Apr 11, 2025, at 15:31, Akshay Gupta wrote:
>> At present, sbrmi driver under hwmon subsystem, is probed as an i2c
>> driver,
>> fetches data using APML specified protocol and reports through hwmon
>> power sensor.
>>
>> AMD provides additional information using custom protocols, which cannot be
>> enumerated as hwmon sensors. Hence, move the existing functionality from hwmon/
>> to misc/ and add support for following custom protocols
>> - read Processor feature capabilities and configuration information
>> through side band.
>> - read Machine Check Architecture(MCA) registers over sideband.
>> The information is accessed for range of MCA registers by passing
>> register address and thread ID to the protocol.
>>
>> NOTE: AMD defines Advanced Platform Management Link (APML) interface
>> which provides
>> system management functionality access to the baseboard management
>> controller (BMC).
> I think this addresses all my comments, thanks for the update.
>
>> Open-sourced and widely used [1]_ will continue to provide user-space
>> programmable API.
>>
>> .. [1] https://github.com/amd/esmi_oob_library
> I'm still a little uneasy about the low-level mailbox interface
> being exposed in a character device, but assuming that everyone
> else is fine with having that in principle, I think the way the
> interface is structured in this version is good enough.
>
> Arnd
Thank you for quick review.
I see a kernel test robot error in patch 09/10, where require to use
"__u16" instead of "u16" in the structure. I will submit patch version 9
to address this.
Can I add your "Reviewed-by:" for the other patches?
prev parent reply other threads:[~2025-04-15 9:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 13:31 [PATCH v8 00/10] misc: Move AMD side band interface(SBI) functionality Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 01/10] hwmon/misc: amd-sbi: Move core sbrmi from hwmon to misc Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 02/10] misc: amd-sbi: Move protocol functionality to core file Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 03/10] misc: amd-sbi: Move hwmon device sensor as separate entity Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 04/10] misc: amd-sbi: Use regmap subsystem Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 05/10] misc: amd-sbi: Optimize the wait condition for mailbox command completion Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 06/10] misc: amd-sbi: Add support for AMD_SBI IOCTL Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 07/10] misc: amd-sbi: Add support for CPUID protocol Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 08/10] misc: amd-sbi: Add support for read MCA register protocol Akshay Gupta
2025-04-11 13:31 ` [PATCH v8 09/10] misc: amd-sbi: Add support for register xfer Akshay Gupta
2025-04-14 5:55 ` kernel test robot
2025-04-11 13:31 ` [PATCH v8 10/10] misc: amd-sbi: Add document for AMD SB IOCTL description Akshay Gupta
2025-04-11 13:51 ` [PATCH v8 00/10] misc: Move AMD side band interface(SBI) functionality Arnd Bergmann
2025-04-15 9:35 ` Gupta, Akshay [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=42ef1aaa-014a-4201-ba47-e7350d2989a6@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