From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Ricardo Neri <ricardo.neri@ti.com>,
tony@atomide.com, lrg@ti.com, s-guiriec@ti.com,
linux-omap@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH v2 2/2] ARM: OMAP4+: HDMI: Rearrange platform devices for ASoC drivers
Date: Fri, 23 Nov 2012 11:03:06 +0900 [thread overview]
Message-ID: <20121123020305.GI4385@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50AE2022.8080607@ti.com>
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
On Thu, Nov 22, 2012 at 02:52:50PM +0200, Tomi Valkeinen wrote:
> Or is there something in ASoC that forces us to represent it in the
> .dts? I don't think there's really anything related to HW to describe
There shouldn't be.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-23 2:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 1:36 [PATCH v2 0/2] ARM: OMAP2+: HDMI: Update platform devices for audio Ricardo Neri
2012-11-16 1:36 ` [PATCH v2 1/2] ARM: OMAP2+: HDMI: Relocate audio platform device creation Ricardo Neri
2012-11-16 2:04 ` Mark Brown
2012-11-16 7:38 ` Tomi Valkeinen
2012-11-16 17:14 ` Ricardo Neri
2012-11-16 1:36 ` [PATCH v2 2/2] ARM: OMAP4+: HDMI: Rearrange platform devices for ASoC drivers Ricardo Neri
2012-11-16 2:05 ` Mark Brown
2012-11-16 7:52 ` Tomi Valkeinen
2012-11-16 18:05 ` Ricardo Neri
2012-11-19 12:58 ` Tomi Valkeinen
2012-11-20 1:15 ` Mark Brown
2012-11-22 0:20 ` Ricardo Neri
2012-11-22 1:03 ` Mark Brown
2012-11-23 2:03 ` Ricardo Neri
2012-11-23 2:12 ` Mark Brown
2012-11-23 20:14 ` Ricardo Neri
2012-11-22 12:52 ` Tomi Valkeinen
2012-11-23 2:03 ` Mark Brown [this message]
2012-11-23 2:12 ` Ricardo Neri
2012-11-22 0:19 ` 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=20121123020305.GI4385@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=ricardo.neri@ti.com \
--cc=s-guiriec@ti.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.