From: Charlie Johnston <charlie.johnston@ni.com>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Brenda Streiff <brenda.streiff@ni.com>
Subject: Re: [RFC PATCH] pps: Increase PPS_MAX_SOURCES value.
Date: Thu, 22 Jun 2023 21:03:35 -0500 [thread overview]
Message-ID: <fa298357-0b3c-5534-0619-1bd8911846f7@ni.com> (raw)
In-Reply-To: <c770492b-dfee-c38e-f15a-aad382caec25@enneenne.com>
On 6/21/23 10:31, Rodolfo Giometti wrote:
> On 20/06/23 22:42, Charlie Johnston wrote:
>> I've resubmitted the patch with just PPS_MAX_SOURCES = MINORMASK. The system which hits the limit and causes the problem is currently available for testing.
>>
>> Is there anything you'd like me to try running? Or just confirm the limit change works?
>
> Sorry for the delay (i was very busy in these days)! Please, test the attached
> two patches.
>
> Ciao,
>
> Rodolfo
>
Had some time to test today. Everything I tried appeared to work and the message log indicated sources were available for each port.
[ 1.853052] pps_core: LinuxPPS API ver. 1 registered
[ 2.749945] pps pps0: new PPS source ptp0
[ 2.790179] pps pps1: new PPS source ptp1
[ 2.818900] pps pps2: new PPS source ptp3
...
[ 6.326282] pps pps26: new PPS source ptp27
[ 6.354941] pps pps27: new PPS source ptp28
[ 6.383575] pps pps28: new PPS source ptp29
Thanks for the quick turnaround on the patches!
Charlie
prev parent reply other threads:[~2023-06-23 2:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 20:31 [RFC PATCH] pps: Increase PPS_MAX_SOURCES value Charlie Johnston
2023-06-07 7:33 ` Rodolfo Giometti
2023-06-07 22:07 ` Charlie Johnston
2023-06-09 7:30 ` Rodolfo Giometti
2023-06-09 21:00 ` Charlie Johnston
2023-06-12 16:07 ` Rodolfo Giometti
2023-06-20 20:42 ` Charlie Johnston
2023-06-21 15:31 ` Rodolfo Giometti
2023-06-23 2:03 ` Charlie Johnston [this message]
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=fa298357-0b3c-5534-0619-1bd8911846f7@ni.com \
--to=charlie.johnston@ni.com \
--cc=brenda.streiff@ni.com \
--cc=giometti@enneenne.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).