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]
Date:   Mon, 23 Nov 2020 19:21:00 -0600
From:   Nishanth Menon <nm@...com>
To:     Sekhar Nori <nsekhar@...com>
CC:     Grygorii Strashko <grygorii.strashko@...com>,
        Device Tree Mailing List <devicetree@...r.kernel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Tero Kristo <t-kristo@...com>,
        Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, Faiz Abbas <faiz_abbas@...com>,
        Lokesh Vutla <lokeshvutla@...com>,
        Andre Przywara <andre.przywara@....com>
Subject: Re: [PATCH v2 2/4] arm64: dts: ti: k3: squelch warnings regarding no
 #address-cells for interrupt-controller

On 09:45-20201123, Sekhar Nori wrote:
> >> The main reason I commented - is hope to get some clarification from DT maintainers.
> >> 90% of interrupt-controller nodes do not have #address-cells and I never seen in in GPIO nodes
> >> (most often is present in PCI and GIC nodes).
> >> and nobody seems fixing it. So, if we are going to move this direction it's reasonable to get clarification to be sure.
> >>
> >> And there is no "never" here - #address-cells always can be added if really required.
> > 
> > 
> > OK - as a GPIO node, but as an interrupt-controller node, I was
> > looking at [1] and wondering if that was the precedence.
> > 
> > Yes, will be good to get direction from the DT maintainers on this
> > topic.
> 
> Shall I respin this series with 2/4 dropped while we wait for decision
> on this?
> 
> #address-cells warnings on interrupt controller can perhaps be handled
> all at once (there are many of those in existing DT anyway).
> 
> GPIO is basic support and holds up many other modules (like MMC/SD).


There are'nt too many new patches in my queue that depends on GPIO, I'd
rather not introduce new warnings unless we are completely at a
stalemate. I'd rather use this opportunity to understand where what we
need to be doing.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ