linux-kernel - Re: [PATCH] arm/dt: tegra devicetree support

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]

Message-ID: <20110720183133.GE4642@ponder.secretlab.ca>
Date:	Wed, 20 Jul 2011 12:31:33 -0600
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Stephen Warren <swarren@...dia.com>,
	Erik Gilling <konkers@...roid.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>,
	Colin Cross <ccross@...roid.com>,
	Olof Johansson <olof@...om.net>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	Russell King <linux@....linux.org.uk>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH] arm/dt: tegra devicetree support

On Wed, Jul 20, 2011 at 05:03:55PM +0100, Mark Brown wrote:
> On Wed, Jul 20, 2011 at 08:37:19AM -0700, Stephen Warren wrote:
> > Grant Likely wrote at Tuesday, July 19, 2011 5:43 PM:
> 
> > > +	sound {
> > > +		compatible = "nvidia,harmony-sound", "nvidia,tegra-wm8903";
> 
> > I thought the sound bindings were still somewhat experimental and not
> > completely agreed upon. One issue I see is that Device Tree is
> > supposed to represent pure HW, rather than driver-required abstractions,
> > and at least the compatible name here is pretty Linux-driver-specific.
> 
> The current decision is that the schematic for embedded audio hardware
> is sufficiently interesting to be considered hardware in its own right
> separately to the chips contained within it.

Correct.  For complex composite devices like audio, it is completely
appropriate to have a root node that represents the entire complex and
how it is wired together.

The compatible property here definitely represents the hardware
because it reflects the sound infrastructure on the harmony board.

g.
--
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/