From: Joel Stanley <joel@jms.id.au>
To: Konstantin Aladyshev <aladyshev22@gmail.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: [PATCH linux dev-5.8] ARM: dts: aspeed: amd-ethanolx: Update KCS nodes to use v2 binding
Date: Wed, 7 Oct 2020 06:36:52 +0000 [thread overview]
Message-ID: <CACPK8XfZ3ZymkF-QM9b5NTqgHuoRc67g1fTXE8_vudCRcvp_GQ@mail.gmail.com> (raw)
In-Reply-To: <20200930075153.2115-1-aladyshev22@gmail.com>
On Wed, 30 Sep 2020 at 07:52, Konstantin Aladyshev
<aladyshev22@gmail.com> wrote:
>
> KCS nodes compatible property in the 'aspeed-g5.dtsi' file was
> changed to use v2 binding in the commit fa4c8ec6feaa
> (ARM: dts: aspeed: Change KCS nodes to v2 binding).
> For the proper initialization of /dev/ipmi-kcs* devices
> KCS node variables also need to be changed to use v2 binding.
>
> Signed-off-by: Konstantin Aladyshev <aladyshev22@gmail.com>
Applied to dev-5.8.
Cheers,
Joel
> ---
> arch/arm/boot/dts/aspeed-bmc-amd-ethanolx.dts | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/arm/boot/dts/aspeed-bmc-amd-ethanolx.dts b/arch/arm/boot/dts/aspeed-bmc-amd-ethanolx.dts
> index 60ba86f3e5bc..89ddc3847222 100644
> --- a/arch/arm/boot/dts/aspeed-bmc-amd-ethanolx.dts
> +++ b/arch/arm/boot/dts/aspeed-bmc-amd-ethanolx.dts
> @@ -139,17 +139,17 @@ lm75a@4f {
>
> &kcs1 {
> status = "okay";
> - kcs_addr = <0x60>;
> + aspeed,lpc-io-reg = <0x60>;
> };
>
> &kcs2 {
> status = "okay";
> - kcs_addr = <0x62>;
> + aspeed,lpc-io-reg = <0x62>;
> };
>
> &kcs4 {
> status = "okay";
> - kcs_addr = <0x97DE>;
> + aspeed,lpc-io-reg = <0x97DE>;
> };
>
> &lpc_snoop {
> --
> 2.25.1
>
prev parent reply other threads:[~2020-10-07 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 7:51 [PATCH linux dev-5.8] ARM: dts: aspeed: amd-ethanolx: Update KCS nodes to use v2 binding Konstantin Aladyshev
2020-10-07 6:36 ` Joel Stanley [this message]
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=CACPK8XfZ3ZymkF-QM9b5NTqgHuoRc67g1fTXE8_vudCRcvp_GQ@mail.gmail.com \
--to=joel@jms.id.au \
--cc=aladyshev22@gmail.com \
--cc=openbmc@lists.ozlabs.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).