Re: [alsa-devel] [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC
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 ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [alsa-devel] [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC
Grant Likely wrote: 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. I don't have any more protection than any other driver that accesses SOC registers directly. Last I heard, Zhang's DMA driver was in limbo, and that driver would be the best place to arbitrate DMA register access. I was planning on adding arbitration support to that driver after both drivers were applied. As for the GUTS driver, well, I just program a few registers at startup, and I don't think any other driver touches them. -- Timur Tabi Linux kernel developer at Freescale ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [alsa-devel] [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC
On 1/10/08, Timur Tabi [EMAIL PROTECTED] wrote: Grant Likely wrote: 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. I don't have any more protection than any other driver that accesses SOC registers directly. Last I heard, Zhang's DMA driver was in limbo, and that driver would be the best place to arbitrate DMA register access. I was planning on adding arbitration support to that driver after both drivers were applied. That sounds appropriate As for the GUTS driver, well, I just program a few registers at startup, and I don't think any other driver touches them. Okay; at some point in the future they'll need to be accessed from a common routine too. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
Re: [alsa-devel] [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC
Grant Likely wrote: As for the GUTS driver, well, I just program a few registers at startup, and I don't think any other driver touches them. Okay; at some point in the future they'll need to be accessed from a common routine too. I'll add that to my to-do list. -- Timur Tabi Linux kernel developer at Freescale ___ Linuxppc-dev mailing list Linuxppc-dev@ozlabs.org https://ozlabs.org/mailman/listinfo/linuxppc-dev
