From: Corey Minyard <minyard@acm.org>
To: Chia-Wei Wang <chiawei_wang@aspeedtech.com>
Cc: joel@jms.id.au, andrew@aj.id.au,
openipmi-developer@lists.sourceforge.net,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org
Subject: Re: [PATCH] ipmi: kcs: aspeed: Update port address comments
Date: Thu, 22 Sep 2022 13:57:39 -0500 [thread overview]
Message-ID: <YyywI8265vECnEHv@minyard.net> (raw)
In-Reply-To: <20220920020333.601-1-chiawei_wang@aspeedtech.com>
On Tue, Sep 20, 2022 at 10:03:33AM +0800, Chia-Wei Wang wrote:
> Remove AST_usrGuide_KCS.pdf as it is no longer maintained.
Even if it's no longer maintained, is it useful? It seems better to
leave in useful documentation unless it has been replaced with something
else.
-corey
>
> Add more descriptions as the driver now supports the I/O
> address configurations for both the KCS Data and Cmd/Status
> interface registers.
>
> Signed-off-by: Chia-Wei Wang <chiawei_wang@aspeedtech.com>
> ---
> drivers/char/ipmi/kcs_bmc_aspeed.c | 29 ++++++++++++++++++-----------
> 1 file changed, 18 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/char/ipmi/kcs_bmc_aspeed.c b/drivers/char/ipmi/kcs_bmc_aspeed.c
> index cdc88cde1e9a..19c32bf50e0e 100644
> --- a/drivers/char/ipmi/kcs_bmc_aspeed.c
> +++ b/drivers/char/ipmi/kcs_bmc_aspeed.c
> @@ -207,17 +207,24 @@ static void aspeed_kcs_updateb(struct kcs_bmc_device *kcs_bmc, u32 reg, u8 mask,
> }
>
> /*
> - * AST_usrGuide_KCS.pdf
> - * 2. Background:
> - * we note D for Data, and C for Cmd/Status, default rules are
> - * A. KCS1 / KCS2 ( D / C:X / X+4 )
> - * D / C : CA0h / CA4h
> - * D / C : CA8h / CACh
> - * B. KCS3 ( D / C:XX2h / XX3h )
> - * D / C : CA2h / CA3h
> - * D / C : CB2h / CB3h
> - * C. KCS4
> - * D / C : CA4h / CA5h
> + * We note D for Data, and C for Cmd/Status, default rules are
> + *
> + * 1. Only the D address is given:
> + * A. KCS1/KCS2 (D/C: X/X+4)
> + * D/C: CA0h/CA4h
> + * D/C: CA8h/CACh
> + * B. KCS3 (D/C: XX2/XX3h)
> + * D/C: CA2h/CA3h
> + * C. KCS4 (D/C: X/X+1)
> + * D/C: CA4h/CA5h
> + *
> + * 2. Both the D/C addresses are given:
> + * A. KCS1/KCS2/KCS4 (D/C: X/Y)
> + * D/C: CA0h/CA1h
> + * D/C: CA8h/CA9h
> + * D/C: CA4h/CA5h
> + * B. KCS3 (D/C: XX2/XX3h)
> + * D/C: CA2h/CA3h
> */
> static int aspeed_kcs_set_address(struct kcs_bmc_device *kcs_bmc, u32 addrs[2], int nr_addrs)
> {
> --
> 2.25.1
>
next prev parent reply other threads:[~2022-09-22 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 2:03 [PATCH] ipmi: kcs: aspeed: Update port address comments Chia-Wei Wang
2022-09-22 18:57 ` Corey Minyard [this message]
2022-09-23 0:08 ` ChiaWei Wang
2022-09-23 0:20 ` Corey Minyard
2022-09-23 0:38 ` ChiaWei Wang
2022-09-23 0:46 ` Corey Minyard
2022-09-23 1:12 ` ChiaWei Wang
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=YyywI8265vECnEHv@minyard.net \
--to=minyard@acm.org \
--cc=andrew@aj.id.au \
--cc=chiawei_wang@aspeedtech.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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