From: Mark Brown <broonie-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
To: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: "alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org"
<alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: ASoC HDMI codec location
Date: Tue, 15 Feb 2011 23:58:33 +0000 [thread overview]
Message-ID: <20110215235832.GB2462@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF03112A51BE-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
On Tue, Feb 15, 2011 at 12:29:59PM -0800, Stephen Warren wrote:
> I see that a Samsung chip has such a codec in drivers/video/sh_mobile_hdmi.c.
That's not Samsung, that's Renesas' SuperH.
> The equivalent for Tegra would be drivers/video/tegra/dc/hdmi.c. Note that
> this location doesn't yet exist upstream. I just wanted to confirm that this
> location makes sense to you, vs. implementing a codec in sound/soc/tegra/hdmi.c,
> and having that call functions exposed by the Tegra dc/hdmi.c driver?
Note that the SH code has code in *both* locations - there's an ASoC
driver that calls into the video driver as well under sound/soc/sh.
> Note that the SPDIF controller isn't involved in the Tegra Digital Audio
> Switch muxing/switching module at all.
Is the DMA shared?
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-02-15 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 20:29 ASoC HDMI codec location Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF03112A51BE-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-02-15 23:58 ` Mark Brown [this message]
[not found] ` <20110215235832.GB2462-yzvPICuk2AATkU/dhu1WVueM+bqZidxxQQ4Iyu8u01E@public.gmane.org>
2011-02-16 16:41 ` Stephen Warren
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF03112A5313-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2011-02-16 16:49 ` 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=20110215235832.GB2462@opensource.wolfsonmicro.com \
--to=broonie-yzvpicuk2aatku/dhu1wvuem+bqzidxxqq4iyu8u01e@public.gmane.org \
--cc=alsa-devel-K7yf7f+aM1XWsZ/bQMPhNw@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
/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