From: Paul Chavent <Paul.Chavent@onera.fr>
To: Johan Hovold <jhovold@gmail.com>
Cc: linux-usb@vger.kernel.org, gregkh@linuxfoundation.org,
fschaefer.oss@googlemail.com, jslaby@suse.cz, max@suse.de,
giometti@enneenne.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] USB : serial : pl2303 wake up after dcd status check.
Date: Fri, 13 Sep 2013 18:22:07 +0200 [thread overview]
Message-ID: <52333BAF.1070409@onera.fr> (raw)
In-Reply-To: <20130913162356.GC9054@localhost>
Hi.
This patch was just a suggestion. Don't bother with rebasing. I will
wait your changes and remove this patch from the next submission.
Cheers.
Paul.
On 09/13/2013 06:23 PM, Johan Hovold wrote:
> On Fri, Sep 13, 2013 at 05:35:13PM +0200, Paul Chavent wrote:
>> Seems to be done this way in other drivers (ch341, 8250, ...).
>> And get tty reference only if dcd_change need to be called.
>
> This is fine. I have a patch here doing the same two changes as part of
> a larger clean-up of the pl2303 interrupt handling (which in turn is
> part of the MSR-refactoring I mentioned). I could rebase on top of this,
> unless you care to wait another week. :)
>
> Thanks,
> Johan
>
>> Signed-off-by: Paul Chavent <paul.chavent@onera.fr>
>> ---
>> drivers/usb/serial/pl2303.c | 17 +++++++++--------
>> 1 file changed, 9 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/usb/serial/pl2303.c b/drivers/usb/serial/pl2303.c
>> index e7a84f0..8b81188 100644
>> --- a/drivers/usb/serial/pl2303.c
>> +++ b/drivers/usb/serial/pl2303.c
>> @@ -854,15 +854,16 @@ static void pl2303_update_line_status(struct usb_serial_port *port,
>> spin_unlock_irqrestore(&priv->lock, flags);
>> if (priv->line_status & UART_BREAK_ERROR)
>> usb_serial_handle_break(port);
>> - wake_up_interruptible(&port->port.delta_msr_wait);
>>
>> - tty = tty_port_tty_get(&port->port);
>> - if (!tty)
>> - return;
>> - if ((priv->line_status ^ prev_line_status) & UART_DCD)
>> - usb_serial_handle_dcd_change(port, tty,
>> - priv->line_status & UART_DCD);
>> - tty_kref_put(tty);
>> + if ((priv->line_status ^ prev_line_status) & UART_DCD) {
>> + tty = tty_port_tty_get(&port->port);
>> + if (tty)
>> + usb_serial_handle_dcd_change(port, tty,
>> + priv->line_status & UART_DCD);
>> + tty_kref_put(tty);
>> + }
>> +
>> + wake_up_interruptible(&port->port.delta_msr_wait);
>> }
>>
>> static void pl2303_read_int_callback(struct urb *urb)
>> --
>> 1.7.12.1
>>
>
prev parent reply other threads:[~2013-09-13 16:28 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
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 [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=52333BAF.1070409@onera.fr \
--to=paul.chavent@onera.fr \
--cc=fschaefer.oss@googlemail.com \
--cc=giometti@enneenne.com \
--cc=gregkh@linuxfoundation.org \
--cc=jhovold@gmail.com \
--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).