From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
Timur Tabi <timur@freescale.com>,
lrg@slimlogic.co.uk
Subject: Re: [PATCH 1/2] powerpc/8610: add probing for individual DMA channels, not just DMA controllers
Date: Wed, 5 May 2010 12:22:08 +0100 [thread overview]
Message-ID: <20100505112208.GD5754@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <2928D88F-057B-498C-8A11-F7193429A90D@freescale.com>
On Tue, May 04, 2010 at 12:20:13PM -0500, Kumar Gala wrote:
> On May 3, 2010, at 4:54 PM, Timur Tabi wrote:
> > A future version of the MPC8610 HPCD's ASoC DMA driver will probe on individual
> > DMA channel nodes, so the DMA controller nodes' compatible string must be listed
> > in mpc8610_ids[] for the probe to work.
> >
> > Also remove the "gianfar" compatible from mpc8610_ids[], since there is no
> > gianfar (or any other networking device) on the 8610.
> >
> > Signed-off-by: Timur Tabi <timur@freescale.com>
> Acked-by: Kumar Gala <galak@kernel.crashing.org>
Just looking at the scheduling here with regard to the merge window and
the fact that this doesn't seem to hurt the existing drivers perhaps it
makes sense to merge this via the PowerPC tree immediately?
next prev parent reply other threads:[~2010-05-05 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 21:54 [PATCH 1/2] powerpc/8610: add probing for individual DMA channels, not just DMA controllers Timur Tabi
2010-05-04 14:54 ` Mark Brown
2010-05-04 15:11 ` Timur Tabi
2010-05-04 19:22 ` [alsa-devel] " Mark Brown
2010-05-04 17:20 ` Kumar Gala
2010-05-05 11:22 ` Mark Brown [this message]
2010-05-05 11:39 ` [alsa-devel] " Timur Tabi
2010-05-05 12:35 ` Mark Brown
2010-05-05 15:59 ` Timur Tabi
2010-05-17 15:55 ` Kumar Gala
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=20100505112208.GD5754@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=lrg@slimlogic.co.uk \
--cc=timur@freescale.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).