From: "Gupta, Akshay" <Akshay.Gupta@amd.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@roeck-us.net, arnd@arndb.de,
naveenkrishna.chatradhi@amd.com
Subject: Re: [PATCH 0/6] misc: add amd side-band functionality
Date: Thu, 4 Jul 2024 20:17:22 +0530 [thread overview]
Message-ID: <9b108208-cb52-68d8-8a16-8a33c3824d74@amd.com> (raw)
In-Reply-To: <2024070416-cosponsor-barrack-6125@gregkh>
On 7/4/2024 5:18 PM, Greg KH wrote:
> Caution: This message originated from an External Source. Use proper caution when opening attachments, clicking links, or responding.
>
>
> On Thu, Jul 04, 2024 at 11:16:18AM +0000, Akshay Gupta wrote:
>> AMD's APML interface provides system management functionality accessed by
>> the BMC. Sbrmi driver under hwmon subsystem, which is probed as an i2c
>> driver and reports power using APML specified protocol.
> What is "APML"? What is "BMC"?
My bad, I will provide expansion for the acronyms in the first usage.
>
>> However, APML interface defines few other protocols to support
>> full system management functionality out-of-band.
> What is out-of-band here?
Out-of-band management is term used for Baseboard Management Controller
(BMC) talking to
system management unit(IP in the processor, AMD's documentation called
this link as side band interface.
We are using the terms out-of-band and side band interface as per context.
>
>> This patchset is an attempt to add all APML core functionality in one place
>> and provide hwmon and user interface
>> 1. Move the i2c client probe and sbrmi core functionality from drivers/hwmon
>> to drivers/misc/
>> 2. Add a platform device, which probes the hwmon/sbrmi and continues to
>> report power using the symbol exported by the misc/sbrmi-core.
> Are you sure this is a platform device? It better not be a pci one...
It is not a pci device, will remove the platform device and register
hwmon device in misc.
>
>> 3. Convert i2c to regmap which provides multiple benefits
>> over direct smbus APIs.
> What are those?
We are planning to add i2c/i3c support and 1byte/2 byte register addressing.
>
>> 4. Register a misc device which provides
>> a. An ioctl interface through node /dev/sbrmiX
> Why?
>
>> b. Open-sourced and widely used https://github.com/amd/esmi_oob_library
>> will continue to provide user-space programmable API.
> Will this use the new ioctl api? If it's not present, what will it use
> instead?
This is an attempt to upstream the out of tree kernel module(which
defines this ioctl), open sourced at:
https://github.com/amd/apml_modules/ and continue to support
https://github.com/amd/esmi_oob_library
which depends only on this ioctl.
Thanks,
Akshay
> thanks,
>
> greg k-h
prev parent reply other threads:[~2024-07-04 14:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 11:16 [PATCH 0/6] misc: add amd side-band functionality Akshay Gupta
2024-07-04 11:16 ` [PATCH 1/6] hwmon/misc sbrmi: Move core sbrmi from hwmon to misc Akshay Gupta
2024-07-04 11:47 ` Greg KH
2024-07-04 13:57 ` Gupta, Akshay
2024-07-04 11:16 ` [PATCH 2/6] misc: sbrmi: Add platform device add to create platform device Akshay Gupta
2024-07-04 11:50 ` Greg KH
2024-07-04 14:13 ` Gupta, Akshay
2024-07-04 11:16 ` [PATCH 3/6] misc: sbrmi: Use regmap subsystem Akshay Gupta
2024-07-04 11:53 ` Greg KH
2024-07-04 14:26 ` Gupta, Akshay
2024-07-04 11:16 ` [PATCH 4/6] misc: sbrmi: Clear sbrmi status register bit SwAlertSts Akshay Gupta
2024-07-04 11:16 ` [PATCH 5/6] misc/hwmon: sbrmi: Add support for APML protocols Akshay Gupta
2024-07-04 11:16 ` [PATCH 6/6] misc: sbrmi: Add support for new revision Akshay Gupta
2024-07-04 11:54 ` Greg KH
2024-07-04 14:28 ` Gupta, Akshay
2024-07-04 11:48 ` [PATCH 0/6] misc: add amd side-band functionality Greg KH
2024-07-04 14:47 ` 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=9b108208-cb52-68d8-8a16-8a33c3824d74@amd.com \
--to=akshay.gupta@amd.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=naveenkrishna.chatradhi@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