From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ricardo Neri <ricardo.neri@ti.com>
Cc: "K, Mythri P" <mythripk@ti.com>,
tomi.valkeinen@ti.com, linux-omap@vger.kernel.org,
s-guiriec@ti.com, lrg@ti.com, peter.ujfalusi@ti.com
Subject: Re: [PATCH 0/4] OMAPDSS/ASoC: Repair broken HDMI audio in K3.2-rcX
Date: Thu, 12 Jan 2012 02:59:35 +0000 [thread overview]
Message-ID: <20120112025933.GA22775@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1326249881.1938.202.camel@dexx0075479.dextra-mty.naucm.ext.ti.com>
On Tue, Jan 10, 2012 at 08:44:41PM -0600, Ricardo Neri wrote:
> The approach that I am planning to follow is to move the ASOC HDMI OMAP4
> codec to the sound directory and leave all the IP-specific functions
> (e.g., to set registers) in the video directory. The audio code should
> be generic in the sense that it does not change an IP register directly.
> This is to follow a similar approach as that followed by DSS in which
> all IP-specific code is separated from DSS code. Also, it makes more
> sense to me to have the ASoC codec under sound/soc/codecs.
Depending on how abstract that interface is it may be better to make it
into something more cross platform than just an OMAP thing - if you're
talking about not having any knowledge of the registers or anything then
it seems like that should be possible. It would preclude the use of
something OMAP specific like DSS though.
next prev parent reply other threads:[~2012-01-12 2:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 7:03 [PATCH 0/4] OMAPDSS/ASoC: Repair broken HDMI audio in K3.2-rcX Ricardo Neri
2011-12-16 7:03 ` [PATCH 1/4] ASoC: OMAP: HDMI: Introduce driver data for audio codec Ricardo Neri
2011-12-16 7:03 ` [PATCH 2/4] ASoC: OMAP: HDMI: Correct signature of ASoC functions Ricardo Neri
2011-12-16 7:03 ` [PATCH 3/4] OMAPDSS: HDMI: Create function to enable HDMI audio Ricardo Neri
2011-12-16 7:03 ` [PATCH 4/4] ASoC: OMAP: HDMI: Move HDMI codec trigger function to generic HDMI driver Ricardo Neri
2011-12-19 8:12 ` Tomi Valkeinen
2011-12-29 9:56 ` [PATCH 0/4] OMAPDSS/ASoC: Repair broken HDMI audio in K3.2-rcX K, Mythri P
2011-12-29 18:48 ` Mark Brown
2012-01-03 5:57 ` Ricardo Neri
2012-01-03 20:09 ` Mark Brown
2012-01-11 2:44 ` Ricardo Neri
2012-01-12 2:59 ` Mark Brown [this message]
2012-01-13 2:23 ` Ricardo Neri
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=20120112025933.GA22775@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mythripk@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@ti.com \
--cc=tomi.valkeinen@ti.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).