linux-mips
[Top] [All Lists]

Re: [alsa-devel] [PATCH] ASoC: Add TXx9 AC link controller driver

To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Subject: Re: [alsa-devel] [PATCH] ASoC: Add TXx9 AC link controller driver
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
Date: Fri, 15 May 2009 20:05:58 +0100
Cc: linux-mips@linux-mips.org, alsa-devel@alsa-project.org, ralf@linux-mips.org
In-reply-to: <20090516.001202.173372394.anemo@mba.ocn.ne.jp>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1242312605-2160-1-git-send-email-anemo@mba.ocn.ne.jp> <20090514185945.GO28291@sirena.org.uk> <20090516.001202.173372394.anemo@mba.ocn.ne.jp>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, May 16, 2009 at 12:12:02AM +0900, Atsushi Nemoto wrote:

> OK, then I will move irq/mem resource stuff to the DAI driver and dma
> resource stuff to the DMA driver.

Either is fine - do whatever makes most sense for your system.

> OTOH, I want to keep arch code as is.  There are some TXx9 SoC
> variations and they can have different baseaddr/irq/dma.  I want to
> leave these details in arch code and make ASoC drivers generic as
> possible.

This is the common situation for SoC CPUs - most silicon vendors reuse
the same IPs in diffierent combinations on different CPUs.  The normal
approach is to have the generic code for each SoC set up the resources
for the devices that are present on that particular SoC.  This avoids
the need for each board using the SoC to have to replicate the
information.

<Prev in Thread] Current Thread [Next in Thread>