[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D423823.4070009@codeaurora.org>
Date: Thu, 27 Jan 2011 19:29:39 -0800
From: Saravana Kannan <skannan@...eaurora.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Russell King - ARM Linux <linux@....linux.org.uk>,
Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
Vincent Guittot <vincent.guittot@...aro.org>,
linux-sh <linux-sh@...r.kernel.org>,
Ben Herrenschmidt <benh@...nel.crashing.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
linux-kernel <linux-kernel@...r.kernel.org>,
Colin Cross <ccross@...gle.com>,
Ben Dooks <ben-linux@...ff.org>,
Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Jeremy Kerr <jeremy.kerr@...onical.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Richard Zhao <linuxzsc@...il.com>
Subject: Re: Locking in the clk API
On 01/27/2011 01:07 PM, Alan Cox wrote:
>>> For internal tree purposes, does .set_termios need to be atomic? Can it
>>> grab mutexes instead of spinlock?
>>
>> I think I already answered that question above where I said "protect
>> against the interrupt handler accessing the port->* stuff".
>
> I'm not sure you answered it correctly however as the locking nowdays is
> a bit different.
>
> Architecturally the termios handling doesn't need a spin lock nor is it
> called under one. In fact it's vital this is the case because of USB.
Thanks for the clarification Alan. This is what I was looking for.
-Saravana
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists