From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
alsa-devel@alsa-project.org, Ralf Baechle <ralf@linux-mips.org>,
Manuel Lauss <manuel.lauss@gmail.com>
Subject: Re: [PATCH 4/7] Alchemy: DB1200 AC97+I2S audio support.
Date: Mon, 8 Jun 2009 13:44:11 +0100 [thread overview]
Message-ID: <20090608124411.GA3396@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <f861ec6f0906080521y4443b888gb81a78305dfca5e2@mail.gmail.com>
On Mon, Jun 08, 2009 at 02:21:18PM +0200, Manuel Lauss wrote:
> I see now what you mean, but this is ugly as sin:
> I now need to register 2 platform devices in the board code: 1 for the DAI
> (with resources mmio + irq) and 1 for the DMA engine (with ddma id resources),
> or register the DMA engine device from within the AC97/I2S drivers.
> This is in my opinion even worse than the current scheme, which at least allows
> me to group all PSC resources into one struct resource which all audio-related
> drivers can share without too much uglyness.
If you trigger registration the DMA engine from within the I2S and AC97
devices you can still group everything together like you want to so I
don't really see the problem - they're peering at a different device for
the data but other than that things are unchanged. At the minute you're
loosing a lot of sharing by having this in the individual machine
drivers.
Note that one of the possibilities once multiple sound card support is
introduced is that DAIs could be shared between multiple cards. This is
only going to be at all useful for CPU DAIs which allow separate
configuration of the RX and TX paths and will never be the common case
but it's something to bear in mind.
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Manuel Lauss <manuel.lauss@googlemail.com>
Cc: Linux-MIPS <linux-mips@linux-mips.org>,
Ralf Baechle <ralf@linux-mips.org>,
Manuel Lauss <manuel.lauss@gmail.com>,
alsa-devel@alsa-project.org
Subject: Re: [alsa-devel] [PATCH 4/7] Alchemy: DB1200 AC97+I2S audio support.
Date: Mon, 8 Jun 2009 13:44:11 +0100 [thread overview]
Message-ID: <20090608124411.GA3396@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <f861ec6f0906080521y4443b888gb81a78305dfca5e2@mail.gmail.com>
On Mon, Jun 08, 2009 at 02:21:18PM +0200, Manuel Lauss wrote:
> I see now what you mean, but this is ugly as sin:
> I now need to register 2 platform devices in the board code: 1 for the DAI
> (with resources mmio + irq) and 1 for the DMA engine (with ddma id resources),
> or register the DMA engine device from within the AC97/I2S drivers.
> This is in my opinion even worse than the current scheme, which at least allows
> me to group all PSC resources into one struct resource which all audio-related
> drivers can share without too much uglyness.
If you trigger registration the DMA engine from within the I2S and AC97
devices you can still group everything together like you want to so I
don't really see the problem - they're peering at a different device for
the data but other than that things are unchanged. At the minute you're
loosing a lot of sharing by having this in the individual machine
drivers.
Note that one of the possibilities once multiple sound card support is
introduced is that DAIs could be shared between multiple cards. This is
only going to be at all useful for CPU DAIs which allow separate
configuration of the RX and TX paths and will never be the common case
but it's something to bear in mind.
next prev parent reply other threads:[~2009-06-08 12:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 18:38 [PATCH 0/7] Alchemy: core and platform updates v2 Manuel Lauss
2009-06-07 18:38 ` [PATCH 1/7] Alchemy: prioritize timer and usb irqs Manuel Lauss
2009-06-07 18:38 ` [PATCH 2/7] Alchemy: get rid of allow_au1k_wait Manuel Lauss
2009-06-07 18:39 ` [PATCH 3/7] Alchemy: extended DB1200 board support Manuel Lauss
2009-06-07 18:39 ` [PATCH 4/7] Alchemy: DB1200 AC97+I2S audio support Manuel Lauss
2009-06-07 18:39 ` [PATCH 5/7] Alchemy: new PCMCIA socket driver for devboards Manuel Lauss
2009-06-07 18:39 ` [PATCH 6/7] Alchemy: convert to physmap flash Manuel Lauss
2009-06-07 18:39 ` [PATCH 7/7] Alchemy: db1200 defconfig update Manuel Lauss
2009-06-08 9:25 ` [PATCH 4/7] Alchemy: DB1200 AC97+I2S audio support Mark Brown
2009-06-08 9:25 ` [alsa-devel] " Mark Brown
2009-06-08 9:43 ` Manuel Lauss
2009-06-08 10:20 ` Mark Brown
2009-06-08 10:20 ` [alsa-devel] " Mark Brown
2009-06-08 11:25 ` Manuel Lauss
2009-06-08 11:53 ` Mark Brown
2009-06-08 11:53 ` [alsa-devel] " Mark Brown
2009-06-08 12:21 ` Manuel Lauss
2009-06-08 12:44 ` Mark Brown [this message]
2009-06-08 12:44 ` Mark Brown
2009-06-08 13:11 ` Manuel Lauss
2009-06-08 13:45 ` Mark Brown
2009-06-08 13:45 ` [alsa-devel] " Mark Brown
2009-06-08 14:48 ` Manuel Lauss
2009-06-08 15:24 ` Mark Brown
2009-06-08 15:42 ` Manuel Lauss
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=20090608124411.GA3396@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-mips@linux-mips.org \
--cc=manuel.lauss@gmail.com \
--cc=manuel.lauss@googlemail.com \
--cc=ralf@linux-mips.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.