linux-kernel - RE: [PATCH 1/2] ASoC: fsl-spdif: big-endian 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: <1a10273e564a4bb7a5aafe3f01ccffa2@BY2PR03MB505.namprd03.prod.outlook.com>
Date:	Tue, 11 Feb 2014 07:39:44 +0000
From:	"Li.Xiubo@...escale.com" <Li.Xiubo@...escale.com>
To:	"guangyu.chen@...escale.com" <guangyu.chen@...escale.com>,
	"shawn.guo@...aro.org" <shawn.guo@...aro.org>
CC:	"broonie@...nel.org" <broonie@...nel.org>,
	"lgirdwood@...il.com" <lgirdwood@...il.com>,
	"perex@...ex.cz" <perex@...ex.cz>, "tiwai@...e.de" <tiwai@...e.de>,
	"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 1/2] ASoC: fsl-spdif: big-endian support



> > +   - big-endian : If this property is absent, the native endian mode will
> > +   be in use as default, or the big endian mode will be in use for all the
> > +   device registers.
> > +
> 
> @Shawn
> Does DT have an existing approach to determine if the current SoC this IP
> uses is BE or LE? I am thinking the scenario that if all drivers support
> BE/LE while the SoC is big-endian, all the nodes in the DT would have to
> include a duplicated property (big-endian).
> 

@Nicolin, @Shawn
One special scenario likes the LS1 platform, the CPU and a few devices are in
LE mode and other devices will be in BE mode.

Thanks,

--
Best Regards,
Xiubo
--
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/