[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date: Mon, 12 Dec 2016 10:59:51 +0100
From: Amelie DELAUNAY <amelie.delaunay@...com>
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
CC: Mathieu Poirier <mathieu.poirier@...aro.org>,
"a.zummo@...ertech.it" <a.zummo@...ertech.it>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"mcoquelin.stm32@...il.com" <mcoquelin.stm32@...il.com>,
Alexandre TORGUE <alexandre.torgue@...com>,
"linux@...linux.org.uk" <linux@...linux.org.uk>,
"rtc-linux@...glegroups.com" <rtc-linux@...glegroups.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Gabriel FERNANDEZ <gabriel.fernandez@...com>
Subject: Re: [PATCH 3/8] rtc: add STM32 RTC driver
Hi Alexandre,
On 12/07/2016 07:37 PM, Alexandre Belloni wrote:
> On 05/12/2016 at 10:43:14 +0100, Amelie DELAUNAY wrote :
>>>> +
>>>> + device_init_wakeup(&pdev->dev, true);
>>>
>>> What happens if device_init_wakeup() returns an error?
>> It means that RTC won't be able to wake up the board with RTC alarm. I can
>> add a warning for the user in this case ?
>>>
>
> There is exactly one driver ever checking the return value of
> device_init_wakeup(). It basically always succeeds.
>
>
OK so, is it OK for everyone that I bet on the fact that it will always
succeed?
Powered by blists - more mailing lists