All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vidya Sagar <vidyas@nvidia.com>
To: <robh@kernel.org>, <bhelgaas@google.com>
Cc: <devicetree@vger.kernel.org>, <treding@nvidia.com>,
	<jonathanh@nvidia.com>, <kthota@nvidia.com>,
	<mmaddireddy@nvidia.com>, <vidyas@nvidia.com>,
	<sagar.tv@gmail.com>
Subject: [DT-SCHEMA PATCH V1] schemas: pci: Extend the meaning of 'linux,pci-probe-only'
Date: Thu, 22 Feb 2024 18:12:31 +0530	[thread overview]
Message-ID: <20240222124231.2685261-1-vidyas@nvidia.com> (raw)

Extend the meaning of 'linux,pci-probe-only' to cover the cases where
it is applicable only to a specific PCIe host bridge if defined in a
PCIe node instead of chosen node. Add the documentation for the same
in schemas/pci/pci-host-bridge.yaml

Signed-off-by: Vidya Sagar <vidyas@nvidia.com>
---
 dtschema/schemas/chosen.yaml              | 2 ++
 dtschema/schemas/pci/pci-host-bridge.yaml | 8 ++++++++
 2 files changed, 10 insertions(+)

diff --git a/dtschema/schemas/chosen.yaml b/dtschema/schemas/chosen.yaml
index 6d5c3f1..9152df3 100644
--- a/dtschema/schemas/chosen.yaml
+++ b/dtschema/schemas/chosen.yaml
@@ -144,6 +144,8 @@ properties:
       Optional property which takes a single-cell argument. If '0', then Linux
       will assign devices in its usual manner, otherwise it will not try to
       assign devices and instead use them as they are configured already.
+      NOTE:- To restrict the applicability of this property to a specific PCIe
+             host bridge, please refer to /schemas/pci/pci-host-bridge.yaml
 
   stdout-path:
     $ref: types.yaml#/definitions/string
diff --git a/dtschema/schemas/pci/pci-host-bridge.yaml b/dtschema/schemas/pci/pci-host-bridge.yaml
index fbbb829..d6d595d 100644
--- a/dtschema/schemas/pci/pci-host-bridge.yaml
+++ b/dtschema/schemas/pci/pci-host-bridge.yaml
@@ -31,6 +31,14 @@ properties:
       number for each host bridge in the system must be unique.
     $ref: /schemas/types.yaml#/definitions/uint32
 
+  linux,pci-probe-only:
+    description: If present, Linux will not try to assign devices and instead
+      use them as they are configured already by the platform firmware for this
+      particular host bridge.
+      NOTE:- If defined in chosen node, this property has system wide applicability.
+             Please refer to /schemas/chosen.yaml for more info.
+    type: boolean
+
   msi-map:
     $ref: /schemas/types.yaml#/definitions/uint32-matrix
     items:
-- 
2.25.1


             reply	other threads:[~2024-02-22 12:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22 12:42 Vidya Sagar [this message]
2024-02-22 16:02 ` [DT-SCHEMA PATCH V1] schemas: pci: Extend the meaning of 'linux,pci-probe-only' Bjorn Helgaas

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=20240222124231.2685261-1-vidyas@nvidia.com \
    --to=vidyas@nvidia.com \
    --cc=bhelgaas@google.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jonathanh@nvidia.com \
    --cc=kthota@nvidia.com \
    --cc=mmaddireddy@nvidia.com \
    --cc=robh@kernel.org \
    --cc=sagar.tv@gmail.com \
    --cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.