From: "Cédric Le Goater" <clg@kaod.org>
To: Patrick Williams <patrick@stwcx.xyz>
Cc: Joel Stanley <joel@jms.id.au>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [RFC PATCH linux dev-4.7 4/6] misc: Add Aspeed BT IPMI BMC driver
Date: Thu, 15 Sep 2016 13:22:50 +0200 [thread overview]
Message-ID: <a376797d-bb53-678a-be60-3c7188f0d3cc@kaod.org> (raw)
In-Reply-To: <20160915105129.GC25351@heinlein.lan>
On 09/15/2016 12:51 PM, Patrick Williams wrote:
> On Thu, Sep 15, 2016 at 10:36:46AM +0200, Cédric Le Goater wrote:
>>>> I'm not sure there. When I open /dev/ttyUSB0 I'm talking to the USB0
>>>> serial device. When I open /dev/mtd0, I'm talking to the mtd0 device.
>>>> So when I open /dev/ipmi-bt-bmc, I would expect to talk to the BMC
>>>> device?
>>>
>>> Yes. I went a little too far in the global rename. /dev/ipmi-bt-bmc makes
>>
>> I meant /dev/ipmi-bt-host ! :)
>
> Does it make sense to have these numbered? I thought Brenden proposed
> an emulated bt-over-i2c. We could also conceive of an SOC that had
> multiple LPC (+bt) engines to facilitate multiple nodes, or an off-board
> FPGA to do it.
>
If we expect to have multiple btbridged process running, we will
need multiple device nodes. How we should name them depends partly
on the driver I think.
We could keep the prefix 'ipmi-bt' because it identifies the BT
interface described in the IPMI specs and use node /dev/ipmi-bt-host
for the original bt_bmc, (used be bt_host) driver. This one will be
unique.
The others could use :
/dev/ipmi-bt-lpc
/dev/ipmi-bt-i2c-<bus>
?
C.
next prev parent reply other threads:[~2016-09-15 11:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 6:32 [RFC PATCH linux dev-4.7 0/6] iBT interface changes Cédric Le Goater
2016-09-15 6:32 ` [RFC PATCH linux dev-4.7 1/6] Revert "misc: Add Aspeed BT IPMI host driver" Cédric Le Goater
2016-09-15 6:32 ` [RFC PATCH linux dev-4.7 2/6] ARM: aspeed: remove previous definitions in default config Cédric Le Goater
2016-09-15 6:32 ` [RFC PATCH linux dev-4.7 3/6] ARM: dts: aspeed: remove previous iBT definitions Cédric Le Goater
2016-09-15 6:32 ` [RFC PATCH linux dev-4.7 4/6] misc: Add Aspeed BT IPMI BMC driver Cédric Le Goater
2016-09-15 7:09 ` Joel Stanley
2016-09-15 7:37 ` Cédric Le Goater
2016-09-15 8:36 ` Cédric Le Goater
2016-09-15 10:03 ` Joel Stanley
2016-09-15 10:42 ` Cédric Le Goater
2016-09-15 10:51 ` Patrick Williams
2016-09-15 11:22 ` Cédric Le Goater [this message]
2016-09-15 11:33 ` Patrick Williams
2016-09-15 14:02 ` Cédric Le Goater
2016-09-15 6:32 ` [RFC PATCH linux dev-4.7 5/6] ARM: aspeed: Add defconfigs for CONFIG_ASPEED_BT_IPMI_BMC Cédric Le Goater
2016-09-15 6:32 ` [RFC PATCH linux dev-4.7 6/6] ARM: dts: aspeed: Enable BT IPMI BMC device Cédric Le Goater
2016-09-15 7:11 ` Joel Stanley
2016-09-15 7:55 ` Cédric Le Goater
2016-09-23 6:14 ` [RFC PATCH linux dev-4.7 0/6] iBT interface changes Joel Stanley
2016-09-23 13:22 ` 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=a376797d-bb53-678a-be60-3c7188f0d3cc@kaod.org \
--to=clg@kaod.org \
--cc=joel@jms.id.au \
--cc=openbmc@lists.ozlabs.org \
--cc=patrick@stwcx.xyz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.