linux-kernel - RE: [PATCH 1/1] Add Wondermedia Technologies (wmt) to docs/devicetree/vendor-bindings.txt

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]

Date:	Thu, 19 Jul 2012 12:39:51 +0000
From:	Tony Prisk <linux@...sktech.co.nz>
To:	Arnd Bergmann <arnd@...db.de>
CC:	"vt8500-wm8505-linux-kernel@...glegroups.com" 
	<vt8500-wm8505-linux-kernel@...glegroups.com>,
	Alexey Charkov <alchark@...il.com>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	Russell King <linux@....linux.org.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH 1/1] Add Wondermedia Technologies (wmt) to
 docs/devicetree/vendor-bindings.txt

_______________________________________
From: Arnd Bergmann [arnd@...db.de]
Sent: 20 July 2012 00:28
To: Tony Prisk
Cc: vt8500-wm8505-linux-kernel@...glegroups.com; Alexey Charkov; devicetree-discuss@...ts.ozlabs.org; Russell King; linux-kernel@...r.kernel.org; linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/1] Add Wondermedia Technologies (wmt) to docs/devicetree/vendor-bindings.txt

On Thursday 19 July 2012, Tony Prisk wrote:
> I have no issue with that.
>
> I am mainly concerned with the Wondermedia products at the moment.
>
> Adding device tree support for WM8505 (and WM8650) is my main goal as the WM8650
> currently isn't supported and trying to get another board file added seems unlikely with
> everything moving to device tree. The VT8500 requires additional/different patches and
> as I don't have a vt8500 I can't test them.
>
> It does raise the question of applying 'wmt, prizm-pmc' to the vt8500 though. While it's
> fine for the restart patch I submitted, the vt8500 registers are the same but the bit-fields
> are different and therefore not entirely compatible with 'prizm-pmc'.
> When it comes to other PMC-related features, in particular the clocks, the VT8500 is quite
> different in its bit-fields.
>
> The vt8500 isn't technically in the Prizm family, as that is Wondermedia's name for the SoC's.
>

My point is that for each peripheral, we should decide separately what the
most descriptive name for it is. If the pmc is common for all wmt prizm
chips, then using the "wmt,prizm-pmc" string makes sense, and vt8500
can use "via,vt8500-pmc" or something like that.

However for stuff like the rtc that appears to be unchanged between them,
I would use the compatible string of the oldest known chip using it,
so even a wmt8650 should just claim compatibility with vt8500 there and
list both "wmt,wm8650-rtc" and "via,vt8500-rtc" there.

        Arnd

-----

Sounds reasonable. If device tree had been done when VT8500 came out, then the WM8xxx
products would have used the vt8500 compatibilities, so it makes sense to use the same logic
now.

Which brings us back to the original question (and raises another one) - can we assume yet that
'wmt' will be the vendor-binding for Wondermedia? Also, what are we going to use for VIA-based
SoC's given that VIA is the ticker for VIACOM. 

I did do a bit of a search on some stock tickers - 'WM' is Waste Management Inc. on the NYSE.
Presumably this would be as safe, or safer, than WMT (Walmart).
VIACOM, being a media content company, seems unlikely to produce any hardware but its possible
they will rebrand others hardware.

Regards,
Tony P--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/