linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tcminyard@gmail.com (Corey Minyard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] misc: Add Aspeed BT IPMI host driver
Date: Mon, 12 Sep 2016 15:33:57 -0500	[thread overview]
Message-ID: <7db5ada0-49ea-55eb-089e-d979941ceff5@gmail.com> (raw)
In-Reply-To: <4727554.yt7pF8chOH@wuerfel>

On 09/12/2016 02:15 PM, Arnd Bergmann wrote:
> On Monday, September 12, 2016 1:55:40 PM CEST Corey Minyard wrote:
>> On 09/02/2016 08:22 AM, C?dric Le Goater wrote:
>>> Hello,
>>>
>>> Adding Corey in cc: . I guess I should have done that in the first place.
>> Yes, probably so.  I've been travelling and didn't see it on the mailing
>> lists until now.
>>
>> There is already a BT driver in the kernel, in drivers/char/ipmi, why
>> won't that work?
> The new driver is the host side (running on the BMC), the existing one
> is the client (running on the PC).
>
> 	Arnd

Ok, that's not really clear from the documentation or the Kconfig.
In the IPMI spec the "host" side is the computer side, not the BMC
side.  Like:

    11.6.1 BT Host Interface Registers
    The Host BT interface provides an independent set of registers and
    interrupts to allow the Host driver to
    communicate with the baseboard management controller without
    conflicting with the O/S ACPI driver.

In light of that, this should probably be named the bt-bmc driver.

I haven't reviewed this in detail, but I'm ok with putting it in
drivers/char/ipmi.  The state machine part looks reasonably
generic.  The configuration part isn't, but that could be split
out later if necessary.

The biggest thing I don't like is the byte at a time interfaces
from userspace.  That seems fairly inefficient if the system
does extra work for each userspace access.  IIRC some
systems do and some don't.

-corey

>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2016-09-12 20:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-31 17:24 [PATCH 0/3] ARM: aspeed: add support for the BT IPMI host device Cédric Le Goater
2016-08-31 17:24 ` [PATCH 1/3] misc: Add Aspeed BT IPMI host driver Cédric Le Goater
2016-08-31 19:57   ` Arnd Bergmann
2016-09-02 13:22     ` Cédric Le Goater
2016-09-12 18:55       ` Corey Minyard
2016-09-12 19:15         ` Arnd Bergmann
2016-09-12 20:33           ` Corey Minyard [this message]
2016-09-12 21:23             ` Cédric Le Goater
2016-09-12 22:06               ` Corey Minyard
2016-09-15  6:51             ` Cédric Le Goater
2016-09-15 12:23               ` Corey Minyard
2016-08-31 17:24 ` [PATCH 2/3] ARM: aspeed: Add defconfigs for CONFIG_ASPEED_BT_IPMI_HOST Cédric Le Goater
2016-08-31 17:24 ` [PATCH 3/3] ARM: dts: aspeed: Enable BT IPMI host device Cédric Le Goater

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=7db5ada0-49ea-55eb-089e-d979941ceff5@gmail.com \
    --to=tcminyard@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).