netdev - Re: [PATCH v2 2/3] net: can: c_can: Add syscon/regmap RAMINIT mechanism

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:	Tue, 30 Sep 2014 16:58:01 +0300
From:	Roger Quadros <rogerq@...com>
To:	Wolfram Sang <wsa@...-dreams.de>
CC:	<wg@...ndegger.com>, <mkl@...gutronix.de>, <tony@...mide.com>,
	<tglx@...utronix.de>, <mugunthanvnm@...com>,
	<george.cherian@...com>, <balbi@...com>, <nsekhar@...com>,
	<nm@...com>, <sergei.shtylyov@...entembedded.com>,
	<linux-omap@...r.kernel.org>, <linux-can@...r.kernel.org>,
	<netdev@...r.kernel.org>
Subject: Re: [PATCH v2 2/3] net: can: c_can: Add syscon/regmap RAMINIT mechanism

On 09/30/2014 04:52 PM, Wolfram Sang wrote:
> 
>>>> +- ti,raminit-syscon	: Handle to system control region that contains the
>>>> +			  RAMINIT register. If specified, the second memory resource
>>>> +			  in the reg property must index into the RAMINIT
>>>> +			  register within the syscon region
>>>
>>> There seems to be a simple "syscon" property these days.
>>
>> I had used plain "syscon" in the earlier revisions but was asked to make it a TI specific
>> property since only TI uses this mechanism.
> 
> I see, when was that? Currently, it looks messy :( Grepping through the
> dts files in 3.17-rc7, I see that bcm7445 uses "syscon" and variants
> with prefixes, STE uses it, too. Samsung uses "samsung,syscon-phandle",
> st uses "st,syscon"...
> 
> The MACID readout patches for AM335x (just applied right now) also use
> "syscon": https://patchwork.ozlabs.org/patch/394289/
> 
> I'd vote for a generic "syscon" to be OK, yet I guess the DT maintainers
> will have the final word.

Now that I actually checked, it was never just "syscon" but just without the "ti" vendor prefix.
Sorry for the misinformation.

As just TI is using this out of band RAMINIT mechanism, should it be "ti,syscon" or just "syscon"?

cheers,
-roger
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html