From: Greg KH <gregkh@linuxfoundation.org>
To: sean.wang@mediatek.com
Cc: jslaby@suse.com, andriy.shevchenko@linux.intel.com,
mika.westerberg@linux.intel.com, sr@denx.de, arnd@arndb.de,
matthias.bgg@gmail.com, tthayer@opensource.altera.com,
linux-mediatek@lists.infradead.org, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Steven Liu <steven.liu@mediatek.com>,
Ryder Lee <ryder.lee@mediatek.com>
Subject: Re: [PATCH v3] tty: serial: don't do termios for BTIF
Date: Tue, 5 May 2020 13:10:28 +0200 [thread overview]
Message-ID: <20200505111028.GA114206@kroah.com> (raw)
In-Reply-To: <20200422180900.GA3454664@kroah.com>
On Wed, Apr 22, 2020 at 08:09:00PM +0200, Greg KH wrote:
> On Thu, Apr 23, 2020 at 02:02:08AM +0800, sean.wang@mediatek.com wrote:
> > From: Sean Wang <sean.wang@mediatek.com>
> >
> > Bluetooth Interface (BTIF) is designed dedicatedly for MediaTek SOC with
> > BT in order to be instead of the UART interface between BT module and Host
> > CPU, and not exported to user space to access.
> >
> > As the UART design, BTIF will be an APB slave and can transmit or receive
> > data by MCU access, but doesn't provide termios function like baudrate and
> > flow control setup.
>
> Why does it matter? If the connection isn't exported to userspace, who
> would run those termios functions on the port?
Dropping from my patch queues due to a lack of response, please address
this question when you resend this.
greg k-h
next prev parent reply other threads:[~2020-05-05 11:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 18:02 [PATCH v3] tty: serial: don't do termios for BTIF sean.wang
2020-04-22 18:09 ` Greg KH
2020-05-05 11:10 ` Greg KH [this message]
2020-06-17 3:50 ` sean.wang
2020-04-22 19:20 ` Andy Shevchenko
2020-06-17 3:58 ` sean.wang
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=20200505111028.GA114206@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=mika.westerberg@linux.intel.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=sr@denx.de \
--cc=steven.liu@mediatek.com \
--cc=tthayer@opensource.altera.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).