| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20241217151040.GA1667241-robh@kernel.org>
Date: Tue, 17 Dec 2024 09:10:40 -0600
From: Rob Herring <robh@...nel.org>
To: Thippeswamy Havalige <thippeswamy.havalige@....com>
Cc: bhelgaas@...gle.com, lpieralisi@...nel.org, kw@...ux.com,
manivannan.sadhasivam@...aro.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-pci@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
jingoohan1@...il.com, michal.simek@....com,
bharat.kumar.gogada@....com
Subject: Re: [RESEND PATCH v5 2/3] dt-bindings: PCI: amd-mdb: Add AMD Versal2
MDB PCIe Root Port Bridge
On Fri, Dec 13, 2024 at 12:10:34PM +0530, Thippeswamy Havalige wrote:
> Add AMD Versal2 MDB (Multimedia DMA Bridge) PCIe Root Port Bridge.
>
> Signed-off-by: Thippeswamy Havalige <thippeswamy.havalige@....com>
> ---
> Changes in v2:
> -------------
> - Modify patch subject.
> - Add pcie host bridge reference.
> - Modify filename as per compatible string.
> - Remove standard PCI properties.
> - Modify interrupt controller description.
> - Indentation
>
> Changes in v3:
> -------------
> - Modified SLCR to lower case.
> - Add dwc schemas.
> - Remove common properties.
> - Move additionalProperties below properties.
> - Remove ranges property from required properties.
> - Drop blank line.
> - Modify pci@ to pcie@
>
> Changes in v4:
> -------------
> - None.
>
> Changes in v5:
> -------------
> - None.
> ---
> .../bindings/pci/amd,versal2-mdb-host.yaml | 121 ++++++++++++++++++
> ---
> .../bindings/pci/amd,versal2-mdb-host.yaml | 121 ++++++++++++++++++
> 1 file changed, 121 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/pci/amd,versal2-mdb-host.yaml
>
> diff --git a/Documentation/devicetree/bindings/pci/amd,versal2-mdb-host.yaml b/Documentation/devicetree/bindings/pci/amd,versal2-mdb-host.yaml
> new file mode 100644
> index 000000000000..c319adeeee66
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pci/amd,versal2-mdb-host.yaml
> @@ -0,0 +1,121 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/pci/amd,versal2-mdb-host.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: AMD Versal2 MDB(Multimedia DMA Bridge) Host Controller
> +
> +maintainers:
> + - Thippeswamy Havalige <thippeswamy.havalige@....com>
> +
> +allOf:
> + - $ref: /schemas/pci/pci-host-bridge.yaml#
> + - $ref: /schemas/pci/snps,dw-pcie.yaml#
> +
> +properties:
> + compatible:
> + const: amd,versal2-mdb-host
> +
> + reg:
> + items:
> + - description: MDB PCIe controller 0 SLCR
> + - description: configuration region
> + - description: data bus interface
> + - description: address translation unit register
> +
> + reg-names:
> + items:
> + - const: mdb_pcie_slcr
> + - const: config
> + - const: dbi
> + - const: atu
> +
> + ranges:
> + maxItems: 2
> +
> + msi-map:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + interrupt-map-mask:
> + items:
> + - const: 0
> + - const: 0
> + - const: 0
> + - const: 7
> +
> + interrupt-map:
> + maxItems: 4
> +
> + "#interrupt-cells":
> + const: 1
> +
> + interrupt-controller:
> + description: identifies the node as an interrupt controller
> + type: object
> + additionalProperties: false
> + properties:
> + interrupt-controller: true
> +
> + "#address-cells":
> + const: 0
> +
> + "#interrupt-cells":
> + const: 1
> +
> + required:
> + - interrupt-controller
> + - "#address-cells"
> + - "#interrupt-cells"
> +
> +required:
> + - reg
> + - reg-names
> + - interrupts
> + - interrupt-map
> + - interrupt-map-mask
> + - msi-map
> + - "#interrupt-cells"
> + - interrupt-controller
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + soc {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + pcie@...31000 {
> + compatible = "amd,versal2-mdb-host";
> + reg = <0x0 0xed931000 0x0 0x2000>,
> + <0x1000 0x100000 0x0 0xff00000>,
> + <0x1000 0x0 0x0 0x100000>,
DBI space is 1MB? Last I checked, there's less than 4KB worth of
registers.
The address looks odd. The config space is purely iATU configuration.
Really, we should have described the entire address space (like the
endpoint) available to the ATU. So the 1MB offset in the base
address seems like just that. Most h/w design to cut down signal
routing would put the base address for the ATU input at something
aligned greater than the size of the address space.
> + <0x0 0xed860000 0x0 0x2000>;
And then the DBI and ATU registers are nowhere near each other?
Possible, but seems odd.
> + reg-names = "mdb_pcie_slcr", "config", "dbi", "atu";
> + ranges = <0x2000000 0x00 0xa8000000 0x00 0xa8000000 0x00 0x10000000>,
> + <0x43000000 0x1100 0x00 0x1100 0x00 0x00 0x1000000>;
> + interrupts = <GIC_SPI 198 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-parent = <&gic>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0 0 0 1 &pcie_intc_0 0>,
> + <0 0 0 2 &pcie_intc_0 1>,
> + <0 0 0 3 &pcie_intc_0 2>,
> + <0 0 0 4 &pcie_intc_0 3>;
> + msi-map = <0x0 &gic_its 0x00 0x10000>;
> + #address-cells = <3>;
> + #size-cells = <2>;
> + #interrupt-cells = <1>;
> + device_type = "pci";
> + pcie_intc_0: interrupt-controller {
> + #address-cells = <0>;
> + #interrupt-cells = <1>;
> + interrupt-controller;
> + };
> + };
> + };
> --
> 2.34.1
>
Powered by blists - more mailing lists