linux-kernel - Re: [PATCH] dt-bindings: PCI: Remove obsolete .txt docs

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAL_JsqLS8qfRRRQ-FEirqo6FGWD4ypU5_=uc1mVu_U_Voga1=w@mail.gmail.com>
Date: Wed, 23 Apr 2025 08:02:04 -0500
From: Rob Herring <robh@...nel.org>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, Lorenzo Pieralisi <lpieralisi@...nel.org>, 
	Krzysztof Wilczyński <kw@...ux.com>, 
	Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
	Conor Dooley <conor+dt@...nel.org>, Thierry Reding <thierry.reding@...il.com>, 
	Jonathan Hunter <jonathanh@...dia.com>, Vidya Sagar <vidyas@...dia.com>, Frank Li <Frank.li@....com>, 
	linux-pci@...r.kernel.org, devicetree@...r.kernel.org, 
	linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, 
	Jean-Philippe Brucker <jean-philippe@...aro.org>
Subject: Re: [PATCH] dt-bindings: PCI: Remove obsolete .txt docs

On Tue, Apr 22, 2025 at 12:18 PM Bjorn Helgaas <helgaas@...nel.org> wrote:
>
> [+cc Jean-Philippe for virtio dangling ref]
>
> On Fri, Apr 04, 2025 at 05:15:57PM -0500, Rob Herring (Arm) wrote:
> > The content in these files has been moved to the schemas in dtschema.
> > pci.txt is covered by pci-bus-common.yaml and pci-host-bridge.yaml.
> > pci-iommu.txt is covered by pci-iommu.yaml. pci-msi.txt is covered in
> > msi-map property in pci-host-bridge.yaml.
>
> I guess "dtschema" refers to
> https://github.com/devicetree-org/dt-schema?

Yes.

> I kinda wish there was some direct link from the Linux kernel source
> to dt-schema where all this information now lives (Requester ID
> format, iommu-map, msi-map, linux,pci-domain, reg (and reference to
> IEEE Std 1275-1994), interrupt mapping info, external-facing, etc).
> Being a DT neophyte, I need all the help I can get ;)

Links to each property wouldn't really scale. Might as well copy all
the common schemas into the kernel tree at that point.

I've thought about some tool to look-up the info. It would be easy
enough to write. I'm just not sure what's useful to folks and what the
interface should look like. It could be something like this:

$ dt-info iommu-map
schema file: path/to/schema.yaml
type: uint32-matrix
description:
 blah blah

But maybe that needs to be "dt-info property <prop>" so we could also
do "dt-info compatible <compat>".

>
> There are a few dangling references to pci.txt:
>
>   Documentation/devicetree/bindings/pci/aardvark-pci.txt: - max-link-speed: see pci.txt
>   Documentation/devicetree/bindings/pci/aardvark-pci.txt: - reset-gpios: see pci.txt
>   Documentation/devicetree/bindings/pci/v3-v360epc-pci.txt:- bus-range: see pci.txt
>   Documentation/devicetree/bindings/pci/v3-v360epc-pci.txt:  1275-1994 (see pci.txt) with the following restriction:

If no one cares enough to convert these, then I don't think the link matters.

>   Documentation/devicetree/bindings/virtio/pci-iommu.yaml:      zero. See Documentation/devicetree/bindings/pci/pci.txt

That's fixed in my tree already.

Rob