| 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
| ||
|
Date: Tue, 4 Feb 2014 20:02:39 +0100 From: Jean-Francois Moine <moinejf@...e.fr> To: Mark Brown <broonie@...nel.org> Cc: alsa-devel@...a-project.org, devicetree@...r.kernel.org, Dave Airlie <airlied@...il.com>, dri-devel@...ts.freedesktop.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, Rob Clark <robdclark@...il.com>, Russell King - ARM Linux <linux@....linux.org.uk> Subject: Re: [PATCH v3 3/5] ASoC: tda998x: add DT documentation of the tda998x CODEC On Tue, 4 Feb 2014 18:12:13 +0000 Mark Brown <broonie@...nel.org> wrote: > On Sat, Feb 01, 2014 at 05:48:49PM +0100, Jean-Francois Moine wrote: > > > + - compatible: must be "nxp,tda998x-codec". > > It's not clear to me why there's a separate compatible here - as far as > I can see this can only appear as part of one of these devices and > there's no addressing or other information that'd account for chip > variation so I'd not expect to need to bind this independently of the > parent. If there is no 'compatible', the CODEC module is not loaded, and, when the module is in the core, no CODEC device can be created from the DT. -- Ken ar c'hentañ | ** Breizh ha Linux atav! ** Jef | http://moinejf.free.fr/ -- 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/
Powered by blists - more mailing lists