From: Michal Simek <michal.simek@amd.com>
To: <linux-kernel@vger.kernel.org>, <monstr@monstr.eu>,
<michal.simek@xilinx.com>, <git@xilinx.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>,
<devicetree@vger.kernel.org>, <linux-spi@vger.kernel.org>
Subject: [PATCH 2/2] dt-bindings: spi: spi-cadence: Add label property
Date: Thu, 3 Aug 2023 09:24:25 +0200 [thread overview]
Message-ID: <82cd1a57397867b5a1039cd15244344c02a3ece1.1691047461.git.michal.simek@amd.com> (raw)
In-Reply-To: <987430ee905fd299fe962663d94f848b341c87df.1691047461.git.michal.simek@amd.com>
Add a label property to allow a custom name to be used for identifying the
controller on a board. This is useful when there is more than one
controller present. Similar change was done by commit 412b7a521c30
("dt-bindings: eeprom: at24: Add label property for AT24").
Signed-off-by: Michal Simek <michal.simek@amd.com>
---
Documentation/devicetree/bindings/spi/spi-cadence.yaml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/spi/spi-cadence.yaml b/Documentation/devicetree/bindings/spi/spi-cadence.yaml
index 9eda7f0d2869..d4b61b0e8301 100644
--- a/Documentation/devicetree/bindings/spi/spi-cadence.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-cadence.yaml
@@ -52,6 +52,9 @@ properties:
power-domains:
maxItems: 1
+ label:
+ description: Descriptive name of the SPI controller.
+
required:
- compatible
- reg
--
2.36.1
next prev parent reply other threads:[~2023-08-03 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 7:24 [PATCH 1/2] dt-bindings: spi: spi-cadence: Describe power-domains property Michal Simek
2023-08-03 7:24 ` Michal Simek [this message]
2023-08-03 15:43 ` Conor Dooley
2023-08-03 18:26 ` Mark Brown
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=82cd1a57397867b5a1039cd15244344c02a3ece1.1691047461.git.michal.simek@amd.com \
--to=michal.simek@amd.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=git@xilinx.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=robh+dt@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).