From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Janusz Uzycki <janusz.uzycki@elproma.com.pl>
Cc: linux-can@vger.kernel.org,
Krzysztof Borgulski <k.borgulski@elproma.com.pl>
Subject: Re: RFC: (optional) software filtering in candump
Date: Wed, 19 Jun 2013 18:59:33 +0200 [thread overview]
Message-ID: <51C1E375.3050600@hartkopp.net> (raw)
In-Reply-To: <D1C57559EF7B4FA8A6C669A1BF05CFDB@laptop2>
>> Additional a hardware timestamp can be retrieved from the hardware and passed
>> to the userspace. (HW timestamps)
>
> Thanks Oliver for the explanation. It's clean now.
> Shouldn't hardware timestamping option be implemented like PTP?
> http://lxr.linux.no/linux+v3.9.6/net/core/timestamping.c#L104 (I don't need
> it but I couldn't find HW timestamp code for SJA1000 or MCP2515)
Yes, that's missing.
AFAIK only the PCAN USB (Pro) supports to pass the hardware timestamps to the
userspace. But when i took a quick look into the output, i wasn't able to
retrieve the HW timestamps.
I wrote a fix for the driver:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/can/usb/peak_usb/pcan_usb.c?id=c9faaa09e2a1335678f09c70a0d0eda095564bab
But i didn't manage to verify the HW timestamp output.
It's on my list of things i wanted to investigate when i'm bored ;-)
Regards,
Oliver
next prev parent reply other threads:[~2013-06-19 16:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <190D92B052C049F4B059DCFE8F841940@laptop2>
2013-06-14 18:05 ` RFC: (optional) software filtering in candump Oliver Hartkopp
2013-06-17 11:27 ` Janusz Uzycki
2013-06-19 16:59 ` Oliver Hartkopp [this message]
2013-06-14 8:42 Janusz Uzycki
-- strict thread matches above, loose matches on Subject: below --
2013-05-29 20:55 RxFilter issues vcan Sebastian Haas
2013-05-30 4:58 ` Oliver Hartkopp
2013-05-30 8:34 ` Sebastian Haas
2013-05-30 8:49 ` Oliver Hartkopp
2013-05-30 9:06 ` Sebastian Haas
2013-05-30 10:17 ` RFC: (optional) software filtering in candump Kurt Van Dijck
2013-05-30 12:07 ` Oliver Hartkopp
2013-05-30 12:35 ` Kurt Van Dijck
2013-05-30 15:37 ` Sebastian Haas
2013-05-30 15:55 ` Oliver Hartkopp
2013-05-31 20:40 ` Sebastian Haas
2013-06-01 14:15 ` Oliver Hartkopp
2013-06-01 18:35 ` Sebastian Haas
2013-06-02 11:23 ` Kurt Van Dijck
2015-03-17 10:44 ` Marc Kleine-Budde
2015-03-17 11:34 ` Marc Kleine-Budde
2015-03-17 12:04 ` Oliver Hartkopp
2015-03-17 13:02 ` Oliver Hartkopp
2015-03-17 13:33 ` Marc Kleine-Budde
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=51C1E375.3050600@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=janusz.uzycki@elproma.com.pl \
--cc=k.borgulski@elproma.com.pl \
--cc=linux-can@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.