From: Tomer Maimon <tmaimon77@gmail.com>
To: olof@lixom.net, gregkh@linuxfoundation.org, arnd@arndb.de,
robh+dt@kernel.org, mark.rutland@arm.com, avifishman70@gmail.com,
venture@google.com, yuenn@google.com, benjaminfair@google.com,
joel@jms.id.au
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, Tomer Maimon <tmaimon77@gmail.com>
Subject: [PATCH v1 1/2] dt-binding: soc: Add common LPC snoop documentation
Date: Mon, 10 Jun 2019 16:32:44 +0300 [thread overview]
Message-ID: <20190610133245.306812-2-tmaimon77@gmail.com> (raw)
In-Reply-To: <20190610133245.306812-1-tmaimon77@gmail.com>
Added device tree binding documentation for Nuvoton BMC
NPCM BIOS Post Code (BPC) and Aspeed AST2500 LPC snoop.
The LPC snoop monitoring two configurable I/O addresses
written by the host on Low Pin Count (LPC) bus.
Signed-off-by: Tomer Maimon <tmaimon77@gmail.com>
Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
Reviewed-by: Rob Herring <robh@kernel.org>
---
.../devicetree/bindings/soc/lpc/lpc-snoop.txt | 27 +++++++++++++++++++
1 file changed, 27 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/lpc/lpc-snoop.txt
diff --git a/Documentation/devicetree/bindings/soc/lpc/lpc-snoop.txt b/Documentation/devicetree/bindings/soc/lpc/lpc-snoop.txt
new file mode 100644
index 000000000000..c21cb8df4ffb
--- /dev/null
+++ b/Documentation/devicetree/bindings/soc/lpc/lpc-snoop.txt
@@ -0,0 +1,27 @@
+LPC snoop interface
+
+The LPC snoop (BIOS Post Code) interface can monitor
+two configurable I/O addresses written by the host on
+the Low Pin Count (LPC) bus.
+
+Nuvoton NPCM7xx LPC snoop supports capture double words,
+when using capture double word only I/O address 1 is monitored.
+
+Required properties for lpc-snoop node
+- compatible : "nuvoton,npcm750-lpc-bpc-snoop" for Poleg NPCM7XX
+ "aspeed,ast2500-lpc-snoop" for Aspeed AST2500.
+- reg : specifies physical base address and size of the registers.
+- interrupts : contain the LPC snoop interrupt with flags for falling edge.
+- snoop-ports : contain monitor I/O addresses, at least one monitor I/O
+ address required
+
+Optional property for NPCM7xx lpc-snoop node
+- nuvoton,lpc-en-dwcapture : enable capture double words support.
+
+Example:
+ lpc-snoop: lpc_snoop@f0007040 {
+ compatible = "nuvoton,npcm750-lpc-bpc-snoop";
+ reg = <0xf0007040 0x14>;
+ snoop-ports = <0x80>;
+ interrupts = <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>;
+ };
--
2.18.0
next prev parent reply other threads:[~2019-06-10 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 13:32 [PATCH v1 0/2] soc: add NPCM LPC BPC driver support Tomer Maimon
2019-06-10 13:32 ` Tomer Maimon [this message]
2019-06-10 13:32 ` [PATCH v1 2/2] soc: nuvoton: add NPCM LPC BPC driver Tomer Maimon
2019-06-11 13:11 ` Arnd Bergmann
2019-06-13 9:26 ` Tomer Maimon
2019-06-13 11:49 ` Arnd Bergmann
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=20190610133245.306812-2-tmaimon77@gmail.com \
--to=tmaimon77@gmail.com \
--cc=arnd@arndb.de \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=joel@jms.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=olof@lixom.net \
--cc=openbmc@lists.ozlabs.org \
--cc=robh+dt@kernel.org \
--cc=venture@google.com \
--cc=yuenn@google.com \
/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).