From: Randy Dunlap <rdunlap@infradead.org>
To: minyard@acm.org, openipmi-developer@lists.sourceforge.net
Cc: Andrew Manley <andrew.manley@sealingtech.com>,
linux-kernel@vger.kernel.org, Corey Minyard <cminyard@mvista.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 3/5] ipmi:ipmb: Add initial support for IPMI over IPMB
Date: Mon, 4 Oct 2021 18:27:34 -0700 [thread overview]
Message-ID: <1d2c2c50-8f79-03ec-5c5c-e1cd8ce07b3d@infradead.org> (raw)
In-Reply-To: <20211005004019.2670691-4-minyard@acm.org>
Hi,
On 10/4/21 5:40 PM, minyard@acm.org wrote:
> From: Corey Minyard <cminyard@mvista.com>
>
> This provides access to the management controllers on an IPMB bus to a
> device sitting on the IPMB bus. It also provides slave capability to
> respond to received messages on the bus.
>
> Signed-off-by: Corey Minyard <minyard@acm.org>
> Tested-by: Andrew Manley <andrew.manley@sealingtech.com>
> Reviewed-by: Andrew Manley <andrew.manley@sealingtech.com>
> ---
> drivers/char/ipmi/Kconfig | 9 +
> drivers/char/ipmi/Makefile | 1 +
> drivers/char/ipmi/ipmi_ipmb.c | 510 ++++++++++++++++++++++++++++++++++
> 3 files changed, 520 insertions(+)
> create mode 100644 drivers/char/ipmi/ipmi_ipmb.c
>
> diff --git a/drivers/char/ipmi/Kconfig b/drivers/char/ipmi/Kconfig
> index 249b31197eea..1c92209f023b 100644
> --- a/drivers/char/ipmi/Kconfig
> +++ b/drivers/char/ipmi/Kconfig
> @@ -75,6 +75,15 @@ config IPMI_SSIF
> have a driver that must be accessed over an I2C bus instead of a
> standard interface. This module requires I2C support.
>
> +config IPMI_IPMB
> + tristate 'IPMI IPMB interface'
> + select I2C
How can this select I2C unconditionally? At this point we don't
even know if this platform has/supports I2C.
Ditto for IPMI_SSIF in the current Kconfig file, while
IPMB_DEVICE_INTERFACE depends on I2C (as it should IMO).
> + help
> + Provides a driver for a system running right on the IPMB bus.
> + It supports normal system interface messages to a BMC on the IPMB
> + bus, and it also supports direct messaging on the bus using
> + IPMB direct messages. This module requires I2C support.
<form-letter-bot>
Please follow coding-style for Kconfig files:
(from Documentation/process/coding-style.rst, section 10):
For all of the Kconfig* configuration files throughout the source tree,
the indentation is somewhat different. Lines under a ``config`` definition
are indented with one tab, while help text is indented an additional two
spaces.
> +
> config IPMI_POWERNV
> depends on PPC_POWERNV
> tristate 'POWERNV (OPAL firmware) IPMI interface'
> diff --git a/drivers/char/ipmi/ipmi_ipmb.c b/drivers/char/ipmi/ipmi_ipmb.c
> new file mode 100644
> index 000000000000..b10a1fd9c563
> --- /dev/null
> +++ b/drivers/char/ipmi/ipmi_ipmb.c
> @@ -0,0 +1,510 @@
> +// SPDX-License-Identifier: GPL-2.0
> +
> +/*
> + * Driver to talk to a remote management controller on IPMB.
> + */
> +
[...]
> +
> +static int ipmi_ipmb_start_processing(void *send_info,
Odd spacing/formatting above.
> + struct ipmi_smi *new_intf)
> +{
> + struct ipmi_ipmb_dev *iidev = send_info;
> +
> + iidev->intf = new_intf;
> + iidev->ready = true;
> + return 0;
> +}
> +
> +
> +static void ipmi_ipmb_sender(void *send_info,
Ditto.
> + struct ipmi_smi_msg *msg)
> +{
--
~Randy
next prev parent reply other threads:[~2021-10-05 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-05 0:40 [PATCH 0/5] Add support for access through an IPMB bus minyard
2021-10-05 0:40 ` [PATCH 1/5] ipmi: Export ipmb_checksum() minyard
2021-10-05 0:40 ` [PATCH 2/5] ipmi: Add support for IPMB direct messages minyard
2021-10-05 0:40 ` [PATCH 3/5] ipmi:ipmb: Add initial support for IPMI over IPMB minyard
2021-10-05 1:27 ` Randy Dunlap [this message]
2021-10-05 11:43 ` Corey Minyard
2021-10-05 0:40 ` [PATCH 4/5] ipmi: Add docs for IPMB direct addressing minyard
2021-10-05 0:40 ` [PATCH 5/5] ipmi: Add docs for the IPMI IPMB driver minyard
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=1d2c2c50-8f79-03ec-5c5c-e1cd8ce07b3d@infradead.org \
--to=rdunlap@infradead.org \
--cc=andrew.manley@sealingtech.com \
--cc=arnd@arndb.de \
--cc=cminyard@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=openipmi-developer@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®