From: Kumar Gala <galak@codeaurora.org>
To: Dongsheng Wang <dongsheng.wang@freescale.com>
Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>,
Sandeep Nair <sandeep_n@ti.com>, Olof Johansson <olof@lixom.net>,
shawn.guo@linaro.org, Greg KH <gregkh@linuxfoundation.org>,
Paul Walmsley <paul@pwsan.com>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, shawn.guo@freescale.com
Subject: Re: [PATCH 2/2] soc/fsl: add ftm alarm driver for ls1021a platform
Date: Fri, 26 Sep 2014 09:04:08 -0500 [thread overview]
Message-ID: <B448818B-E208-4451-8BA0-53D53E4BB7FC@codeaurora.org> (raw)
In-Reply-To: <1411714121-32138-2-git-send-email-dongsheng.wang@freescale.com>
On Sep 26, 2014, at 1:48 AM, Dongsheng Wang <dongsheng.wang@freescale.com> wrote:
> From: Wang Dongsheng <dongsheng.wang@freescale.com>
>
> Only Ftm0 can be used when system going to deep sleep. So this driver
> to support ftm0 as a wakeup source.
>
> Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
How does this differ from drivers/clocksource/fsl_ftm_timer.c
Why not extend that with the alarm functionality you need?
Also, where is the DT binding spec for this (if you plan on having a separate driver)?
- k
--
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-09-26 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-26 6:48 [PATCH 1/2] soc/fsl: add freescale dir for SOC specific drivers Dongsheng Wang
2014-09-26 6:48 ` [PATCH 2/2] soc/fsl: add ftm alarm driver for ls1021a platform Dongsheng Wang
2014-09-26 14:04 ` Kumar Gala [this message]
2014-09-28 2:55 ` Dongsheng.Wang
2015-08-12 5:53 [PATCH v2 1/2] soc/fsl: add freescale dir for SOC specific drivers Dongsheng Wang
2015-08-12 5:53 ` [PATCH 2/2] soc/fsl: add ftm alarm driver for ls1021a platform Dongsheng Wang
2015-08-13 13:54 ` Linus Walleij
2015-08-14 3:12 ` Wang Dongsheng
2015-08-14 10:06 ` Linus Walleij
2015-08-21 3:07 ` Wang Dongsheng
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=B448818B-E208-4451-8BA0-53D53E4BB7FC@codeaurora.org \
--to=galak@codeaurora.org \
--cc=arnd@arndb.de \
--cc=dongsheng.wang@freescale.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=paul@pwsan.com \
--cc=sandeep_n@ti.com \
--cc=santosh.shilimkar@ti.com \
--cc=shawn.guo@freescale.com \
--cc=shawn.guo@linaro.org \
/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
all inboxes | Powered by JetHome®