mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Drobyshev <immortalguardian1@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: gq@cs.msu.su, giometti@enneenne.com
Subject: [PATCH 0/8] LinuxPPS: some minor fixes and improvements.
Date: Wed, 15 Feb 2017 17:31:01 +0300	[thread overview]
Message-ID: <1487169069-15721-1-git-send-email-immortalguardian1@gmail.com> (raw)

Hello folks,

We are using PPS subsystem with kernel consumer in our long-lasting
project. (To be precise, kernel consumer and most of PPS drivers was
included in vanilla kernel by one of our employee Alexander Gordeev).

During the last years we have fixed dozen of issues and made some
improvements we'd like to give away. I split the patchset into
two parts. Here are some common fixes I'd like to submit. After that
I'll post some improvements in filtration algorithms to increase time
synchronization precision using low quality PPS sources with high
jitter (e.g. x86 box with pps_gen_parport).

I would like this patchset to be merged into current devel.

[PATCH 1/8] hardpps: simple fixes replacing clumsy code with abs() macro. 
[PATCH 2/8] ntp/pps: ignore pps_valid decreasing if there is no pps signal. 
[PATCH 3/8] hardpps: fix some pps_jitter issues. 
[PATCH 4/8] LinuxPPS: kapi: Unlock before waking up events queue in pps_event(). 
[PATCH 5/8] LinuxPPS: pps_parport: Do not generate assert in case of lost signal.
[PATCH 6/8] LinuxPPS: pps_parport: Ignore interrupt invoked less than 0.5 sec after previous.
[PATCH 7/8] LinuxPPS: pps_gen_parport: Add polarity parameter for inverted signal.
[PATCH 8/8] LinuxPPS: pps_gen_parport: Add check for bad clocksource.

             reply	other threads:[~2017-02-15 14:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 14:31 Andrey Drobyshev [this message]
2017-02-15 14:31 ` [PATCH 1/8] hardpps: simple fixes replacing clumsy code with abs() macro Andrey Drobyshev
2017-03-04  7:36   ` Rodolfo Giometti
2017-02-15 14:31 ` [PATCH 2/8] ntp/pps: ignore pps_valid decreasing if there is no pps signal Andrey Drobyshev
2017-03-04  7:36   ` Rodolfo Giometti
2017-02-15 14:31 ` [PATCH 3/8] hardpps: fix some pps_jitter issues Andrey Drobyshev
2017-03-04  7:37   ` Rodolfo Giometti
2017-02-15 14:31 ` [PATCH 4/8] LinuxPPS: kapi: Unlock before waking up events queue in pps_event() Andrey Drobyshev
2017-03-04  7:38   ` Rodolfo Giometti
2017-02-15 14:31 ` [PATCH 5/8] LinuxPPS: pps_parport: Do not generate assert in case of lost signal Andrey Drobyshev
2017-03-04  7:39   ` Rodolfo Giometti
2017-02-15 14:31 ` [PATCH 6/8] LinuxPPS: pps_parport: Ignore interrupt invoked less than 0.5sec after previous Andrey Drobyshev
2017-03-04  7:40   ` Rodolfo Giometti
2017-02-15 14:31 ` [PATCH 7/8] LinuxPPS: pps_gen_parport: Add polarity parameter for inverted signal Andrey Drobyshev
2017-03-04  7:42   ` Rodolfo Giometti
2017-02-15 14:31 ` [PATCH 8/8] LinuxPPS: pps_gen_parport: Add check for bad clocksource Andrey Drobyshev
2017-03-04  7:44   ` Rodolfo Giometti
2017-03-04  9:19     ` Alexander Gerasiov
2017-03-04 13:25       ` Rodolfo Giometti

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=1487169069-15721-1-git-send-email-immortalguardian1@gmail.com \
    --to=immortalguardian1@gmail.com \
    --cc=giometti@enneenne.com \
    --cc=gq@cs.msu.su \
    --cc=linux-kernel@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 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®