From: "Christopher Hall" <christopher.s.hall@intel.com>
To: "Richard Cochran" <richardcochran@gmail.com>
Cc: tglx@linutronix.de, mingo@redhat.com, john.stultz@linaro.org,
hpa@zytor.com, jeffrey.t.kirsher@intel.com, x86@kernel.org,
linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, kevin.b.stanton@intel.com
Subject: Re: [RFC v5 5/6] Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping
Date: Wed, 06 Jan 2016 17:42:53 -0800 [thread overview]
Message-ID: <op.yauhpruq1774gr@chall-mobl2.amr.corp.intel.com> (raw)
In-Reply-To: <20160105152731.GA24372@netboy>
Hi Richard,
This all sounds fine. Thanks for the feedback. I'll roll this into the
next patchset.
Chris
On Tue, 05 Jan 2016 07:27:32 -0800, Richard Cochran
<richardcochran@gmail.com> wrote:
> On Mon, Jan 04, 2016 at 04:45:22AM -0800, Christopher S. Hall wrote:
>> + case PTP_SYS_OFFSET_PRECISE:
>> + if (!ptp->info->getsynctime) {
>> + err = -EINVAL;
>
> -EOPNOTSUPP would be better here.
>
>> + precise_offset.sys_real.sec =
>> + div_u64_rem(ktime_to_ns(xtstamp.sys_realtime),
>> + NSEC_PER_SEC, &rem);
>> + precise_offset.sys_real.nsec = rem;
>
> How about this instead:
>
> ts = ktime_to_timespec64(xtstamp.sys_realtime);
> precise_offset.sys_real.sec = ts.tv_sec;
> precise_offset.sys_real.nsec = ts.tv_nsec;
>
>> + precise_offset.sys_raw.sec =
>> + div_u64_rem(ktime_to_ns(xtstamp.sys_monoraw),
>> + NSEC_PER_SEC, &rem);
>> + precise_offset.sys_raw.nsec = rem;
>> + precise_offset.dev.sec =
>> + div_u64_rem(ktime_to_ns(xtstamp.device), NSEC_PER_SEC,
>> + &rem);
>> + precise_offset.dev.nsec = rem;
>
> And for these as well.
>
> Thanks,
> Richard
next prev parent reply other threads:[~2016-01-07 1:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 12:45 [RFC v5 0/6] Patchset enabling hardware based cross-timestamps for next gen Intel platforms Christopher S. Hall
2016-01-04 12:45 ` [RFC v5 1/6] Timekeeping cross timestamp interface for device drivers Christopher S. Hall
2016-01-06 18:55 ` John Stultz
2016-01-08 0:42 ` Christopher Hall
2016-01-08 1:05 ` John Stultz
2016-01-08 9:13 ` Richard Cochran
2016-01-04 12:45 ` [RFC v5 2/6] Always Running Timer (ART) correlated clocksource Christopher S. Hall
2016-01-04 12:45 ` [RFC v5 3/6] Add history to cross timestamp interface supporting slower devices Christopher S. Hall
2016-01-06 19:37 ` John Stultz
2016-01-08 1:07 ` Christopher Hall
2016-01-08 1:12 ` John Stultz
2016-01-08 14:04 ` Thomas Gleixner
2016-01-08 22:28 ` Christopher Hall
2016-01-04 12:45 ` [RFC v5 4/6] Remove duplicate code from ktime_get_raw_and_real code Christopher S. Hall
2016-01-06 19:42 ` John Stultz
2016-01-04 12:45 ` [RFC v5 5/6] Add PTP_SYS_OFFSET_PRECISE for driver crosstimestamping Christopher S. Hall
2016-01-05 15:27 ` Richard Cochran
2016-01-07 1:42 ` Christopher Hall [this message]
2016-01-04 12:45 ` [RFC v5 6/6] Adds hardware supported cross timestamp Christopher S. Hall
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=op.yauhpruq1774gr@chall-mobl2.amr.corp.intel.com \
--to=christopher.s.hall@intel.com \
--cc=hpa@zytor.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.stultz@linaro.org \
--cc=kevin.b.stanton@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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®