From: Johan Hovold <johan@kernel.org>
To: Keerthy <j-keerthy@ti.com>
Cc: a.zummo@towertech.it, alexandre.belloni@bootlin.com,
t-kristo@ti.com, linux-rtc@vger.kernel.org,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
johan@kernel.org
Subject: Re: [PATCH v4 4/4] rtc: interface: Add power_off_program to rtc_class_ops
Date: Thu, 19 Jul 2018 12:40:18 +0200 [thread overview]
Message-ID: <20180719104018.GT10204@localhost> (raw)
In-Reply-To: <1531372060-10532-5-git-send-email-j-keerthy@ti.com>
On Thu, Jul 12, 2018 at 10:37:40AM +0530, Keerthy wrote:
> Add an interface function to set up the rtc for a power_off
> mode.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
> drivers/rtc/interface.c | 12 ++++++++++++
> drivers/rtc/rtc-omap.c | 1 +
> include/linux/rtc.h | 2 ++
> 3 files changed, 15 insertions(+)
>
> diff --git a/drivers/rtc/interface.c b/drivers/rtc/interface.c
> index 6d4012d..c19668b9 100644
> --- a/drivers/rtc/interface.c
> +++ b/drivers/rtc/interface.c
> @@ -1139,3 +1139,15 @@ int rtc_set_offset(struct rtc_device *rtc, long offset)
> trace_rtc_set_offset(offset, ret);
> return ret;
> }
> +
> +/**
> + * rtc_power_off_program - Some of the rtc are hooked on to PMIC_EN
> + * line and can be used to power off the SoC.
> + *
> + * Kernel interface to program rtc to power off
> + */
> +int rtc_power_off_program(struct rtc_device *rtc)
> +{
> + return rtc->ops->power_off_program(rtc->dev.parent);
Why pass in parent instead of the rtc?
> +}
> +EXPORT_SYMBOL_GPL(rtc_power_off_program);
Either way, this is likely not an acceptable interface for this as
Alexandre already mentioned.
As I already suggested, I think you submit this as part of the PM work
adding support for entering the TI RTC-only mode. That will hopefully
provide enough context to be able to determine the right interface.
Note that this also means that we shouldn't split the current rtc-omap
power-off handler before this has been settled (i.e. patches 2/4 and 4/4
should not be applied before then).
Thanks,
Johan
prev parent reply other threads:[~2018-07-19 10:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 5:07 [PATCH v4 0/4] rtc: OMAP: Add support for rtc-only mode Keerthy
2018-07-12 5:07 ` [PATCH v4 1/4] rtc: omap: Cut down the shutdown time from 2 seconds to 1 sec Keerthy
2018-07-19 10:02 ` Johan Hovold
2018-07-19 11:53 ` Keerthy
2018-07-19 12:22 ` Keerthy
2018-07-19 12:36 ` Johan Hovold
2018-07-19 12:46 ` Keerthy
2018-07-20 10:33 ` Keerthy
2018-07-20 11:03 ` Johan Hovold
2018-07-19 10:23 ` Johan Hovold
2018-07-12 5:07 ` [PATCH v4 2/4] rtc: OMAP: Add support for rtc-only mode Keerthy
2018-07-19 10:29 ` Johan Hovold
2018-07-12 5:07 ` [PATCH v4 3/4] rtc: omap: use of_device_is_system_power_controller function Keerthy
2018-07-19 10:34 ` Johan Hovold
2018-07-12 5:07 ` [PATCH v4 4/4] rtc: interface: Add power_off_program to rtc_class_ops Keerthy
2018-07-19 10:40 ` Johan Hovold [this message]
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=20180719104018.GT10204@localhost \
--to=johan@kernel.org \
--cc=a.zummo@towertech.it \
--cc=alexandre.belloni@bootlin.com \
--cc=j-keerthy@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=t-kristo@ti.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;
as well as URLs for NNTP newsgroup(s).