| 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: <a4e1765a-8768-8e1d-9556-34644fcce101@linaro.org>
Date: Wed, 29 Jun 2022 08:32:22 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Vidya Sagar <vidyas@...dia.com>, bhelgaas@...gle.com,
lorenzo.pieralisi@....com, robh+dt@...nel.org,
thierry.reding@...il.com, jonathanh@...dia.com
Cc: kishon@...com, vkoul@...nel.org, kw@...ux.com,
p.zabel@...gutronix.de, mperttunen@...dia.com,
linux-pci@...r.kernel.org, devicetree@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-phy@...ts.infradead.org, kthota@...dia.com,
mmaddireddy@...dia.com, sagar.tv@...il.com
Subject: Re: [PATCH V3 03/11] dt-bindings: PCI: tegra234: Add schema for
tegra234 rootport mode
On 29/06/2022 08:04, Vidya Sagar wrote:
> Add support for PCIe controllers that operate in the rootport mode
> in tegra234 chipset.
>
> Signed-off-by: Vidya Sagar <vidyas@...dia.com>
> ---
> V3:
> * New patch in this series
>
> .../bindings/pci/nvidia,tegra194-pcie.yaml | 151 +++++++++++++++++-
> 1 file changed, 146 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.yaml b/Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.yaml
> index 4a49dddf33bb..ede53baa1d71 100644
> --- a/Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.yaml
> +++ b/Documentation/devicetree/bindings/pci/nvidia,tegra194-pcie.yaml
> @@ -22,6 +22,7 @@ properties:
> compatible:
> enum:
> - nvidia,tegra194-pcie
> + - nvidia,tegra234-pcie
>
> reg:
> items:
> @@ -82,6 +83,8 @@ properties:
> name for the PCIe controller. Following are the specifiers for the different PCIe
> controllers:
>
> + Tegra194
> +
> - TEGRA194_POWER_DOMAIN_PCIEX8B: C0
> - TEGRA194_POWER_DOMAIN_PCIEX1A: C1
> - TEGRA194_POWER_DOMAIN_PCIEX1A: C2
> @@ -91,6 +94,22 @@ properties:
>
> these specifiers are defined in "include/dt-bindings/power/tegra194-powergate.h" file.
>
> + Tegra234
> +
> + - TEGRA234_POWER_DOMAIN_PCIEX4BA: C0
> + - TEGRA234_POWER_DOMAIN_PCIEX1A : C1
> + - TEGRA234_POWER_DOMAIN_PCIEX1A : C2
> + - TEGRA234_POWER_DOMAIN_PCIEX1A : C3
> + - TEGRA234_POWER_DOMAIN_PCIEX4BB: C4
> + - TEGRA234_POWER_DOMAIN_PCIEX8A : C5
> + - TEGRA234_POWER_DOMAIN_PCIEX4A : C6
> + - TEGRA234_POWER_DOMAIN_PCIEX8B : C7
> + - TEGRA234_POWER_DOMAIN_PCIEX4CA: C8
> + - TEGRA234_POWER_DOMAIN_PCIEX4CB: C9
> + - TEGRA234_POWER_DOMAIN_PCIEX4CC: C10
Why duplicating header?
> +
> + these specifiers are defined in "include/dt-bindings/power/tegra234-powergate.h" file.
> +
> interconnects:
> items:
> - description: memory read client
> @@ -112,17 +131,30 @@ properties:
> Must contain a pair of phandle to BPMP controller node followed by controller ID. Following
> are the controller IDs for each controller:
>
> + Tegra194
> +
> 0: C0
> 1: C1
> 2: C2
> 3: C3
> 4: C4
> 5: C5
> - items:
> - - items:
> - - minimum: 0
> - maximum: 0xffffffff
> - - enum: [ 0, 1, 2, 3, 4, 5 ]
> +
> + Tegra234
> +
> + 0 : C0
> + 1 : C1
> + 2 : C2
> + 3 : C3
> + 4 : C4
> + 5 : C5
> + 6 : C6
> + 7 : C7
> + 8 : C8
> + 9 : C9
> + 10: C10
> +
> + Platform constraints are described later
>
> nvidia,update-fc-fixup:
> description: |
> @@ -131,6 +163,8 @@ properties:
> enabling root port to exchange optimum number of FC (Flow Control) credits with downstream
> devices:
>
> + NOTE:- This is applicable only for Tegra194.
> +
Then make it false in other variants in allOf:if:then
> 1. If C0/C4/C5 run at x1/x2 link widths (irrespective of speed and MPS)
> 2. If C0/C1/C2/C3/C4/C5 operate at their respective max link widths and
> a) speed is Gen-2 and MPS is 256B
> @@ -159,10 +193,56 @@ properties:
> description: A phandle to the regulator node that supplies 12V to the slot if the platform has
> one such slot. (Ex:- x16 slot owned by C5 controller in p2972-0000 platform).
>
> + nvidia,enable-srns:
> + description: |
> + This boolean property needs to be present if the controller is configured
Remove "This boolean property needs to be present" and instead describe
the feature behind, e.g. "Configure the controller to operate in SRNS
......".
There is no need to make descriptions longer than necessary.
> + to operate in SRNS (Separate Reference Clocks with No Spread-Spectrum Clocking).
> + NOTE:- This is applicable only for Tegra234.
Make it false on other variants (allOf:if:then)
> +
No need for such blank lines.
> + $ref: /schemas/types.yaml#/definitions/flag
type: boolean (the same in your patch #2)
> +
> + nvidia,enable-ext-refclk:
> + description: |
> + This boolean property needs to be present if the controller is configured
> + to use the reference clocking coming in from an external clock source instead of
> + using the internal clock source.
> +
> + $ref: /schemas/types.yaml#/definitions/flag
> +
> allOf:
> - $ref: "/schemas/pci/pci-bus.yaml#"
> - $ref: "/schemas/pci/snps,dw-pcie.yaml#"
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - nvidia,tegra194-pcie
> + then:
> + properties:
> + nvidia,bpmp:
> + items:
> + - items:
> + - minimum: 0
> + maximum: 0xffffffff
> + - enum: [ 0, 1, 2, 3, 4, 5 ]
> +
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - nvidia,tegra234-pcie
> + then:
> + properties:
> + nvidia,bpmp:
> + items:
> + - items:
> + - minimum: 0
> + maximum: 0xffffffff
> + - enum: [ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 ]
> +
> unevaluatedProperties: false
>
> required:
> @@ -252,3 +332,64 @@ examples:
> phy-names = "p2u-0", "p2u-1", "p2u-2", "p2u-3";
> };
> };
> +
> + - |
> + #include <dt-bindings/clock/tegra234-clock.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> + #include <dt-bindings/power/tegra234-powergate.h>
> + #include <dt-bindings/reset/tegra234-reset.h>
> +
> + bus@0 {
> + #address-cells = <2>;
> + #size-cells = <2>;
> + ranges = <0x0 0x0 0x0 0x8 0x0>;
> +
> + pcie@...60000 {
> + compatible = "nvidia,tegra234-pcie";
> + power-domains = <&bpmp TEGRA234_POWER_DOMAIN_PCIEX4BB>;
> + reg = <0x00 0x14160000 0x0 0x00020000>, /* appl registers (128K) */
> + <0x00 0x36000000 0x0 0x00040000>, /* configuration space (256K) */
> + <0x00 0x36040000 0x0 0x00040000>, /* iATU_DMA reg space (256K) */
> + <0x00 0x36080000 0x0 0x00040000>; /* DBI reg space (256K) */
> + reg-names = "appl", "config", "atu_dma", "dbi";
> +
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <4>;
> + num-viewport = <8>;
> + linux,pci-domain = <4>;
> +
> + clocks = <&bpmp TEGRA234_CLK_PEX0_C4_CORE>;
> + clock-names = "core";
> +
> + resets = <&bpmp TEGRA234_RESET_PEX0_CORE_4_APB>,
> + <&bpmp TEGRA234_RESET_PEX0_CORE_4>;
> + reset-names = "apb", "core";
> +
> + interrupts = <GIC_SPI 51 IRQ_TYPE_LEVEL_HIGH>, /* controller interrupt */
> + <GIC_SPI 52 IRQ_TYPE_LEVEL_HIGH>; /* MSI interrupt */
> + interrupt-names = "intr", "msi";
> +
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 0>;
> + interrupt-map = <0 0 0 0 &gic GIC_SPI 51 IRQ_TYPE_LEVEL_HIGH>;
> +
> + nvidia,bpmp = <&bpmp 4>;
> +
> + nvidia,aspm-cmrt-us = <60>;
> + nvidia,aspm-pwr-on-t-us = <20>;
> + nvidia,aspm-l0s-entrance-latency-us = <3>;
> +
> + bus-range = <0x0 0xff>;
> + ranges = <0x43000000 0x21 0x40000000 0x21 0x40000000 0x2 0xe8000000>, /* prefetchable */
> + <0x02000000 0x0 0x40000000 0x24 0x28000000 0x0 0x08000000>, /* non-prefetchable */
> + <0x01000000 0x0 0x36100000 0x00 0x36100000 0x0 0x00100000>; /* downstream I/O */
> +
> + vddio-pex-ctl-supply = <&p3701_vdd_AO_1v8>;
> +
> + phys = <&p2u_hsio_4>, <&p2u_hsio_5>, <&p2u_hsio_6>,
> + <&p2u_hsio_7>;
> + phy-names = "p2u-0", "p2u-1", "p2u-2", "p2u-3";
> + };
> + };
Best regards,
Krzysztof
Powered by blists - more mailing lists