linux-kernel - Re: [PATCH 1/2] remoteproc: core: Add rproc OF look-up functions

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:	Thu, 11 Aug 2016 11:23:25 -0700
From:	Bjorn Andersson <bjorn.andersson@...aro.org>
To:	Suman Anna <s-anna@...com>
Cc:	Tony Lindgren <tony@...mide.com>, Lee Jones <lee.jones@...aro.org>,
	"ohad@...ery.com" <ohad@...ery.com>,
	"kernel@...inux.com" <kernel@...inux.com>,
	"linux-remoteproc@...r.kernel.org" <linux-remoteproc@...r.kernel.org>,
	"patrice.chotard@...com" <patrice.chotard@...com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ludovic.barre@...com" <ludovic.barre@...com>,
	"ssantosh@...nel.org" <ssantosh@...nel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Dave Gerlach <d-gerlach@...com>
Subject: Re: [PATCH 1/2] remoteproc: core: Add rproc OF look-up functions

On Wed 10 Aug 15:44 PDT 2016, Suman Anna wrote:

> On 08/10/2016 04:19 PM, Bjorn Andersson wrote:
> > On Wed 10 Aug 14:04 PDT 2016, Suman Anna wrote:
> > 
[..]
> > As far as cleaning up wkup_m3_ipc, patch 2 does that and cleans out the
> > old implementation and with that wkup_m3_ipc is moved to the new API.
> > 
> > So the only issue is that the wkup_m3_ipc DT binding states that the
> > property should be named "ti,rproc" and as such someone has to send a
> > patch to that and make an argument that we don't have to maintain
> > backwards compatibility. But as this is used in am33xx.dtsi and
> > am4372.dtsi that might be too late?
> 
> I could fix up the wkup_m3_ipc driver using of_update_property() /
> of_remove_property(), but looks like these are not exported. I am not
> sure if there are any specific reasons as to why these were not
> exported. So, for now, we may have to go with the current code.
> 

Sorry I didn't think that far, that would be the preferred solution.

Regards,
Bjorn