[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <54CA1A12.5080507@ti.com>
Date: Thu, 29 Jan 2015 13:31:30 +0200
From: Roger Quadros <rogerq@...com>
To: Tony Lindgren <tony@...mide.com>
CC: Chanwoo Choi <cw00.choi@...sung.com>, Felipe Balbi <balbi@...com>,
"myungjoo.ham@...sung.com" <myungjoo.ham@...sung.com>,
<george.cherian@...com>, <nsekhar@...com>,
devicetree <devicetree@...r.kernel.org>,
<linux-usb@...r.kernel.org>, <linux-omap@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/7] extcon: usb-gpio: Introduce gpio usb extcon driver
On 28/01/15 19:09, Tony Lindgren wrote:
> * Roger Quadros <rogerq@...com> [150128 04:15]:
>> On 28/01/15 04:19, Chanwoo Choi wrote:
>>>>
>>>> I still fail to understand that we need to call disable_irq() in .suspend() and
>>>> enable_irq() in .resume()
>>>>
>>>> can you point me to any other drivers doing so?
>>>
>>> You can refer the suspend function in drivers/mfd/max14577.c or drivers/mfd/max77693.c.
>>> The max14577_suspend() includes the detailed comment for why using disable_irq() in suspend function.
>>>
>>> In max14577 case, max14577_suspend() use disable_irq() function because of i2c dependency.
>>> If max14577 device is wake-up from suspend state before completing the resume sequence
>>> of i2c, max14577 may fail to read/write i2c communication.
>>
>> Thanks for this information. I will add disable/enable_irq() in suspend/resume().
>
> Are the .dts changes safe for me to apply already?
>
Yes Tony, you can pick them. Thanks.
cheers,
-roger
--
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