From: Vidya Sagar <vidyas@nvidia.com>
To: <bhelgaas@google.com>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <lpieralisi@kernel.org>,
<kw@linux.com>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <mani@kernel.org>,
<Sergey.Semin@baikalelectronics.ru>, <jszhang@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<kthota@nvidia.com>, <mmaddireddy@nvidia.com>,
<vidyas@nvidia.com>, <sagar.tv@gmail.com>
Subject: [PATCH V1 1/4] dt-bindings: Add "hotplug-gpios" PCIe property
Date: Sat, 1 Oct 2022 00:57:44 +0530 [thread overview]
Message-ID: <20220930192747.21471-2-vidyas@nvidia.com> (raw)
In-Reply-To: <20220930192747.21471-1-vidyas@nvidia.com>
Provide a way for the firmware to tell the OS about the GPIO that can be
used to get the Hot-Plug and Unplug events.
Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
---
Documentation/devicetree/bindings/pci/pci.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/pci/pci.txt b/Documentation/devicetree/bindings/pci/pci.txt
index 6a8f2874a24d..7b89bddc8dde 100644
--- a/Documentation/devicetree/bindings/pci/pci.txt
+++ b/Documentation/devicetree/bindings/pci/pci.txt
@@ -32,6 +32,10 @@ driver implementation may support the following properties:
root port to downstream device and host bridge drivers can do programming
which depends on CLKREQ signal existence. For example, programming root port
not to advertise ASPM L1 Sub-States support if there is no CLKREQ signal.
+- hotplug-gpios:
+ If present this property specifies the GPIO to be used for Hot-Plug/Unplug
+ functionality. It is used by the PCIe GPIO Hot-Plug core driver for
+ PCIe device Hot-Plug/Unplug events.
PCI-PCI Bridge properties
-------------------------
--
2.17.1
next prev parent reply other threads:[~2022-09-30 19:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 19:27 [PATCH V1 0/4] GPIO based PCIe Hot-Plug support Vidya Sagar
2022-09-30 19:27 ` Vidya Sagar [this message]
2022-10-01 15:56 ` [PATCH V1 1/4] dt-bindings: Add "hotplug-gpios" PCIe property Lukas Wunner
2022-10-01 16:10 ` Pali Rohár
2022-09-30 19:27 ` [PATCH V1 2/4] PCI/hotplug: Add GPIO PCIe hotplug driver Vidya Sagar
2022-09-30 19:27 ` [PATCH V1 3/4] PCI: tegra194: Add support to configure a pluggable slot Vidya Sagar
2022-09-30 19:27 ` [PATCH V1 4/4] PCI: tegra194: Enable GPIO based Hot-Plug support Vidya Sagar
2022-10-01 16:00 ` [PATCH V1 0/4] GPIO based PCIe " Lukas Wunner
2022-10-01 16:20 ` Pali Rohár
2022-10-01 23:50 ` Jonathan Derrick
2022-10-03 18:09 ` Bjorn Helgaas
2022-10-03 18:21 ` Pali Rohár
2022-10-03 19:18 ` Jonathan Derrick
2022-10-04 4:04 ` Vidya Sagar
2022-10-10 6:14 ` Vidya Sagar
2022-10-17 2:46 ` Vidya Sagar
2022-11-09 15:35 ` Manivannan Sadhasivam
2022-10-03 17:04 ` Rob Herring
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=20220930192747.21471-2-vidyas@nvidia.com \
--to=vidyas@nvidia.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kthota@nvidia.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=mmaddireddy@nvidia.com \
--cc=robh+dt@kernel.org \
--cc=sagar.tv@gmail.com \
--cc=thierry.reding@gmail.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).