From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: IGEPv2 audio problem
Date: Mon, 17 Jun 2013 00:34:12 -0700 [thread overview]
Message-ID: <20130617073411.GD4465@atomide.com> (raw)
In-Reply-To: <51BDAD7F.8090303@collabora.co.uk>
* Javier Martinez Canillas <javier.martinez@collabora.co.uk> [130616 05:26]:
>
> I can take a look to this but I don't know if Tony is still accepting bugfixes
> for board files.
Critical fixes yes, but let's plan on making omap3 also DT only for v3.12
merge window. With the patches posted recently I've verified that ret-idle
and off-idle work for omap3. So only board related device configuration and
some driver work remains. And we can of course still initialize some platform
data too where needed.
> twl4030 based audio should already work with DT as far as I know.
Yes I think so.
Regards,
Tony
prev parent reply other threads:[~2013-06-17 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130616135208.3f124c2c@skate>
2013-06-16 12:20 ` IGEPv2 audio problem Javier Martinez Canillas
2013-06-16 13:34 ` Thomas Petazzoni
2013-06-16 15:43 ` Javier Martinez Canillas
2013-06-16 16:10 ` Thomas Petazzoni
2013-06-17 7:40 ` Tony Lindgren
2013-06-17 7:34 ` Tony Lindgren [this message]
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=20130617073411.GD4465@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).