From: "Wang, Haiyue" <haiyue.wang@linux.intel.com>
To: Joel Stanley <joel@jms.id.au>, Corey Minyard <minyard@acm.org>,
Ed Tanous <ed.tanous@intel.com>,
james.mihm@intel.com, OpenBMC Maillist <openbmc@lists.ozlabs.org>,
tomer.maimon@nuvoton.com
Cc: openipmi-developer@lists.sourceforge.net,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
andriy.shevchenko@intel.com
Subject: Re: [PATCH arm/aspeed/ast2500 v1] ipmi: add an Aspeed KCS IPMI BMC driver
Date: Wed, 17 Jan 2018 14:32:36 +0800 [thread overview]
Message-ID: <f802a1fd-7553-d8cd-937c-6066b1db150e@linux.intel.com> (raw)
In-Reply-To: <CACPK8XfmrtJkUcFXNRDh7t3EDaETU1R=RawkErgduPG--CEVEg@mail.gmail.com>
On 2018-01-17 07:06, Joel Stanley wrote:
> On Tue, Jan 16, 2018 at 2:59 PM, Corey Minyard <minyard@acm.org> wrote:
>> On 01/16/2018 05:43 AM, Haiyue Wang wrote:
>>> The KCS (Keyboard Controller Style) interface is used to perform in-band
>>> IPMI communication between a server host and its BMC (BaseBoard Management
>>> Controllers).
>>>
>>> This driver exposes the KCS interface on ASpeed SOCs (AST2400 and AST2500)
>>> as a character device. Such SOCs are commonly used as BMCs and this driver
>>> implements the BMC side of the KCS interface.
>>
>> I thought we were going to unify the BMC ioctl interface? My preference
>> would be to
>> create a file named include/uapi/linux/ipmi-bmc.h and add the following:
>>
>> #define __IPMI_BMC_IOCTL_MAGIC 0xb1
>> #define IPMI_BMC_IOCTL_SMS_SET_ATN _IO(__IPMI_BMC_IOCTL_MAGIC, 0x00)
>>
>> to make it the same as BT. Then in bt-bmc.h, set BT_BMC_IOCTL_SMS_ATN to
>> IPMI_BMC_IOCTL_SMS_SET_ATN. Then add the KCS ioctls in ipmi-bmc.h and
>> use that. That way we stay backward compatible but we are unified.
>>
>> Since more KCS interfaces may come around, can you make the name more
>> specific? (I made this same error on bt-bmc,c, it should probably be
>> renamed.)
> Yes, we had a group of openbmc people get together recently and spoke
> about this. Unfortunately Haiyue wasn't there (but other Intel BMC
> people were).
>
> We've got code coming from another BMC vendor who will use the same
> userspace API. The intention is to unify ASPEED's KCS and BT, along
> with Nuvoton's KCS and BT, as you outlined above.
Great design for common BMC code, thanks Joel & Corey.
Then we need to divide the kcs-bmc.c into two files, one (still
kcs-bmc.c) is for handling IPMI KCS state
according to IPMI 2.0 specification, and also handing device misc
operations; another file is called such
as aspeed-kcs-bmc.c which handles ast2500 kcs controller. So that
Nuvoton can define nvvoton-kcs-bmc.c
low level API, and call the IPMI KCS function in kcs-bmc.c ?
How about this idea ? If it makes sense, I will change the code for
review in patch v2.
> Cheers,
>
> Joel
next prev parent reply other threads:[~2018-01-17 6:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 11:43 [PATCH arm/aspeed/ast2500 v1] ipmi: add an Aspeed KCS IPMI BMC driver Haiyue Wang
2018-01-16 20:59 ` Corey Minyard
2018-01-16 22:12 ` Corey Minyard
2018-01-17 14:31 ` Wang, Haiyue
2018-01-17 15:59 ` Corey Minyard
2018-01-18 0:16 ` Wang, Haiyue
2018-01-18 2:58 ` Corey Minyard
2018-01-18 3:10 ` Wang, Haiyue
2018-01-17 16:31 ` Corey Minyard
2018-01-18 0:57 ` Wang, Haiyue
2018-01-16 23:06 ` Joel Stanley
2018-01-17 6:32 ` Wang, Haiyue [this message]
2018-01-17 12:54 ` Avi Fishman
2018-01-17 14:34 ` Wang, Haiyue
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=f802a1fd-7553-d8cd-937c-6066b1db150e@linux.intel.com \
--to=haiyue.wang@linux.intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=ed.tanous@intel.com \
--cc=james.mihm@intel.com \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openbmc@lists.ozlabs.org \
--cc=openipmi-developer@lists.sourceforge.net \
--cc=tomer.maimon@nuvoton.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