All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyril Bur <cyrilbur@gmail.com>
To: joel@jms.id.au
Cc: openbmc@lists.ozlabs.org, andrew@aj.id.au
Subject: [PATCH v2 1/3] ARM: dts: aspeed-g5: Add mailbox and LPC control node
Date: Mon, 16 Jan 2017 16:37:38 +1100	[thread overview]
Message-ID: <20170116053740.15299-1-cyrilbur@gmail.com> (raw)

Both these devices exist on the LPC bus these nodes are children of a
new LPC bus node.

Signed-off-by: Cyril Bur <cyrilbur@gmail.com>
---
v2:
	Add the core to to the dtsi
	Enable them in the platforms that want them in subsequent patches
	Remove the compatible property for the reserved-memory nodes
	  All my understanding seems to indicate that this is how it
	  should be. However i've had problems with drivers probing on
	  other systems, hopefully these problems will turn out to have
	  been unrelated.

 arch/arm/boot/dts/aspeed-g5.dtsi | 38 ++++++++++++++++++++++++++++++++++++++
 1 file changed, 38 insertions(+)

diff --git a/arch/arm/boot/dts/aspeed-g5.dtsi b/arch/arm/boot/dts/aspeed-g5.dtsi
index d6ff41ee6c58..1ce07d0ed431 100644
--- a/arch/arm/boot/dts/aspeed-g5.dtsi
+++ b/arch/arm/boot/dts/aspeed-g5.dtsi
@@ -89,6 +89,44 @@
 			};
 		};
 
+		lpc: lpc@1e789000 {
+			compatible = "aspeed,ast2500-lpc", "simple-mfd";
+			reg = <0x1e789000 0x1000>;
+
+			#address-cells = <1>;
+			#size-cells = <1>;
+			ranges = <0x0 0x1e789000 0x1000>;
+
+			lpc_bmc: lpc-bmc@0 {
+				compatible = "aspeed,ast2500-lpc-bmc";
+				reg = <0x0 0x80>;
+			};
+
+			lpc_host: lpc-host@80 {
+				compatible = "aspeed,ast2500-lpc-host", "simple-mfd", "syscon";
+				reg = <0x80 0x1e0>;
+				reg-io-width = <4>;
+
+				#address-cells = <1>;
+				#size-cells = <1>;
+				ranges = <0x0 0x80 0x1e0>;
+
+				lpc_ctrl: lpc-ctrl@0 {
+					compatible = "aspeed,ast2500-lpc-ctrl";
+					reg = <0x0 0x80>;
+					status = "disabled"
+				};
+
+				mbox: mbox@180 {
+					compatible = "aspeed,ast2500-mbox";
+					reg = <0x180 0x5c>;
+					interrupts = <46>;
+					#mbox-cells = <1>;
+					status = "disabled"
+				};
+			};
+		};
+
 		vic: interrupt-controller@1e6c0080 {
 			compatible = "aspeed,ast2400-vic";
 			interrupt-controller;
-- 
2.11.0

             reply	other threads:[~2017-01-16  5:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16  5:37 Cyril Bur [this message]
2017-01-16  5:37 ` [PATCH v2 2/3] ARM: dts: aspeed-bmc-opp-zaius: Enable mailbox and LPC control nodes Cyril Bur
2017-01-16  5:59   ` Joel Stanley
2017-01-16  5:37 ` [PATCH v2 3/3] ARM: dts: aspeed-bmc-opp-witherspoon: " Cyril Bur
2017-01-16  5:59   ` Joel Stanley
2017-01-16  5:58 ` [PATCH v2 1/3] ARM: dts: aspeed-g5: Add mailbox and LPC control node Joel Stanley
2017-01-16  6:03   ` Joel Stanley

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=20170116053740.15299-1-cyrilbur@gmail.com \
    --to=cyrilbur@gmail.com \
    --cc=andrew@aj.id.au \
    --cc=joel@jms.id.au \
    --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 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.