linux-kernel - Re: [PATCHv2] ASoC: fsl-sai: using 'lsb-first' property instead of 'big-endian-data'.

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]

Date:	Fri, 29 Aug 2014 12:59:43 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Mark Rutland <mark.rutland@....com>
Cc:	Xiubo Li <Li.Xiubo@...escale.com>,
	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	"nicoleotsuka@...il.com" <nicoleotsuka@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCHv2] ASoC: fsl-sai: using 'lsb-first' property instead of
 'big-endian-data'.

On Fri, Aug 29, 2014 at 12:06:01PM +0100, Mark Rutland wrote:
> On Fri, Aug 29, 2014 at 08:12:12AM +0100, Xiubo Li wrote:

> > The 'big-endian-data' property is originally used to indicate whether the
> > LSB firstly or MSB firstly will be transmitted to the CODEC or received
> > from the CODEC, and there has nothing relation to the memory data.

> Both Nicolin [1] and Mark [2] asked for the old property to be kept
> around for compatibility reasons. Those requests seem to have been
> ignored entirely; the commit message doesn't even describe why you
> believe removing support for the old property is safe.

The response was that the relevant chips aren't out in the wild so it's
vanishingly unlikely that anyone would have a real DT with this option
enabled.  I'll defer to Nicolin on if that's the case or not.

Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)