From: Timur Tabi <timur@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
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 17:12:16 -0600 [thread overview]
Message-ID: <4786A650.2080107@freescale.com> (raw)
In-Reply-To: <fa686aa40801101502v264d8caw6faf935d71b15c9@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: olof@lixom.net, linuxppc-dev@ozlabs.org,
alsa-devel@alsa-project.org, david@gibson.dropbear.id.au
Subject: Re: [alsa-devel] [PATCH v2] [ALSA] Add ASoC drivers for the Freescale MPC8610 SoC
Date: Thu, 10 Jan 2008 17:12:16 -0600 [thread overview]
Message-ID: <4786A650.2080107@freescale.com> (raw)
In-Reply-To: <fa686aa40801101502v264d8caw6faf935d71b15c9@mail.gmail.com>
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
next prev parent reply other threads:[~2008-01-10 23:13 UTC|newest]
Thread overview: 34+ 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
2008-01-10 23:12 ` Timur Tabi [this message]
2008-01-10 23:12 ` [alsa-devel] " Timur Tabi
2008-01-10 23:17 ` Grant Likely
2008-01-10 23:17 ` [alsa-devel] " Grant Likely
2008-01-10 23:19 ` Timur Tabi
2008-01-10 23:19 ` [alsa-devel] " Timur Tabi
2008-01-11 0:24 ` Olof Johansson
2008-01-11 0:24 ` [alsa-devel] " Olof Johansson
2008-01-11 15:08 ` Timur Tabi
2008-01-11 15:08 ` [alsa-devel] " 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-11 16:39 ` Timur Tabi
2008-01-11 16:44 ` Takashi Iwai
2008-01-11 17:07 ` Timur Tabi
2008-01-11 17:12 ` Takashi Iwai
2008-01-11 17:16 ` Timur Tabi
2008-01-11 17:20 ` Takashi Iwai
2008-01-11 17:23 ` Jaroslav Kysela
2008-01-12 13:40 ` Mark Brown
2008-01-18 6:48 ` Kumar Gala
2008-01-18 14:48 ` Timur Tabi
2008-01-18 14:48 ` [alsa-devel] " Timur Tabi
2008-01-18 15:18 ` Kumar Gala
2008-01-18 15:18 ` [alsa-devel] " Kumar Gala
2008-01-18 15:40 ` Takashi Iwai
2008-01-18 15:40 ` [alsa-devel] " 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
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=4786A650.2080107@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=david@gibson.dropbear.id.au \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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.