From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Geliang Tang <geliangtang@163.com>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] rtc: efi: add efi_procfs in efi_rtc_ops
Date: Wed, 25 Nov 2015 01:05:47 +0100 [thread overview]
Message-ID: <20151125000547.GK3950@piout.net> (raw)
In-Reply-To: <92f29256c04397cde0a3572982702dca359392b6.1446868545.git.geliangtang@163.com>
Hi,
On 07/11/2015 at 12:00:22 +0800, Geliang Tang wrote :
> Add efi_procfs in efi_rtc_ops to show rtc-efi info in /proc/driver/rtc.
> Most of the code comes from efi_rtc_proc_show() in efirtc.
>
I'm actually wondering whether someone actually use those information in
/proc/driver/rtc. Do you have a use case?
> Signed-off-by: Geliang Tang <geliangtang@163.com>
> ---
> drivers/rtc/rtc-efi.c | 66 +++++++++++++++++++++++++++++++++++++++++++++++----
> 1 file changed, 62 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/rtc/rtc-efi.c b/drivers/rtc/rtc-efi.c
> index 3806961..96d3860 100644
> --- a/drivers/rtc/rtc-efi.c
> +++ b/drivers/rtc/rtc-efi.c
> @@ -191,11 +191,69 @@ static int efi_set_time(struct device *dev, struct rtc_time *tm)
> return status == EFI_SUCCESS ? 0 : -EINVAL;
> }
>
> +static int efi_procfs(struct device *dev, struct seq_file *seq)
> +{
> + efi_time_t eft, alm;
> + efi_time_cap_t cap;
> + efi_bool_t enabled, pending;
> +
> + memset(&eft, 0, sizeof(eft));
> + memset(&alm, 0, sizeof(alm));
> + memset(&cap, 0, sizeof(cap));
> +
> + efi.get_time(&eft, &cap);
> + efi.get_wakeup_time(&enabled, &pending, &alm);
> +
> + seq_printf(seq,
> + "Time\t\t: %u:%u:%u.%09u\n"
> + "Date\t\t: %u-%u-%u\n"
> + "Daylight\t: %u\n",
> + eft.hour, eft.minute, eft.second, eft.nanosecond,
> + eft.year, eft.month, eft.day,
> + eft.daylight);
> +
> + if (eft.timezone == EFI_UNSPECIFIED_TIMEZONE)
> + seq_puts(seq, "Timezone\t: unspecified\n");
> + else
> + /* XXX fixme: convert to string? */
> + seq_printf(seq, "Timezone\t: %u\n", eft.timezone);
> +
> + seq_printf(seq,
> + "Alarm Time\t: %u:%u:%u.%09u\n"
> + "Alarm Date\t: %u-%u-%u\n"
> + "Alarm Daylight\t: %u\n"
> + "Enabled\t\t: %s\n"
> + "Pending\t\t: %s\n",
> + alm.hour, alm.minute, alm.second, alm.nanosecond,
> + alm.year, alm.month, alm.day,
> + alm.daylight,
> + enabled == 1 ? "yes" : "no",
> + pending == 1 ? "yes" : "no");
> +
> + if (eft.timezone == EFI_UNSPECIFIED_TIMEZONE)
> + seq_puts(seq, "Timezone\t: unspecified\n");
> + else
> + /* XXX fixme: convert to string? */
> + seq_printf(seq, "Timezone\t: %u\n", alm.timezone);
> +
> + /*
> + * now prints the capabilities
> + */
> + seq_printf(seq,
> + "Resolution\t: %u\n"
> + "Accuracy\t: %u\n"
> + "SetstoZero\t: %u\n",
> + cap.resolution, cap.accuracy, cap.sets_to_zero);
> +
> + return 0;
> +}
> +
> static const struct rtc_class_ops efi_rtc_ops = {
> - .read_time = efi_read_time,
> - .set_time = efi_set_time,
> - .read_alarm = efi_read_alarm,
> - .set_alarm = efi_set_alarm,
> + .read_time = efi_read_time,
> + .set_time = efi_set_time,
> + .read_alarm = efi_read_alarm,
> + .set_alarm = efi_set_alarm,
> + .proc = efi_procfs,
> };
>
> static int __init efi_rtc_probe(struct platform_device *dev)
> --
> 2.5.0
>
>
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-25 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 4:00 [PATCH 1/2] rtc: fix module reference count in rtc-proc Geliang Tang
2015-11-07 4:00 ` [PATCH 2/2] rtc: efi: add efi_procfs in efi_rtc_ops Geliang Tang
2015-11-25 0:05 ` Alexandre Belloni [this message]
2015-11-30 19:03 ` [PATCH 1/2] rtc: fix module reference count in rtc-proc Alexandre Belloni
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=20151125000547.GK3950@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=geliangtang@163.com \
--cc=linux-kernel@vger.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