From: Ricardo Neri <ricardo.neri@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Tomi Valkeinen <tomi.valkeinen@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 14:14:25 -0600 [thread overview]
Message-ID: <50AFD921.1020205@ti.com> (raw)
In-Reply-To: <20121123021211.GL4385@opensource.wolfsonmicro.com>
On 11/22/2012 08:12 PM, Mark Brown wrote:
> On Thu, Nov 22, 2012 at 08:03:53PM -0600, Ricardo Neri wrote:
>> On 11/21/2012 07:03 PM, Mark Brown wrote:
>
>>> instantiation infrastructure in there which is rather Linux specific.
>
>> But the board files are only for Linux, right? The ASoC drivers will
>> always be initialized anyways. They will reach probe only if the
>> devices are present.
>
> Could you be more specific please?
>
Sorry, I meant that the drivers will try to register anyways. The will
only probe if there is a matching device for them.
next prev parent reply other threads:[~2012-11-23 20:15 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 [this message]
2012-11-22 12:52 ` Tomi Valkeinen
2012-11-23 2:03 ` Mark Brown
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=50AFD921.1020205@ti.com \
--to=ricardo.neri@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@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 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).