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:	Mon, 30 May 2016 15:26:13 +0800
From:	Chris Zhong <zyw@...k-chips.com>
To:	Vinod Koul <vinod.koul@...el.com>, Mark Brown <broonie@...nel.org>
Cc:	dianders@...omium.org, tfiga@...omium.org, heiko@...ech.de,
	yzq@...k-chips.com, linux-rockchip@...ts.infradead.org,
	Liam Girdwood <lgirdwood@...il.com>,
	Jaroslav Kysela <perex@...ex.cz>,
	Takashi Iwai <tiwai@...e.com>,
	Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>,
	Michael Trimarchi <michael@...rulasolutions.com>,
	Bard Liao <bardliao@...ltek.com>,
	Adam Thomson <Adam.Thomson.Opensource@...semi.com>,
	anish kumar <yesanishhere@...il.com>,
	Jacob Siverskog <jacob@...nage.engineering>,
	Richard Fitzgerald <rf@...nsource.wolfsonmicro.com>,
	"Damien.Horsley" <Damien.Horsley@...tec.com>,
	Oder Chiou <oder_chiou@...ltek.com>,
	Jyri Sarha <jsarha@...com>, Caesar Wang <wxt@...k-chips.com>,
	linux-kernel@...r.kernel.org, alsa-devel@...a-project.org
Subject: Re: [RESEND PATCH 5/6] ASoC: cdn-dp: Add cdn DP codec driver

Hi Mark & Vinod

Thanks for your suggestion, I am going to use this HDMI codec driver.
But it seems no one use it, currently.

On 05/30/2016 11:33 AM, Vinod Koul wrote:
> On Fri, May 27, 2016 at 09:23:12PM +0100, Mark Brown wrote:
>> On Fri, May 27, 2016 at 06:45:41PM +0800, Chris Zhong wrote:
>>> codec driver get some interfaces from cdn-dp driver, than using those
>>> to set DP audio formats, corresponding to alsa formats.
>> I'm not seeing anything Rockchip specific in here...  DisplayPort is
>> backwards compatible with HDMI, shouldn't this be using the existing
>> hdmi-codec code?
>
> Yup, typically only difference between the two would be programming the
> info frame for DP or HDMI, otherwise it is pretty much same stuff...
>
> They should patch hdmi-codec for that, if that is not supported.
>
> Thanks


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ