From: Amelie DELAUNAY <amelie.delaunay@st.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
"a.zummo@towertech.it" <a.zummo@towertech.it>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
Alexandre TORGUE <alexandre.torgue@st.com>,
"linux@armlinux.org.uk" <linux@armlinux.org.uk>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Gabriel FERNANDEZ <gabriel.fernandez@st.com>
Subject: [rtc-linux] Re: [PATCH 3/8] rtc: add STM32 RTC driver
Date: Mon, 12 Dec 2016 10:59:51 +0100 [thread overview]
Message-ID: <a2d3ddc0-c8f6-0f42-ad33-a92e0ac6aee4@st.com> (raw)
In-Reply-To: <20161207183709.tbkapu34ljlg4skp@piout.net>
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?
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-12-12 10:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 14:09 [rtc-linux] [PATCH 0/8] Add support for STM32 RTC Amelie Delaunay
2016-12-02 14:09 ` [rtc-linux] [PATCH 1/8] ARM: dts: stm32: set HSE_RTC clock frequency to 1 MHz on stm32f429 Amelie Delaunay
2016-12-02 14:09 ` [rtc-linux] [PATCH 2/8] dt-bindings: document the STM32 RTC bindings Amelie Delaunay
2016-12-05 10:06 ` [rtc-linux] " Alexandre Belloni
2016-12-05 10:14 ` Amelie DELAUNAY
2016-12-02 14:09 ` [rtc-linux] [PATCH 3/8] rtc: add STM32 RTC driver Amelie Delaunay
2016-12-02 17:56 ` [rtc-linux] " Mathieu Poirier
2016-12-05 9:43 ` Amelie DELAUNAY
2016-12-05 16:32 ` Mathieu Poirier
2016-12-07 10:16 ` Amelie DELAUNAY
2016-12-07 18:37 ` Alexandre Belloni
2016-12-12 9:59 ` Amelie DELAUNAY [this message]
2016-12-02 18:05 ` Mathieu Poirier
2016-12-05 9:45 ` Amelie DELAUNAY
2016-12-07 19:08 ` Alexandre Belloni
2016-12-02 14:09 ` [rtc-linux] [PATCH 4/8] ARM: dts: stm32: Add STM32 RTC support for STM32F429 MCU Amelie Delaunay
2016-12-02 14:09 ` [rtc-linux] [PATCH 5/8] ARM: dts: stm32: enable RTC on stm32f429-disco Amelie Delaunay
2016-12-02 14:09 ` [rtc-linux] [PATCH 6/8] ARM: dts: stm32: enable RTC on stm32f469-disco Amelie Delaunay
2016-12-02 14:10 ` [rtc-linux] [PATCH 7/8] ARM: dts: stm32: enable RTC on stm32429i-eval Amelie Delaunay
2016-12-02 14:10 ` [rtc-linux] [PATCH 8/8] ARM: configs: stm32: Add STM32 RTC support in STM32 defconfig Amelie Delaunay
[not found] <bc5c308d-472a-bf05-89b8-6d813fb5321d@st.com>
2016-12-12 10:19 ` [rtc-linux] Re: [PATCH 3/8] rtc: add STM32 RTC driver Amelie DELAUNAY
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=a2d3ddc0-c8f6-0f42-ad33-a92e0ac6aee4@st.com \
--to=amelie.delaunay@st.com \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@free-electrons.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=mathieu.poirier@linaro.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh+dt@kernel.org \
--cc=rtc-linux@googlegroups.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