From: sven.auhagen@voleatech.de
To: linux-arm-kernel@lists.infradead.org
Cc: baruch@tkos.co.il, antoine.tenart@bootlin.com,
maxime.chevallier@bootlin.com, nadavh@marvell.com,
thomas.petazzoni@bootlin.com, miquel.raynal@bootlin.com
Subject: [PATCH 5/7] dt-bindings: ata: Update ahci bindings with possible per-port interrupts
Date: Tue, 7 Jul 2020 17:21:12 +0200 [thread overview]
Message-ID: <20200707152114.53890-6-sven.auhagen@voleatech.de> (raw)
In-Reply-To: <20200707152114.53890-1-sven.auhagen@voleatech.de>
From: Miquel Raynal <miquel.raynal@bootlin.com>
Update bindings to reflect the fact that a SATA IP can either have:
- only one interrupt: in this case an 'interrupts' property is
declared at the root of the node;
or
- each SATA port can have their own interrupt: in this case there is
one 'interrupts' property per port/sub-node and none at the root.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Reviewed-by: Rob Herring <robh@kernel.org>
---
Documentation/devicetree/bindings/ata/ahci-platform.txt | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindings/ata/ahci-platform.txt b/Documentation/devicetree/bindings/ata/ahci-platform.txt
index 77091a277642..83d715cbcecd 100644
--- a/Documentation/devicetree/bindings/ata/ahci-platform.txt
+++ b/Documentation/devicetree/bindings/ata/ahci-platform.txt
@@ -49,6 +49,12 @@ And at least one of the following properties:
- phys : reference to the SATA PHY node
- target-supply : regulator for SATA target power
+Sub-nodes optional properties:
+- interrupts : <interrupt mapping for SATA ports IRQ>, please
+ note that either the root SATA node has the
+ interrupts property, or there is one per SATA
+ port, but not both at the same time.
+
Examples:
sata@ffe08000 {
compatible = "snps,spear-ahci";
--
2.24.3 (Apple Git-128)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-07-07 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 15:21 [PATCH 0/7] Armada8k enable per-port SATA interrupts and drop a hack in the IRQ subsystem sven.auhagen
2020-07-07 15:21 ` [PATCH 1/7] ata: ahci: mvebu: Rename a platform data flag sven.auhagen
2020-07-07 15:21 ` [PATCH 2/7] ata: ahci: mvebu: Support A8k compatible sven.auhagen
2020-07-07 15:21 ` [PATCH 3/7] ata: ahci: mvebu: Add support for A8k legacy DT bindings sven.auhagen
2020-07-07 15:21 ` [PATCH 4/7] irqchip/irq-mvebu-icu: Remove the double SATA ports interrupt hack sven.auhagen
2020-07-07 15:21 ` sven.auhagen [this message]
2020-07-07 15:21 ` [PATCH 6/7] dt-bindings: ata: Update ahci_mvebu bindings sven.auhagen
2020-07-07 15:21 ` [PATCH 7/7] arm64: dts: marvell: armada-cp110: Switch to per-port SATA interrupts sven.auhagen
2020-07-18 21:15 ` [PATCH 0/7] Armada8k enable per-port SATA interrupts and drop a hack in the IRQ subsystem Gregory CLEMENT
2020-07-19 6:14 ` Sven Auhagen
2020-10-07 15:45 sven.auhagen
2020-10-07 15:45 ` [PATCH 5/7] dt-bindings: ata: Update ahci bindings with possible per-port interrupts sven.auhagen
2020-10-27 14:25 ` Hans de Goede
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=20200707152114.53890-6-sven.auhagen@voleatech.de \
--to=sven.auhagen@voleatech.de \
--cc=antoine.tenart@bootlin.com \
--cc=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maxime.chevallier@bootlin.com \
--cc=miquel.raynal@bootlin.com \
--cc=nadavh@marvell.com \
--cc=thomas.petazzoni@bootlin.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).