From: Timur Tabi <timur@freescale.com>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, alsa-devel@alsa-project.org,
david@gibson.dropbear.id.au
Subject: Re: [alsa-devel] [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC
Date: Fri, 11 Jan 2008 09:08:36 -0600 [thread overview]
Message-ID: <47878674.7010705@freescale.com> (raw)
In-Reply-To: <20080111002450.GA13291@lixom.net>
Olof Johansson wrote:
> Having been in a similar situation myself (needing to share resources
> between DMA, ethernet and function offload), I recommend creating a
> separate small library that all those drivers use, instead of making
> some sort of dependency between drivers in completely different parts
> of the kernel.
Well, the DMA driver should be in soon. Actually, it should be in now, because
I saw a blurb in this month's Linux Journal about it. As soon as I find it :-),
I'll post a new patch that adds arbitration.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-01-11 15:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-10 22:44 [PATCH 0/2] ASoC drivers for the Freescale MPC8610 SoC Timur Tabi
2008-01-10 22:44 ` [PATCH v3] [POWERPC] Update MPC8610 HPCD to support audio drivers Timur Tabi
2008-01-10 22:44 ` [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC Timur Tabi
2008-01-10 23:02 ` Grant Likely
2008-01-10 23:12 ` [alsa-devel] " Timur Tabi
2008-01-10 23:17 ` Grant Likely
2008-01-10 23:19 ` Timur Tabi
2008-01-11 0:24 ` Olof Johansson
2008-01-11 15:08 ` Timur Tabi [this message]
2008-01-10 22:52 ` [PATCH v3] [POWERPC] Update MPC8610 HPCD to support audio drivers Grant Likely
2008-01-10 23:00 ` Scott Wood
2008-01-18 6:48 ` Kumar Gala
2008-01-18 14:48 ` [alsa-devel] " Timur Tabi
2008-01-18 15:18 ` Kumar Gala
2008-01-18 15:40 ` Takashi Iwai
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=47878674.7010705@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).