linux-kernel - Re: [alsa-devel] [PATCH 1/2] ASoC: cygnus-audio: adding device tree 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <551A4C37.5090903@metafoo.de>
Date:	Tue, 31 Mar 2015 09:26:47 +0200
From:	Lars-Peter Clausen <lars@...afoo.de>
To:	Scott Branden <sbranden@...adcom.com>,
	Rob Herring <robh+dt@...nel.org>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Mark Brown <broonie@...nel.org>,
	Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.de>,
	alsa-devel@...a-project.org
CC:	devicetree@...r.kernel.org, Lori Hikichi <lhikichi@...adcom.com>,
	linux-kernel@...r.kernel.org, bryeung@...gle.com,
	abrestic@...gle.com, bcm-kernel-feedback-list@...adcom.com,
	linux-arm-kernel@...ts.infradead.org, pwestin@...gle.com,
	Anatol Pomazao <anatol@...gle.com>, olofj@...gle.com,
	Dmitry Torokhov <dtor@...gle.com>,
	linux-rpi-kernel@...ts.infradead.org
Subject: Re: [alsa-devel] [PATCH 1/2] ASoC: cygnus-audio: adding device tree
 bindings

On 03/31/2015 05:16 AM, Scott Branden wrote:
[...]
> +- ssp-port-id: The ssp port interface to use
> +	Valid value are 0, 1, 2, or 3 (for spdif)

How about using 'reg' as the property name here. It is the standard property 
name for identifying or assigning an address to a sub-node.

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