linux-kernel - Re: [PATCH 1/5] dt-bindings: remoteproc: Add PRU consumer bindings

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] [day] [month] [year] [list]

Message-ID: <4fd5d68a-830a-83df-fc7a-1070e2619a86@lechnology.com>
Date:   Mon, 4 Jan 2021 13:56:01 -0600
From:   David Lechner <david@...hnology.com>
To:     robh@...nel.org
Cc:     bjorn.andersson@...aro.org, devicetree@...r.kernel.org,
        grzegorz.jaszczyk@...aro.org, lee.jones@...aro.org,
        linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
        linux-omap@...r.kernel.org, linux-remoteproc@...r.kernel.org,
        mathieu.poirier@...aro.org, ohad@...ery.com, praneeth@...com,
        rogerq@...com, s-anna@...com, ssantosh@...nel.org
Subject: Re: [PATCH 1/5] dt-bindings: remoteproc: Add PRU consumer bindings


> Also, I think you can get rid of 'ti,pruss-gp-mux-sel'. Can't it just
> be an arg cell in 'ti,prus' entries?
> 
> Rob

+1 for using cells instead of a separate property.

FYI, we will have a similar issue with the PRUSSEVTSEL signal for the
interrupt controller on the AM18XX. I am still of the opinion (described
in more detail at [1]) that using a cell for this makes for both better
device tree bindings and easier driver implementation. So I am interested
to see what the resolution is here.

[1]: https://patchwork.kernel.org/project/linux-arm-kernel/patch/20190708035243.12170-5-s-anna@ti.com/