| 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: <3e54d23b.14bf.1995b523ddf.Coremail.zhangsenchuan@eswincomputing.com>
Date: Thu, 18 Sep 2025 13:35:40 +0800 (GMT+08:00)
From: zhangsenchuan <zhangsenchuan@...incomputing.com>
To: "Bjorn Helgaas" <helgaas@...nel.org>
Cc: bhelgaas@...gle.com, lpieralisi@...nel.org, kwilczynski@...nel.org,
mani@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-pci@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
p.zabel@...gutronix.de, johan+linaro@...nel.org,
quic_schintav@...cinc.com, shradha.t@...sung.com, cassel@...nel.org,
thippeswamy.havalige@....com, mayank.rana@....qualcomm.com,
inochiama@...il.com, ningyu@...incomputing.com,
linmin@...incomputing.com, pinkesh.vaghela@...fochips.com
Subject: Re: Re: [PATCH v2 1/2] dt-bindings: PCI: eic7700: Add Eswin eic7700
PCIe host controller
> -----Original Messages-----
> From: "Bjorn Helgaas" <helgaas@...nel.org>
> Send time:Friday, 05/09/2025 00:06:00
> To: zhangsenchuan@...incomputing.com
> Cc: bhelgaas@...gle.com, lpieralisi@...nel.org, kwilczynski@...nel.org, mani@...nel.org, robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org, linux-pci@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, p.zabel@...gutronix.de, johan+linaro@...nel.org, quic_schintav@...cinc.com, shradha.t@...sung.com, cassel@...nel.org, thippeswamy.havalige@....com, mayank.rana@....qualcomm.com, inochiama@...il.com, ningyu@...incomputing.com, linmin@...incomputing.com, pinkesh.vaghela@...fochips.com
> Subject: Re: [PATCH v2 1/2] dt-bindings: PCI: eic7700: Add Eswin eic7700 PCIe host controller
>
> On Fri, Aug 29, 2025 at 04:22:37PM +0800, zhangsenchuan@...incomputing.com wrote:
> > From: Senchuan Zhang <zhangsenchuan@...incomputing.com>
> >
> > Add Device Tree binding documentation for the ESWIN EIC7700
> > PCIe controller module,the PCIe controller enables the core
> > to correctly initialize and manage the PCIe bus and connected
> > devices.
> >
> > Signed-off-by: Yu Ning <ningyu@...incomputing.com>
> > Signed-off-by: Senchuan Zhang <zhangsenchuan@...incomputing.com>
> > ---
> > .../bindings/pci/eswin,eic7700-pcie.yaml | 142 ++++++++++++++++++
> > 1 file changed, 142 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/pci/eswin,eic7700-pcie.yaml
> >
> > diff --git a/Documentation/devicetree/bindings/pci/eswin,eic7700-pcie.yaml b/Documentation/devicetree/bindings/pci/eswin,eic7700-pcie.yaml
> > new file mode 100644
> > index 000000000000..65f640902b11
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pci/eswin,eic7700-pcie.yaml
> > @@ -0,0 +1,142 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/pci/eswin,eic7700-pcie.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Eswin EIC7700 PCIe host controller
> > +
> > +maintainers:
> > + - Yu Ning <ningyu@...incomputing.com>
> > + - Senchuan Zhang <zhangsenchuan@...incomputing.com>
> > +
> > +description:
> > + The PCIe controller on EIC7700 SoC.
> > +
> > +allOf:
> > + - $ref: /schemas/pci/pci-host-bridge.yaml#
> > +
> > +properties:
> > + compatible:
> > + const: eswin,eic7700-pcie
> > +
> > + reg:
> > + maxItems: 3
> > +
> > + reg-names:
> > + items:
> > + - const: dbi
> > + - const: config
> > + - const: mgmt
> > +
> > + ranges:
> > + maxItems: 3
> > +
> > + num-lanes:
> > + const: 4
> > +
> > + '#interrupt-cells':
> > + const: 1
> > +
> > + interrupts:
> > + maxItems: 9
> > +
> > + interrupt-names:
> > + items:
> > + - const: msi
> > + - const: inta
> > + - const: intb
> > + - const: intc
> > + - const: intd
> > + - const: inte
> > + - const: intf
> > + - const: intg
> > + - const: inth
> > +
> > + interrupt-map:
> > + maxItems: 4
> > +
> > + interrupt-map-mask:
> > + items:
> > + - const: 0
> > + - const: 0
> > + - const: 0
> > + - const: 7
> > +
> > + clocks:
> > + maxItems: 4
> > +
> > + clock-names:
> > + items:
> > + - const: mstr
> > + - const: dbi
> > + - const: pclk
> > + - const: aux
> > +
> > + resets:
> > + maxItems: 3
> > +
> > + reset-names:
> > + items:
> > + - const: cfg
> > + - const: powerup
> > + - const: pwren
> > +
> > +required:
> > + - compatible
> > + - reg
> > + - ranges
> > + - num-lanes
> > + - interrupts
> > + - interrupt-names
> > + - interrupt-map-mask
> > + - interrupt-map
> > + - '#interrupt-cells'
> > + - clocks
> > + - clock-names
> > + - resets
> > + - reset-names
> > +
> > +unevaluatedProperties: false
> > +
> > +examples:
> > + - |
> > + soc {
> > + #address-cells = <2>;
> > + #size-cells = <2>;
> > +
> > + pcie@...00000 {
> > + compatible = "eswin,eic7700-pcie";
> > + reg = <0x0 0x54000000 0x0 0x4000000>,
> > + <0x0 0x40000000 0x0 0x800000>,
> > + <0x0 0x50000000 0x0 0x100000>;
> > + reg-names = "dbi", "config", "mgmt";
> > + #address-cells = <3>;
> > + #size-cells = <2>;
> > + #interrupt-cells = <1>;
> > + ranges = <0x81000000 0x0 0x40800000 0x0 0x40800000 0x0 0x800000>,
> > + <0x82000000 0x0 0x41000000 0x0 0x41000000 0x0 0xf000000>,
> > + <0xc3000000 0x80 0x00000000 0x80 0x00000000 0x2 0x00000000>;
> > + bus-range = <0x0 0xff>;
> > + clocks = <&clock 562>,
> > + <&clock 563>,
> > + <&clock 564>,
> > + <&clock 565>;
> > + clock-names = "mstr", "dbi", "pclk", "aux";
> > + resets = <&reset 8 (1 << 0)>,
> > + <&reset 8 (1 << 1)>,
> > + <&reset 8 (1 << 2)>;
> > + reset-names = "cfg", "powerup", "pwren";
> > + interrupts = <220>, <179>, <180>, <181>, <182>, <183>, <184>, <185>, <186>;
> > + interrupt-names = "msi", "inta", "intb", "intc", "intd",
> > + "inte", "intf", "intg", "inth";
> > + interrupt-parent = <&plic>;
> > + interrupt-map-mask = <0x0 0x0 0x0 0x7>;
> > + interrupt-map = <0x0 0x0 0x0 0x1 &plic 179>,
> > + <0x0 0x0 0x0 0x2 &plic 180>,
> > + <0x0 0x0 0x0 0x3 &plic 181>,
> > + <0x0 0x0 0x0 0x4 &plic 182>;
> > + device_type = "pci";
> > + num-lanes = <0x4>;
>
> num-lanes and perst are per-Root Port items. Please put anything
> related specifically to the Root Port in its own stanza to make it
> easier to support multiple Root Ports in future versions of the
> hardware.
>
> See
> https://lore.kernel.org/linux-pci/20250625221653.GA1590146@bhelgaas/
> for examples of how to do this.
Dear Bjorn
Thank you very much for your review.
I think the suggestions you put forward are very good，I placed perst in the
root port as per your suggestion.
I'm a bit confused about the "num-lanes" attribute.
The "num-lanes" attribute will be parsed in the "pcie-designware.c" file. In the
"pcie-designware-host.c" file, When our driver calls the dw_pcie_host_init function
for initialization, the attribute "num_lanes" will be judged. If the attribute is
available, use the value parsed from the device tree. If the attribute cannot be
obtained from the node, the lanes supported by the hardware default will be obtained
by reading the register.Can I avoid reparsing the num-lanes attribute?
I saw vendors based on Synopsys implementation. They separated the root port node
and did not place "num-lanes" in the root port node.
For examples:
hisilicon,kirin-pcie.yaml
qcom,pcie-sc7280.yaml
qcom,pcie-sa8255p.yaml
Is it allowed for me not to place "num-lanes" in the root port node?
Looking forward to your reply, thanks!
Best regards,
Senchuan zhang
Powered by blists - more mailing lists