From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Stefan Roese <sr@denx.de>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Yegor Yefremov <yegorslists@googlemail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Giulio Benetti <giulio.benetti@micronovasrl.com>
Subject: Re: [PATCH 2/3 v6] serial: 8250: Add MSR/MCR TIOCM conversion wrapper functions
Date: Thu, 13 Jun 2019 21:32:29 +0300 [thread overview]
Message-ID: <20190613183229.GS2640@lahna.fi.intel.com> (raw)
In-Reply-To: <20190613154542.32438-2-sr@denx.de>
On Thu, Jun 13, 2019 at 05:45:41PM +0200, Stefan Roese wrote:
> This patch adds wrapper functions to convert MSR <-> TIOCM and also
> MCR <-> TIOCM. These functions are used now in serial8250_do_set_mctrl()
> and serial8250_do_get_mctrl().
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Cc: Mika Westerberg <mika.westerberg@linux.intel.com>
Reviewed-by: Mika Westerberg <mika.westerberg@linux.intel.com>
next prev parent reply other threads:[~2019-06-13 18:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 15:45 [PATCH 1/3 v6] serial: mctrl_gpio: Check if GPIO property exisits before requesting it Stefan Roese
2019-06-13 15:45 ` [PATCH 2/3 v6] serial: 8250: Add MSR/MCR TIOCM conversion wrapper functions Stefan Roese
2019-06-13 17:07 ` Andy Shevchenko
2019-06-13 18:32 ` Mika Westerberg [this message]
2019-06-13 15:45 ` [PATCH 3/3 v6] tty/serial/8250: use mctrl_gpio helpers Stefan Roese
2019-06-13 17:12 ` Andy Shevchenko
2019-06-13 18:34 ` Mika Westerberg
2019-06-17 9:40 ` Yegor Yefremov
2019-06-17 9:51 ` Yegor Yefremov
2019-06-17 12:42 ` Stefan Roese
2019-06-17 12:51 ` Yegor Yefremov
2019-06-13 17:08 ` [PATCH 1/3 v6] serial: mctrl_gpio: Check if GPIO property exisits before requesting it Andy Shevchenko
2019-06-14 9:04 ` Yegor Yefremov
2019-06-14 9:29 ` Stefan Roese
2019-06-14 9:38 ` Yegor Yefremov
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=20190613183229.GS2640@lahna.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=giulio.benetti@micronovasrl.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sr@denx.de \
--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).