On Fri, Feb 07, 2025 at 10:30:23PM +0100, J. Neuschäfer via B4 Relay wrote: > From: "J. Neuschäfer" <j.ne@xxxxxxxxxx> > > Formalise the binding for the PCI controllers in the Freescale MPC8xxx > chip family. Information about PCI-X-specific properties was taken from > fsl,pci.txt. The examples were taken from mpc8315erdb.dts and > xpedite5200_xmon.dts. > > Signed-off-by: J. Neuschäfer <j.ne@xxxxxxxxxx> > --- > > V2: > - merge fsl,pci.txt into fsl,mpc8xxx-pci.yaml > - regroup compatible strings, list single-item values in one enum > - trim subject line (remove "binding") > - fix property order to comply with dts coding style > --- > .../devicetree/bindings/pci/fsl,mpc8xxx-pci.yaml | 115 +++++++++++++++++++++ > Documentation/devicetree/bindings/pci/fsl,pci.txt | 27 ----- > 2 files changed, 115 insertions(+), 27 deletions(-) > > diff --git a/Documentation/devicetree/bindings/pci/fsl,mpc8xxx-pci.yaml b/Documentation/devicetree/bindings/pci/fsl,mpc8xxx-pci.yaml > new file mode 100644 > index 0000000000000000000000000000000000000000..57c5503cec47e6e90ed2b09835bfad10309db927 > --- /dev/null > +++ b/Documentation/devicetree/bindings/pci/fsl,mpc8xxx-pci.yaml > @@ -0,0 +1,115 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > + > +$id: http://devicetree.org/schemas/pci/fsl,mpc8xxx-pci.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Freescale MPC83xx PCI/PCI-X/PCIe controllers > + > +description: | > + Binding for the PCI/PCI-X/PCIe host bridges on MPC8xxx SoCs. > + See also: Documentation/devicetree/bindings/pci/fsl,pci.txt This is obviously a bit wrong; I ended up putting the information from fsl,pci.txt entirely under the fsl,pci-agent-force-enum property, but forgot to remove the reference to the old txt file. > +properties: [...] > + fsl,pci-agent-force-enum: > + type: boolean > + description: > + Typically any Freescale PCI-X bridge hardware strapped into Agent mode is > + prevented from enumerating the bus. The PrPMC form-factor requires all > + mezzanines to be PCI-X Agents, but one per system may still enumerate the > + bus. > + > + This property allows a PCI-X bridge to be used for bus enumeration > + despite being strapped into Agent mode. > + > +required: > + - reg > + - compatible
