From: Jyri Sarha <jsarha@ti.com>
To: Chris Zhong <zyw@rock-chips.com>,
Vinod Koul <vinod.koul@intel.com>,
Mark Brown <broonie@kernel.org>, <linux-kernel@vger.kernel.org>,
<alsa-devel@alsa-project.org>
Cc: <dianders@chromium.org>, <tfiga@chromium.org>, <heiko@sntech.de>,
<yzq@rock-chips.com>, <linux-rockchip@lists.infradead.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
Michael Trimarchi <michael@amarulasolutions.com>,
Bard Liao <bardliao@realtek.com>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
anish kumar <yesanishhere@gmail.com>,
Jacob Siverskog <jacob@teenage.engineering>,
Richard Fitzgerald <rf@opensource.wolfsonmicro.com>,
"Damien.Horsley" <Damien.Horsley@imgtec.com>,
Oder Chiou <oder_chiou@realtek.com>,
Caesar Wang <wxt@rock-chips.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>
Subject: Re: [RESEND PATCH 5/6] ASoC: cdn-dp: Add cdn DP codec driver
Date: Mon, 30 May 2016 10:47:52 +0300 [thread overview]
Message-ID: <574BF028.70102@ti.com> (raw)
In-Reply-To: <574BEB15.20704@rock-chips.com>
On 05/30/16 10:26, Chris Zhong wrote:
> Hi Mark & Vinod
>
> Thanks for your suggestion, I am going to use this HDMI codec driver.
> But it seems no one use it, currently.
>
There is three users working on getting their code accepted in main
line. I have been trying to get my tda998x patches reviewed for some
time now, but not lately, because I have been busy with my other tasks.
The two others are Philipp Zabel and Arnaud Pouliquen, both in cc. Not
sure if they actually have some patches already queued for mainline.
Best regards,
Jyri
> 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
>
>
next prev parent reply other threads:[~2016-05-30 7:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 10:45 [RESEND PATCH 0/6] Rockchip Type-C and DispplayPort driver Chris Zhong
2016-05-27 10:45 ` [RESEND PATCH 1/6] phy: Add USB Type-C PHY driver for rk3399 Chris Zhong
2016-05-27 10:45 ` [RESEND PATCH 2/6] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY Chris Zhong
2016-06-01 14:54 ` Rob Herring
2016-06-01 15:35 ` Chris Zhong
2016-05-27 10:45 ` [RESEND PATCH 3/6] drm/rockchip: vop: add cdn DP support for rk3399 Chris Zhong
2016-05-27 10:45 ` [RESEND PATCH 4/6] Documentation: bindings: add dt documentation for cdn DP controller Chris Zhong
2016-06-01 14:56 ` Rob Herring
2016-05-27 10:45 ` [RESEND PATCH 5/6] ASoC: cdn-dp: Add cdn DP codec driver Chris Zhong
2016-05-27 20:23 ` Mark Brown
2016-05-30 3:33 ` Vinod Koul
2016-05-30 7:26 ` Chris Zhong
2016-05-30 7:47 ` Jyri Sarha [this message]
2016-05-30 12:26 ` Arnaud Pouliquen
2016-05-27 10:45 ` [RESEND PATCH 6/6] ASoC: rockchip: Add machine driver for cdn dp codec Chris Zhong
2016-06-01 14:57 ` Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=574BF028.70102@ti.com \
--to=jsarha@ti.com \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=Damien.Horsley@imgtec.com \
--cc=alsa-devel@alsa-project.org \
--cc=arnaud.pouliquen@st.com \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=jacob@teenage.engineering \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael@amarulasolutions.com \
--cc=oder_chiou@realtek.com \
--cc=p.zabel@pengutronix.de \
--cc=perex@perex.cz \
--cc=rf@opensource.wolfsonmicro.com \
--cc=tfiga@chromium.org \
--cc=tiwai@suse.com \
--cc=vinod.koul@intel.com \
--cc=wxt@rock-chips.com \
--cc=yesanishhere@gmail.com \
--cc=yzq@rock-chips.com \
--cc=zyw@rock-chips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).