From: Tony Lindgren <tony@atomide.com>
To: Felipe Balbi <balbi@ti.com>
Cc: Nishanth Menon <nm@ti.com>,
yegorslists@googlemail.com, linux-serial@vger.kernel.org,
linux-omap@vger.kernel.org, gregkh@linuxfoundation.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Sekhar Nori <nsekhar@ti.com>
Subject: Re: [PATCH] tty: serial: omap: use mctrl_gpio helpers
Date: Fri, 22 May 2015 10:54:30 -0700 [thread overview]
Message-ID: <20150522175429.GB10274@atomide.com> (raw)
In-Reply-To: <20150522173816.GE5582@saruman.tx.rr.com>
* Felipe Balbi <balbi@ti.com> [150522 10:41]:
> On Fri, May 22, 2015 at 09:52:13AM -0700, Tony Lindgren wrote:
> > * Nishanth Menon <nm@ti.com> [150522 08:36]:
> > > On 05/22/2015 07:16 AM, yegorslists@googlemail.com wrote:
> > > > From: Yegor Yefremov <yegorslists@googlemail.com>
> > > >
> > > > This patch permits to use GPIOs to control the CTS/RTS/DTR/DSR/DCD/RI
> > > > signals.
> > > >
> > > > Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
> > > > ---
> > > > .../devicetree/bindings/serial/omap_serial.txt | 9 +
> > > > drivers/tty/serial/Kconfig | 1 +
> > > > drivers/tty/serial/omap-serial.c | 168 +++++++++++++++++++-
> > > > 3 files changed, 171 insertions(+), 7 deletions(-)
> > >
> > > Would we rather move introducing new features to 8250_omap.c rather
> > > than doing that to omap-serial and keep feature creeping it such that
> > > we wont ever be able to switch to 8250_omap ?
> >
> > Yes please. Also, do we really want to allow mapping
> > random GPIO pins to the UART driver? I guess it would be
>
> See drivers/tty/serial/serial_mctrl_gpio.[ch], these are used for UARTs
> on SoCs with enough GPIOs available whose UART don't have full Modem
> signals. It's pretty handy for BT, GSM, LTE, whatever type of modem-like
> device.
OK
Tony
next prev parent reply other threads:[~2015-05-22 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 12:16 [PATCH] tty: serial: omap: use mctrl_gpio helpers yegorslists
2015-05-22 15:34 ` Nishanth Menon
2015-05-22 16:52 ` Tony Lindgren
2015-05-22 17:38 ` Felipe Balbi
2015-05-22 17:54 ` Tony Lindgren [this message]
2015-05-26 7:04 ` Yegor Yefremov
2015-05-27 6:01 ` Sekhar Nori
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=20150522175429.GB10274@atomide.com \
--to=tony@atomide.com \
--cc=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=yegorslists@googlemail.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).