From: Rodolfo Giometti <giometti@enneenne.com>
To: lakshmi.sowjanya.d@intel.com, linux-kernel@vger.kernel.org
Cc: andriy.shevchenko@linux.intel.com, pandith.n@intel.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v1] Documentation: driver-api: pps: Update PPS generator documentation
Date: Fri, 6 Oct 2023 14:38:19 +0200 [thread overview]
Message-ID: <539bcab9-e8f8-524a-c14b-a5879ce4415a@enneenne.com> (raw)
In-Reply-To: <20231006121531.22450-1-lakshmi.sowjanya.d@intel.com>
On 06/10/23 14:15, lakshmi.sowjanya.d@intel.com wrote:
> From: Pandith N <pandith.n@intel.com>
>
> PPS documentation has a generalized section for generators. Update the
> section so any new generator documentation can be appended.
>
> Signed-off-by: Pandith N <pandith.n@intel.com>
> Signed-off-by: Lakshmi Sowjanya D <lakshmi.sowjanya.d@intel.com>
> ---
> Documentation/driver-api/pps.rst | 16 +++++++++++-----
> 1 file changed, 11 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/driver-api/pps.rst b/Documentation/driver-api/pps.rst
> index 2d6b99766ee8..78dded03e5d8 100644
> --- a/Documentation/driver-api/pps.rst
> +++ b/Documentation/driver-api/pps.rst
> @@ -200,11 +200,17 @@ Generators
>
> Sometimes one needs to be able not only to catch PPS signals but to produce
> them also. For example, running a distributed simulation, which requires
> -computers' clock to be synchronized very tightly. One way to do this is to
> -invent some complicated hardware solutions but it may be neither necessary
> -nor affordable. The cheap way is to load a PPS generator on one of the
> -computers (master) and PPS clients on others (slaves), and use very simple
> -cables to deliver signals using parallel ports, for example.
> +computers' clock to be synchronized very tightly.
> +
> +
> +Parallel port generator
> +------------------------
> +
> +One way to do this is to invent some complicated hardware solutions but it
> +may be neither necessary nor affordable. The cheap way is to load a PPS
> +generator on one of the computers (master) and PPS clients on others
> +(slaves), and use very simple cables to deliver signals using parallel
> +ports, for example.
>
> Parallel port cable pinout::
>
Acked-by: Rodolfo Giometti <giometti@enneenne.com>
--
GNU/Linux Solutions e-mail: giometti@enneenne.com
Linux Device Driver giometti@linux.it
Embedded Systems phone: +39 349 2432127
UNIX programming skype: rodolfo.giometti
next prev parent reply other threads:[~2023-10-06 12:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 12:15 lakshmi.sowjanya.d
2023-10-06 12:38 ` Rodolfo Giometti [this message]
2023-10-16 9:11 ` Andy Shevchenko
2023-10-16 10:19 lakshmi.sowjanya.d
2023-10-17 12:48 ` Andy Shevchenko
2023-10-26 17:38 ` Jonathan Corbet
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=539bcab9-e8f8-524a-c14b-a5879ce4415a@enneenne.com \
--to=giometti@enneenne.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pandith.n@intel.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
all inboxes | Powered by JetHome®