[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160819120305.4a3b1b54@lxorguk.ukuu.org.uk>
Date: Fri, 19 Aug 2016 12:03:05 +0100
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Sebastian Reichel <sre@...nel.org>
Cc: Rob Herring <robh@...nel.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Marcel Holtmann <marcel@...tmann.org>,
Jiri Slaby <jslaby@...e.com>, Pavel Machek <pavel@....cz>,
Peter Hurley <peter@...leysoftware.com>,
NeilBrown <neil@...wn.name>,
"Dr . H . Nikolaus Schaller" <hns@...delico.com>,
Arnd Bergmann <arnd@...db.de>,
Linus Walleij <linus.walleij@...aro.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@...r.kernel.org>,
"linux-serial@...r.kernel.org" <linux-serial@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 0/3] UART slave device bus
> I meant "Either some function similar to userspace's poll() is
> needed, ...". Something like uart_dev_wait_for_rx()
You can't really do that - it might never return and then how do you want
to handle timeouts and cleanups
> Alternatively the rx function could be a callback, that
> is called when there is new data.
That's what the existing API gives you as an ldisc, it can't be immediate
in many cases however but must be buffered.
> > I'm assuming the only immediate consumers are in-kernel.
>
> Yes, but the driver should be notified about incoming data.
Alan
Powered by blists - more mailing lists