From: Johan Hovold <jhovold@gmail.com>
To: Paul Chavent <Paul.Chavent@onera.fr>
Cc: linux-usb@vger.kernel.org, gregkh@linuxfoundation.org,
jhovold@gmail.com, fschaefer.oss@googlemail.com, jslaby@suse.cz,
max@suse.de, giometti@enneenne.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] USB : serial : invoke dcd_change ldisc's handler.
Date: Fri, 13 Sep 2013 17:53:55 +0200 [thread overview]
Message-ID: <20130913155355.GB9054@localhost> (raw)
In-Reply-To: <1379086513-2434-3-git-send-email-paul.chavent@onera.fr>
On Fri, Sep 13, 2013 at 05:35:12PM +0200, Paul Chavent wrote:
> Signed-off-by: Paul Chavent <paul.chavent@onera.fr>
> ---
> Documentation/pps/pps.txt | 15 +++++++++++++++
> drivers/usb/serial/generic.c | 9 +++++++++
> 2 files changed, 24 insertions(+)
>
> diff --git a/Documentation/pps/pps.txt b/Documentation/pps/pps.txt
> index d35dcdd..67b9a94 100644
> --- a/Documentation/pps/pps.txt
> +++ b/Documentation/pps/pps.txt
> @@ -66,6 +66,21 @@ In LinuxPPS the PPS sources are simply char devices usually mapped
> into files /dev/pps0, /dev/pps1, etc..
>
>
> +PPS with USB to serial devices
> +------------------------------
> +
> +It is possible to grab the PPS from an USB to serial device. However,
> +you should take into account the latencies and jitter introduced by
> +the USB stack. Users has reported clock instability around +-1ms when
> +synchronized with PPS through USB. This isn't suited for time server
> +synchronisation.
> +
> +If your device doesn't report PPS, you can check that the feature is
> +supported by its driver. Most of the time, you only need to add a call
> +to usb_serial_handle_dcd_change after checking the DCD status (see
> +ch341 and pl2303 examples).
> +
> +
> Coding example
> --------------
>
> diff --git a/drivers/usb/serial/generic.c b/drivers/usb/serial/generic.c
> index 1f31e6b..877d6e0 100644
> --- a/drivers/usb/serial/generic.c
> +++ b/drivers/usb/serial/generic.c
> @@ -568,6 +568,15 @@ void usb_serial_handle_dcd_change(struct usb_serial_port *usb_port,
> {
> struct tty_port *port = &usb_port->port;
>
> + if (tty) {
> + struct tty_ldisc *ld = tty_ldisc_ref(tty);
> + if (ld) {
> + if (ld->ops->dcd_change)
> + ld->ops->dcd_change(tty, status);
> + tty_ldisc_deref(ld);
> + }
> + }
> +
> dev_dbg(&usb_port->dev, "%s - status %d\n", __func__, status);
Please add your ldisc handling after the debug statement.
Thanks,
Johan
next prev parent reply other threads:[~2013-09-13 15:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 15:35 [PATCH 0/3] Enable PPS reporting for USB serial devices V2 Paul Chavent
2013-09-13 15:35 ` [PATCH 1/3] USB : serial : call handle_dcd_change in ftdi driver Paul Chavent
2013-09-13 15:47 ` Greg KH
2013-09-13 15:51 ` Johan Hovold
2013-09-13 19:08 ` Sergei Shtylyov
2013-09-13 15:35 ` [PATCH 2/3] USB : serial : invoke dcd_change ldisc's handler Paul Chavent
2013-09-13 15:47 ` Greg KH
2013-09-13 15:53 ` Johan Hovold [this message]
2013-09-13 17:12 ` Rodolfo Giometti
2013-09-13 19:12 ` Sergei Shtylyov
2013-09-13 15:35 ` [PATCH 3/3] USB : serial : pl2303 wake up after dcd status check Paul Chavent
2013-09-13 16:23 ` Johan Hovold
2013-09-13 16:22 ` Paul Chavent
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=20130913155355.GB9054@localhost \
--to=jhovold@gmail.com \
--cc=Paul.Chavent@onera.fr \
--cc=fschaefer.oss@googlemail.com \
--cc=giometti@enneenne.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=max@suse.de \
/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 NNTP newsgroup(s).