linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Wang, Haiyue" <haiyue.wang@linux.intel.com>
To: joel@jms.id.au, andrew@aj.id.au
Cc: linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH dts/arm/aspeed-g5 v1] ARM: dts: aspeed-g5: Add IPMI KCS node
Date: Fri, 16 Mar 2018 08:47:51 +0800	[thread overview]
Message-ID: <9231baaf-e77c-c517-bca2-083070a53342@linux.intel.com> (raw)
In-Reply-To: <1520399090-2455-1-git-send-email-haiyue.wang@linux.intel.com>

Hi Joel and Andrew,

Have time to review this patch ? Hope for your comments. :-)

BR,
Haiyue

On 2018-03-07 13:04, Haiyue Wang wrote:
> The IPMI KCS device part of the LPC interface and is used for
> communication with the host processor.
>
> Signed-off-by: Haiyue Wang <haiyue.wang@linux.intel.com>
> ---
>   arch/arm/boot/dts/aspeed-g5.dtsi | 43 +++++++++++++++++++++++++++++++++++++++-
>   1 file changed, 42 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
> index 8eac57c..f443169 100644
> --- a/arch/arm/boot/dts/aspeed-g5.dtsi
> +++ b/arch/arm/boot/dts/aspeed-g5.dtsi
> @@ -267,8 +267,40 @@
>   				ranges = <0x0 0x1e789000 0x1000>;
>   
>   				lpc_bmc: lpc-bmc@0 {
> -					compatible = "aspeed,ast2500-lpc-bmc";
> +					compatible = "aspeed,ast2500-lpc-bmc", "simple-mfd", "syscon";
>   					reg = <0x0 0x80>;
> +					reg-io-width = <4>;
> +
> +					#address-cells = <1>;
> +					#size-cells = <1>;
> +					ranges = <0x0 0x0 0x80>;
> +
> +					kcs1: kcs1@0 {
> +						compatible = "aspeed,ast2500-kcs-bmc";
> +						reg = <0x0 0x80>;
> +						interrupts = <8>;
> +						kcs_chan = <1>;
> +						kcs_addr = <0x0>;
> +						status = "disabled";
> +					};
> +
> +					kcs2: kcs2@0 {
> +						compatible = "aspeed,ast2500-kcs-bmc";
> +						reg = <0x0 0x80>;
> +						interrupts = <8>;
> +						kcs_chan = <2>;
> +						kcs_addr = <0x0>;
> +						status = "disabled";
> +					};
> +
> +					kcs3: kcs3@0 {
> +						compatible = "aspeed,ast2500-kcs-bmc";
> +						reg = <0x0 0x80>;
> +						interrupts = <8>;
> +						kcs_chan = <3>;
> +						kcs_addr = <0x0>;
> +						status = "disabled";
> +					};
>   				};
>   
>   				lpc_host: lpc-host@80 {
> @@ -294,6 +326,15 @@
>   						status = "disabled";
>   					};
>   
> +					kcs4: kcs4@0 {
> +						compatible = "aspeed,ast2500-kcs-bmc";
> +						reg = <0x0 0xa0>;
> +						interrupts = <8>;
> +						kcs_chan = <4>;
> +						kcs_addr = <0x0>;
> +						status = "disabled";
> +					};
> +
>   					lhc: lhc@20 {
>   						compatible = "aspeed,ast2500-lhc";
>   						reg = <0x20 0x24 0x48 0x8>;

  reply	other threads:[~2018-03-16  0:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-07  5:04 [PATCH dts/arm/aspeed-g5 v1] ARM: dts: aspeed-g5: Add IPMI KCS node Haiyue Wang
2018-03-16  0:47 ` Wang, Haiyue [this message]
2018-05-25  4:34   ` Joel Stanley
2018-05-25 11:33     ` Wang, Haiyue
  -- strict thread matches above, loose matches on Subject: below --
2018-03-04  5:03 Haiyue Wang
2018-03-07  3:56 ` Joel Stanley
2018-03-07  4:41   ` Wang, Haiyue

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=9231baaf-e77c-c517-bca2-083070a53342@linux.intel.com \
    --to=haiyue.wang@linux.intel.com \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.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).