devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sebastian Reichel <sre@kernel.org>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Gustavo Padovan <gustavo@padovan.org>,
	Johan Hedberg <johan.hedberg@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Pavel Machek <pavel@ucw.cz>, Tony Lindgren <tony@atomide.com>,
	Jiri Slaby <jslaby@suse.com>, Mark Rutland <mark.rutland@arm.com>,
	linux-bluetooth@vger.kernel.org, linux-serial@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCHv3 02/10] serdev: add serdev_device_wait_until_sent
Date: Sat, 8 Apr 2017 18:57:40 +0200	[thread overview]
Message-ID: <20170408165740.GA20058@kroah.com> (raw)
In-Reply-To: <20170328155939.31566-3-sre@kernel.org>

On Tue, Mar 28, 2017 at 05:59:31PM +0200, Sebastian Reichel wrote:
> Add method, which waits until the transmission buffer has been sent.
> Note, that the change in ttyport_write_wakeup is related, since
> tty_wait_until_sent will hang without that change.
> 
> Acked-by: Rob Herring <robh@kernel.org>
> Acked-by: Pavel Machek <pavel@ucw.cz>
> Signed-off-by: Sebastian Reichel <sre@kernel.org>
> ---
> Changes since PATCHv2:
>  * Avoid goto in ttyport_write_wakeup
> ---
>  drivers/tty/serdev/core.c           | 11 +++++++++++
>  drivers/tty/serdev/serdev-ttyport.c | 18 ++++++++++++++----
>  include/linux/serdev.h              |  3 +++
>  3 files changed, 28 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/tty/serdev/core.c b/drivers/tty/serdev/core.c
> index f4c6c90add78..a63b74031e22 100644
> --- a/drivers/tty/serdev/core.c
> +++ b/drivers/tty/serdev/core.c
> @@ -173,6 +173,17 @@ void serdev_device_set_flow_control(struct serdev_device *serdev, bool enable)
>  }
>  EXPORT_SYMBOL_GPL(serdev_device_set_flow_control);
>  
> +void serdev_device_wait_until_sent(struct serdev_device *serdev, long timeout)
> +{
> +	struct serdev_controller *ctrl = serdev->ctrl;
> +
> +	if (!ctrl || !ctrl->ops->wait_until_sent)
> +		return;
> +
> +	ctrl->ops->wait_until_sent(ctrl, timeout);
> +}
> +EXPORT_SYMBOL_GPL(serdev_device_wait_until_sent);

Is this still needed now that we have serdev_device_write() with an
unlimited timeout available?

thanks,

greg k-h

  reply	other threads:[~2017-04-08 16:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28 15:59 [PATCHv3 00/10] Nokia H4+ support Sebastian Reichel
2017-03-28 15:59 ` [PATCHv3 01/10] tty: serial: omap: add UPF_BOOT_AUTOCONF flag for DT init Sebastian Reichel
     [not found] ` <20170328155939.31566-1-sre-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-03-28 15:59   ` [PATCHv3 02/10] serdev: add serdev_device_wait_until_sent Sebastian Reichel
2017-04-08 16:57     ` Greg Kroah-Hartman [this message]
     [not found]       ` <20170408165740.GA20058-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-04-10 13:46         ` Rob Herring
2017-04-10 14:03           ` Greg Kroah-Hartman
     [not found]             ` <20170410140313.GA31894-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-04-10 16:12               ` Rob Herring
2017-04-10 17:10                 ` Sebastian Reichel
2017-03-28 15:59   ` [PATCHv3 06/10] Bluetooth: hci_uart: add serdev driver support library Sebastian Reichel
2017-03-28 15:59   ` [PATCHv3 08/10] Bluetooth: hci_serdev: allow modular drivers Sebastian Reichel
2017-03-28 15:59   ` [PATCHv3 09/10] dt-bindings: net: bluetooth: Add nokia-bluetooth Sebastian Reichel
2017-03-28 15:59   ` [PATCHv3 10/10] Bluetooth: add nokia driver Sebastian Reichel
2017-03-28 15:59 ` [PATCHv3 03/10] serdev: implement get/set tiocm Sebastian Reichel
2017-03-28 15:59 ` [PATCHv3 04/10] serdev: add helpers for cts and rts handling Sebastian Reichel
2017-03-28 15:59 ` [PATCHv3 05/10] Bluetooth: hci_uart: add support for word alignment Sebastian Reichel
2017-03-28 15:59 ` [PATCHv3 07/10] Bluetooth: hci_serdev: do not open device in hci open Sebastian Reichel
2017-03-29 21:17 ` [PATCHv3 00/10] Nokia H4+ support Rob Herring
2017-03-29 21:33   ` Marcel Holtmann
2017-03-31 13:33     ` Greg Kroah-Hartman
2017-04-05 18:16       ` Rob Herring
     [not found]         ` <CAL_Jsq+NU3M5yuBpK1UGgzCVvq0eABMApCqEe3_d5+tDaABsgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-04-05 20:28           ` Pavel Machek
2017-04-10 23:10           ` Sebastian Reichel
2017-04-11 11:36             ` Marcel Holtmann
     [not found]               ` <4FEFA1D8-BE23-40FB-BAA3-3EC910FE9F96-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2017-04-11 14:06                 ` Greg Kroah-Hartman
     [not found]                   ` <20170411140637.GA4388-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2017-04-12 20:19                     ` Marcel Holtmann
     [not found]                       ` <C16140C4-0264-411B-9058-0B9013AAC82F-kz+m5ild9QBg9hUCZPvPmw@public.gmane.org>
2017-04-13  0:26                         ` Sebastian Reichel

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=20170408165740.GA20058@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gustavo@padovan.org \
    --cc=johan.hedberg@gmail.com \
    --cc=jslaby@suse.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=mark.rutland@arm.com \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=sre@kernel.org \
    --cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).