public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Mark Brown <broonie@sirena.org.uk>
Cc: arunks@mistralsolutions.com, alsa-devel@alsa-project.org,
	linux-omap@vger.kernel.org, steve@sakoman.com
Subject: Re: [alsa-devel] [PATCH] ASoC: Fix TW4030 Kconfig dependency
Date: Tue, 25 Nov 2008 12:14:53 -0800	[thread overview]
Message-ID: <200811251214.54155.david-b@pacbell.net> (raw)
In-Reply-To: <20081125200411.GA6572@sirena.org.uk>

On Tuesday 25 November 2008, Mark Brown wrote:
> BTW, it'd also be really handy if you could remove the OMAP dependencies
> from TWL4030_CORE - I know it currently needs them to actually be useful
> at runtime but it'd mean that it's possible to build things like the
> codec driver on other configs which helps when working on subsystems.

Patches for that are ready, but need a bit more testing
in the OMAP tree before they go to mainline.  I may prep
the mainline patches anyway ... the patches are roughly

 - updates to twl4030-core device creation, which
   are now in the OMAP tree, passing more IRQs via
   platform_device resources;

 - updates to various TWL drivers that won't go to
   mainline for a while, so they get the IRQs from
   those new resources;

 - removing the global IRQ symbols from the headers,
   and thus the OMAP dependencies.

The need for testing is from that second set of
patches.  There's also regulator framework stuff.

- Dave

      reply	other threads:[~2008-11-25 20:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  4:26 [PATCH] ASoC: Fix TW4030 Kconfig dependency arunks
2008-11-25  4:44 ` David Brownell
2008-11-25 15:30   ` Mark Brown
2008-11-25 18:54     ` [alsa-devel] " David Brownell
2008-11-25 20:04       ` Mark Brown
2008-11-25 20:14         ` David Brownell [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=200811251214.54155.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=alsa-devel@alsa-project.org \
    --cc=arunks@mistralsolutions.com \
    --cc=broonie@sirena.org.uk \
    --cc=linux-omap@vger.kernel.org \
    --cc=steve@sakoman.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