From: Mark Brown <broonie@kernel.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: alsa-devel@alsa-project.org, Koro Chen <koro.chen@mediatek.com>,
Daniel Kurtz <djkurtz@chromium.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-mediatek@lists.infradead.org, kernel@pengutronix.de,
Matthias Brugger <matthias.bgg@gmail.com>,
Cawa Cheng <cawa.cheng@mediatek.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC] ASoC: Add mediatek HDMI codec driver
Date: Wed, 4 Nov 2015 12:03:43 +0000 [thread overview]
Message-ID: <20151104120343.GZ20228@sirena.org.uk> (raw)
In-Reply-To: <1446638053-12143-1-git-send-email-p.zabel@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 670 bytes --]
On Wed, Nov 04, 2015 at 12:54:13PM +0100, Philipp Zabel wrote:
> This driver is based on the work of DW HDMI codec driver.
> It controls mediatek HDMI Tx's audio module, and handles
> HDMI jack detection by sharing IRQ with HDMI Tx.
How does this relate to all the other HDMI related work that's going on,
especially around handling of the EDID data? I'm not seeing anything in
here that uses the constraints code that Russell added for example. As
I keep saying I really want to see some collaboration and consensus here
with the goal of sharing code and achieving a consistent userspace
interface rather than a lot of individual independently implemented
drivers.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-11-04 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-04 11:54 [RFC] ASoC: Add mediatek HDMI codec driver Philipp Zabel
2015-11-04 12:03 ` Mark Brown [this message]
2015-11-05 15:15 ` Philipp Zabel
2015-11-05 15:52 ` Mark Brown
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=20151104120343.GZ20228@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=cawa.cheng@mediatek.com \
--cc=djkurtz@chromium.org \
--cc=kernel@pengutronix.de \
--cc=koro.chen@mediatek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=p.zabel@pengutronix.de \
/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