linux-kernel - Re: [PATCH 3/3] dt-bindings: PCI: Convert generic host binding to DT schema

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_Jsq+24qYqN6u1o93gkGm13GZeSRQM4uor0170HeFbLdU-xQ@mail.gmail.com>
Date:   Mon, 30 Dec 2019 16:29:48 -0700
From:   Rob Herring <robh@...nel.org>
To:     Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:     "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        linux-pci <linux-pci@...r.kernel.org>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Andrew Murray <andrew.murray@....com>,
        Zhou Wang <wangzhou1@...ilicon.com>,
        Will Deacon <will@...nel.org>,
        David Daney <david.daney@...ium.com>,
        Linux-Renesas <linux-renesas-soc@...r.kernel.org>
Subject: Re: [PATCH 3/3] dt-bindings: PCI: Convert generic host binding to DT schema

On Thu, Dec 12, 2019 at 7:41 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> Hi Rob,
>
> On Sat, Nov 16, 2019 at 1:53 AM Rob Herring <robh@...nel.org> wrote:
> > Convert the generic PCI host binding to DT schema. The derivative Juno,
> > PLDA XpressRICH3-AXI, and Designware ECAM bindings all just vary in
> > their compatible strings. The simplest way to convert those to
> > schema is just add them into the common generic PCI host schema.
> >
> > Cc: Bjorn Helgaas <bhelgaas@...gle.com>
> > Cc: Lorenzo Pieralisi <lorenzo.pieralisi@....com>
> > Cc: Andrew Murray <andrew.murray@....com>
> > Cc: Zhou Wang <wangzhou1@...ilicon.com>
> > Cc: Will Deacon <will@...nel.org>
> > Cc: David Daney <david.daney@...ium.com>
> > Signed-off-by: Rob Herring <robh@...nel.org>
>
> > index 515b2f9542e5..000000000000
> > --- a/Documentation/devicetree/bindings/pci/designware-pcie-ecam.txt
> > +++ /dev/null
>
> > -Example:
> > -
> > -    pcie1: pcie@...00000 {
> > -        compatible = "socionext,synquacer-pcie-ecam", "snps,dw-pcie-ecam";
> > -        device_type = "pci";
> > -        reg = <0x0 0x7f000000 0x0 0xf00000>;
> > -        bus-range = <0x0 0xe>;
> > -        #address-cells = <3>;
> > -        #size-cells = <2>;
> > -        ranges = <0x1000000 0x00 0x00010000 0x00 0x7ff00000 0x0 0x00010000>,
> > -                 <0x2000000 0x00 0x70000000 0x00 0x70000000 0x0 0x0f000000>,
> > -                 <0x3000000 0x3f 0x00000000 0x3f 0x00000000 0x1 0x00000000>;
> > -
> > -        #interrupt-cells = <0x1>;
> > -        interrupt-map-mask = <0x0 0x0 0x0 0x0>;
>
> An all-zeroes interrupt-map-mask seems to be very common on embedded
> SoCs, where all devices are mapped to a single interrupt.

Indeed.

> However, schemas/pci/pci-bus.yaml says:
>
>   interrupt-map-mask:
>     items:
>       - description: PCI high address cell
>         minimum: 0
>         maximum: 0xf800
>       - description: PCI mid address cell
>         const: 0
>       - description: PCI low address cell
>         const: 0
>       - description: PCI IRQ cell
>         minimum: 1
>         maximum: 7
>
> and thus complains about an all-zeroes mask, e.g.
>
>     arch/arm64/boot/dts/renesas/r8a7795-salvator-x.dt.yaml:
> pcie@...00000: interrupt-map-mask:0:3: 0 is less than the minimum of 1

Now fixed.

Thanks,
Rob