linux-kernel - Re: [PATCH 5/5] dt-bindings: Fix incorrect 'reg' property sizes

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 for Android: free password hash cracker in your pocket

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

Message-ID: <158931997603.215346.13048447179585746005@swboyd.mtv.corp.google.com>
Date:   Tue, 12 May 2020 14:46:16 -0700
From:   Stephen Boyd <sboyd@...nel.org>
To:     Rob Herring <robh@...nel.org>, devicetree@...r.kernel.org
Cc:     linux-clk@...r.kernel.org, linux-usb@...r.kernel.org,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH 5/5] dt-bindings: Fix incorrect 'reg' property sizes

Quoting Rob Herring (2020-05-12 13:45:43)
> The examples template is a 'simple-bus' with a size of 1 cell for
> #address-cells and #size-cells. The schema was only checking the entries
> had between 2 and 4 cells which really only errors on I2C or SPI type
> devices with a single cell.
> 
> The easiest fix in most cases is to change the 'reg' property to for 1 cell
> address and size. In some cases with child devices having 2 cells, that
> doesn't make sense so a bus node is needed.
> 
> Signed-off-by: Rob Herring <robh@...nel.org>
> ---

Acked-by: Stephen Boyd <sboyd@...nel.org> # clk