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: Wed, 19 Mar 2014 20:31:45 +0100 From: Lars-Peter Clausen <lars@...afoo.de> To: Mark Brown <broonie@...nel.org> CC: Jyri Sarha <jsarha@...com>, Jean-Francois Moine <moinejf@...e.fr>, devicetree@...r.kernel.org, alsa-devel@...a-project.org, Xiubo Li <Li.Xiubo@...escale.com>, linux-kernel@...r.kernel.org, Kuninori Morimoto <kuninori.morimoto.gx@...esas.com> Subject: Re: [alsa-devel] [PATCH v3 4/4] ASoC: simple-card: Add DT documentation for multi-DAI links On 03/19/2014 08:21 PM, Mark Brown wrote: > On Wed, Mar 19, 2014 at 09:15:14PM +0200, Jyri Sarha wrote: >> On 03/19/2014 08:51 PM, Lars-Peter Clausen wrote: > >>> When does this make sense? Either the bitclock is inverted for all of >>> them or for none. > >> Definition of clock signal and it's inversion varies between chip >> manufacturers and sometimes it may not be possible to get all the dai >> drivers to work identically in this respect. Because of this in some cases >> there may be a need to set the inversion bit only at one end of the link. > > No, Linux has a definition of all the clock modes which applies to all > devices regardless of what the manufacturer documents in their > datasheet. > Yep. The clock properties are well defined for the different modes that can be specified in the format property. It's up to the driver to translate this to driver specific settings. If two drivers behave differently for the same mode one of them (or both) are broken. We should probably add the definitions for the different formats to the DT bindings. E.g. what is default, what is inverted polarity, etc. - Lars -- 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