From: Eddie James <eajames@linux.ibm.com>
To: linux-aspeed@lists.ozlabs.org
Cc: joel@jms.id.au, andrew@codeconstruct.com.au,
devicetree@vger.kernel.org, linux-fsi@lists.ozlabs.org,
robh@kernel.org, conor+dt@kernel.org, krzk+dt@kernel.org,
jk@ozlabs.org, alistair@popple.id.au, eajames@linux.ibm.com,
lakshmiy@us.ibm.com
Subject: [PATCH 1/3] dt-bindings: fsi: Document the IBM SBEFIFO engine
Date: Fri, 12 Apr 2024 09:43:56 -0500 [thread overview]
Message-ID: <20240412144358.204129-2-eajames@linux.ibm.com> (raw)
In-Reply-To: <20240412144358.204129-1-eajames@linux.ibm.com>
The SBEFIFO engine provides an interface to the POWER processor
Self Boto Engine (SBE).
Signed-off-by: Eddie James <eajames@linux.ibm.com>
---
.../devicetree/bindings/fsi/ibm,sbefifo.yaml | 39 +++++++++++++++++++
1 file changed, 39 insertions(+)
create mode 100644 Documentation/devicetree/bindings/fsi/ibm,sbefifo.yaml
diff --git a/Documentation/devicetree/bindings/fsi/ibm,sbefifo.yaml b/Documentation/devicetree/bindings/fsi/ibm,sbefifo.yaml
new file mode 100644
index 000000000000..d70012e42d79
--- /dev/null
+++ b/Documentation/devicetree/bindings/fsi/ibm,sbefifo.yaml
@@ -0,0 +1,39 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/fsi/ibm,sbefifo.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: IBM FSI-attached SBEFIFO engine
+
+maintainers:
+ - Eddie James <eajames@linux.ibm.com>
+
+description: |
+ This binding describes an FSI CFAM engine called the SBEFIFO. Therefore this
+ node will always be a child of an FSI CFAM node; see fsi.txt for details on
+ FSI slave and CFAM nodes. This SBEFIFO engine provides an interface to the
+ POWER processor Self Boot Engine (SBE).
+
+properties:
+ compatible:
+ enum:
+ - ibm,p9-sbefifo
+ - ibm,ody-sbefifo
+
+ reg:
+ items:
+ - description: FSI slave address
+
+required:
+ - compatible
+ - reg
+
+additionalProperties: false
+
+examples:
+ - |
+ sbefifo@2400 {
+ compatible = "ibm,p9-sbefifo";
+ reg = <0x2400 0x400>;
+ };
--
2.39.3
next prev parent reply other threads:[~2024-04-12 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 14:43 [PATCH 0/3] fsi: sbefifo: Prevent async FFDC collection for Odyssey SBEFIFOs Eddie James
2024-04-12 14:43 ` Eddie James [this message]
2024-04-13 7:47 ` [PATCH 1/3] dt-bindings: fsi: Document the IBM SBEFIFO engine Krzysztof Kozlowski
2024-04-15 0:50 ` Andrew Jeffery
2024-04-15 15:03 ` Eddie James
2024-04-12 14:43 ` [PATCH 2/3] fsi: sbefifo: Prevent async FFDC collection for Odyssey SBEFIFOs Eddie James
2024-04-12 14:43 ` [PATCH 3/3] ARM: dts: aspeed: Update Odyssey SBEFIFO compatible strings Eddie James
2024-04-15 0:54 ` Andrew Jeffery
2024-04-15 14:59 ` Eddie James
2024-04-16 0:06 ` Andrew Jeffery
2024-04-16 14:48 ` Eddie James
2024-04-17 7:02 ` Andrew Jeffery
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=20240412144358.204129-2-eajames@linux.ibm.com \
--to=eajames@linux.ibm.com \
--cc=alistair@popple.id.au \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jk@ozlabs.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=lakshmiy@us.ibm.com \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-fsi@lists.ozlabs.org \
--cc=robh@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).