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 DMAcontroller. */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.