From: Lars-Peter Clausen <lars@metafoo.de>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Vinod Koul <vinod.koul@intel.com>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] dma:of: Use a mutex to protect the of_dma_list
Date: Sat, 20 Apr 2013 09:28:19 +0200 [thread overview]
Message-ID: <51724393.1060608@metafoo.de> (raw)
In-Reply-To: <5171C8F6.6010702@ti.com>
On 04/20/2013 12:45 AM, Jon Hunter wrote:
[...]
>> @@ -219,15 +183,15 @@ struct dma_chan *of_dma_request_slave_channel(struct device_node *np,
>> if (of_dma_match_channel(np, name, i, &dma_spec))
>> continue;
>>
>> - ofdma = of_dma_get_controller(&dma_spec);
>> + mutex_lock(&of_dma_lock);
>> + ofdma = of_dma_find_controller(&dma_spec);
>>
>> - if (ofdma) {
>> + if (ofdma)
>> chan = ofdma->of_dma_xlate(&dma_spec, ofdma);
>
> I think that there is a problem here. For controllers using the
> of_dma_simple_xlate(), this will call dma_request_channel() which also
> uses a mutex.
That would only be a problem if it'd use the same mutex. Holding two mutexes at
the same time is not a problem per se.
- Lars
next prev parent reply other threads:[~2013-04-20 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 9:42 [PATCH 1/2] dma: of: Fix of_node reference leak Lars-Peter Clausen
2013-04-19 9:42 ` [PATCH 2/2] dma:of: Use a mutex to protect the of_dma_list Lars-Peter Clausen
2013-04-19 10:13 ` Arnd Bergmann
2013-04-19 11:04 ` Lars-Peter Clausen
2013-04-19 12:25 ` Arnd Bergmann
2013-04-19 22:45 ` Jon Hunter
2013-04-19 23:13 ` Arnd Bergmann
2013-04-22 1:22 ` Jon Hunter
2013-04-20 7:28 ` Lars-Peter Clausen [this message]
2013-04-20 10:38 ` Arnd Bergmann
2013-04-22 1:18 ` Jon Hunter
2013-04-19 10:10 ` [PATCH 1/2] dma: of: Fix of_node reference leak Arnd Bergmann
2013-04-19 22:29 ` Jon Hunter
2013-05-02 16:24 ` Vinod Koul
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=51724393.1060608@metafoo.de \
--to=lars@metafoo.de \
--cc=arnd@arndb.de \
--cc=jon-hunter@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinod.koul@intel.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
Powered by JetHome