From: Jarkko Nikula <jarkko.nikula@nokia.com>
To: ext Tony Lindgren <tony@atomide.com>
Cc: "Hunter, Jon" <jon-hunter@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAP5912: Fix omap5912 osk alsa driver [1/2]
Date: Thu, 14 Aug 2008 09:13:29 +0300 [thread overview]
Message-ID: <20080814091329.bcb2755e.jarkko.nikula@nokia.com> (raw)
In-Reply-To: <20080813135721.GC27446@atomide.com>
On Wed, 13 Aug 2008 16:57:25 +0300
"ext Tony Lindgren" <tony@atomide.com> wrote:
> * Hunter, Jon <jon-hunter@ti.com> [080813 06:08]:
> > Move OMAP_MCBSP_READ and OMAP_MCBSP_WRITE macro definitions from
> > arch/arm/plat-omap/mcbsp.c to include/asm-arm/arch-omap/mcbsp.h.
>
> Let's rather get rid of the direct mcbsp register tinkering from
> drivers and use following instead:
>
Workaround for omap_mcbsp3_aic23_clock_init not adding new McBSP API
would be to put those registers into "struct omap_mcbsp_reg_cfg" and
call omap_mcbsp_config.
> And, really the best solution would be to add support to
> sound/soc/omap/ for various codecs rather than try to keep
> the old drivers working.
>
I propose this as well. Luckily it seems that someone is already
developing ASoC driver for TLV320AIC23B. Then native ALSA SoC support
for OSK require only to develope new machine driver in sound/soc/omap/.
http://mailman.alsa-project.org/pipermail/alsa-devel/2008-August/009826.html
I'm also curious to know how well my OMAP ASoC drivers work on
OMAP1's :-)
Jarkko
next prev parent reply other threads:[~2008-08-14 6:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 3:07 [PATCH] OMAP5912: Fix omap5912 osk alsa driver [1/2] Hunter, Jon
2008-08-13 13:57 ` Tony Lindgren
2008-08-14 6:13 ` Jarkko Nikula [this message]
2008-08-14 15:09 ` Hunter, Jon
2008-08-15 8:12 ` Jarkko Nikula
2008-08-18 15:14 ` Hunter, Jon
2008-08-19 21:11 ` Yuri Jaeger Monti
2008-09-01 14:41 ` Yuri Jaeger Monti
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=20080814091329.bcb2755e.jarkko.nikula@nokia.com \
--to=jarkko.nikula@nokia.com \
--cc=jon-hunter@ti.com \
--cc=linux-omap@vger.kernel.org \
--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