From: "Velumani T-ERS,HCLTech" <velumanit@hcl.com>
To: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: Patrick Williams <patrickw3@fb.com>
Subject: adding sync method in phosphor-time-manager
Date: Tue, 6 Oct 2020 17:38:13 +0000 [thread overview]
Message-ID: <PU1PR04MB2248961AEF87BA87C7749050A70D0@PU1PR04MB2248.apcprd04.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1930 bytes --]
Classification:
Hi Team,
We wanted to add another time sync method in phosphor-time-manager to get the time from the host and set it to BMC. To have this option configurable I propose a dbus property in the time interface(given below). Please provide your feedback/comments.
https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/xyz/openbmc_project/Time/Synchronization.interface.yaml
enumerations:
- name: Method
description: >
Possible methods of time synchronization.
values:
- name: NTP
description: >
Sync by using the Network Time Protocol.
- name: Manual
description: >
Sync time manually.
- name: HostSync
description: >
Sync the time from host.
Regards,
Velu
::DISCLAIMER::
________________________________
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects.
________________________________
[-- Attachment #2: Type: text/html, Size: 5127 bytes --]
next reply other threads:[~2020-10-06 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-06 17:38 Velumani T-ERS,HCLTech [this message]
2020-10-06 21:41 ` adding sync method in phosphor-time-manager Richard Hanley
2020-10-07 1:38 ` Patrick Williams
2020-10-07 17:18 ` Velumani T-ERS,HCLTech
2020-10-07 1:34 ` Patrick Williams
2021-04-08 18:08 ` Alexander Amelkin
2021-04-08 19:36 ` Ed Tanous
2021-04-09 7:26 ` Lei Yu
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=PU1PR04MB2248961AEF87BA87C7749050A70D0@PU1PR04MB2248.apcprd04.prod.outlook.com \
--to=velumanit@hcl.com \
--cc=openbmc@lists.ozlabs.org \
--cc=patrickw3@fb.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).