From: Jeremy Linton <jeremy.linton@arm.com>
To: linux-pci@vger.kernel.org
Cc: will@kernel.org, bhelgaas@google.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, lpieralisi@kernel.org,
kw@linux.com, mark.rutland@arm.com, sudeep.holla@arm.com,
boqun.feng@gmail.com, catalin.marinas@arm.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jeremy Linton <jeremy.linton@arm.com>
Subject: [PATCH 4/4] dt-bindings: PCI: Note the use of pci-host-smc-generic
Date: Mon, 25 Jul 2022 11:39:05 -0500 [thread overview]
Message-ID: <20220725163905.2024437-5-jeremy.linton@arm.com> (raw)
In-Reply-To: <20220725163905.2024437-1-jeremy.linton@arm.com>
Note the addition of pci-host-smc-generic for
firmware based config assistance, and the relaxation
of the 'reg' property for such machines.
Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
---
.../bindings/pci/host-generic-pci.yaml | 24 ++++++++++++++-----
1 file changed, 18 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/pci/host-generic-pci.yaml b/Documentation/devicetree/bindings/pci/host-generic-pci.yaml
index 6bcaa8f2c3cf..b4471617fa46 100644
--- a/Documentation/devicetree/bindings/pci/host-generic-pci.yaml
+++ b/Documentation/devicetree/bindings/pci/host-generic-pci.yaml
@@ -18,10 +18,11 @@ description: |
presenting a set of fixed windows describing a subset of IO, Memory and
Configuration Spaces.
- Configuration Space is assumed to be memory-mapped (as opposed to being
- accessed via an ioport) and laid out with a direct correspondence to the
- geography of a PCI bus address by concatenating the various components to
- form an offset.
+ Configuration Space is assumed to be laid out with a direct correspondence
+ to the geography of a PCI bus address by concatenating the various components
+ to form an offset. The CAM and ECAM mechanisms require a memory mapped
+ interface, while the SMC traps to the firmware to perform config space
+ reads and writes decoded similarly to the ECAM mapping.
For CAM, this 24-bit offset is:
@@ -86,6 +87,7 @@ properties:
enum:
- pci-host-cam-generic
- pci-host-ecam-generic
+ - pci-host-smc-generic
reg:
description:
@@ -93,7 +95,8 @@ properties:
bus. The base address corresponds to the first bus in the "bus-range"
property. If no "bus-range" is specified, this will be bus 0 (the
default). Some host controllers have a 2nd non-compliant address range,
- so 2 entries are allowed.
+ so 2 entries are allowed. Machines which implement the Arm PCI SMCCC spec
+ must not provide this property.
minItems: 1
maxItems: 2
@@ -109,7 +112,6 @@ properties:
required:
- compatible
- - reg
- ranges
allOf:
@@ -123,6 +125,16 @@ allOf:
required:
- dma-coherent
+ - if:
+ properties:
+ compatible:
+ not:
+ contains:
+ const: pci-host-smc-generic
+ then:
+ required:
+ - reg
+
- if:
properties:
compatible:
--
2.37.1
next prev parent reply other threads:[~2022-07-25 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 16:39 [PATCH 0/4] PCI SMC conduit, now with DT support Jeremy Linton
2022-07-25 16:39 ` [PATCH 1/4] arm64: smccc: Add PCI SMCCCs Jeremy Linton
2022-07-25 16:39 ` [PATCH 2/4] arm64: PCI: Enable SMC conduit Jeremy Linton
2022-07-25 16:39 ` [PATCH 3/4] PCI: host-generic: Add firmware managed config ops Jeremy Linton
2022-07-25 16:39 ` Jeremy Linton [this message]
2022-07-26 11:40 ` [PATCH 0/4] PCI SMC conduit, now with DT support Will Deacon
2022-07-28 17:20 ` Jeremy Linton
2022-08-16 7:59 ` Catalin Marinas
2022-08-18 21:55 ` Pali Rohár
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=20220725163905.2024437-5-jeremy.linton@arm.com \
--to=jeremy.linton@arm.com \
--cc=bhelgaas@google.com \
--cc=boqun.feng@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kw@linux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=will@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).