From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Timur Tabi" <timur@freescale.com>
Cc: olof@lixom.net, linuxppc-dev@ozlabs.org,
alsa-devel@alsa-project.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC
Date: Thu, 10 Jan 2008 16:02:10 -0700 [thread overview]
Message-ID: <fa686aa40801101502v264d8caw6faf935d71b15c9@mail.gmail.com> (raw)
In-Reply-To: <12000050682718-git-send-email-timur@freescale.com>
On 1/10/08, Timur Tabi <timur@freescale.com> wrote:
> Add the ASoC drivers for the Freescale MPC8610 SoC and the MPC8610 HPCD
> reference board.
>
> Signed-off-by: Timur Tabi <timur@freescale.com>
This is a very big patch, but I'm going to keep my nose out of the
ALSA stuff. I've got no problem against it being merged, but I do
have a concern about access to shared registers (see below)
> diff --git a/sound/soc/fsl/mpc8610_hpcd.c b/sound/soc/fsl/mpc8610_hpcd.c
> new file mode 100644
> index 0000000..f26c4b2
> --- /dev/null
> +++ b/sound/soc/fsl/mpc8610_hpcd.c
> +/**
> + * mpc8610_hpcd_probe: OF probe function for the fabric driver
> + *
> + * This function gets called when an SSI node is found in the device tree.
> + *
> + * Although this is a fabric driver, the SSI node is the "master" node with
> + * respect to audio hardware connections. Therefore, we create a new ASoC
> + * device for each new SSI node that has a codec attached.
> + *
> + * FIXME: Currently, we only support one DMA controller, so if there are
> + * multiple SSI nodes with codecs, only the first will be supported.
> + *
> + * FIXME: Even if we did support multiple DMA controllers, we have no
> + * mechanism for assigning DMA controllers and channels to the individual
> + * SSI devices. We also probably aren't compatible with the generic Elo DMA
> + * device driver.
> + */
> +static int mpc8610_hpcd_probe(struct of_device *ofdev,
> + const struct of_device_id *match)
> +{
<snip>
> + /* Map the global utilities registers. */
> + guts_np = of_find_compatible_node(NULL, NULL, "fsl,mpc8610-guts");
> + if (!guts_np) {
> + dev_err(&ofdev->dev, "could not obtain address of GUTS\n");
> + ret = -EINVAL;
> + goto error;
> + }
This...
> + /* Find the DMA channels to use. For now, we always use the first DMA
> + controller. */
> + for_each_compatible_node(dma_np, NULL, "fsl,mpc8610-dma") {
> + iprop = of_get_property(dma_np, "cell-index", NULL);
> + if (iprop && (*iprop == 0)) {
> + of_node_put(dma_np);
> + break;
> + }
> + }
and this...
Does the driver access the DMA and GUTS registers directly? If so,
what do you have to protect against race conditions of other drivers
accessing them also.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-01-10 23:02 UTC|newest]
Thread overview: 17+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2008-01-07 18:56 [PATCH 0/2] ASoC drivers for the Freescale MPC8610 SoC Timur Tabi
2008-01-07 18:56 ` [PATCH v2] [POWERPC] Update MPC8610 HPCD to support audio drivers Timur Tabi
2008-01-07 18:56 ` [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC Timur Tabi
2008-01-08 16:20 ` Liam Girdwood
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=fa686aa40801101502v264d8caw6faf935d71b15c9@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=alsa-devel@alsa-project.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--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).