From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Stefan Roese <sr@denx.de>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
Yegor Yefremov <yegorslists@googlemail.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Giulio Benetti <giulio.benetti@micronovasrl.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 2/2 v5] tty/serial/8250: use mctrl_gpio helpers
Date: Tue, 11 Jun 2019 15:44:15 +0300 [thread overview]
Message-ID: <20190611124415.GT9224@smile.fi.intel.com> (raw)
In-Reply-To: <20190611105603.4435-2-sr@denx.de>
On Tue, Jun 11, 2019 at 12:56:03PM +0200, Stefan Roese wrote:
> From: Yegor Yefremov <yegorslists@googlemail.com>
>
> This patch permits the usage for GPIOs to control
> the CTS/RTS/DTR/DSR/DCD/RI signals.
> static inline void serial8250_out_MCR(struct uart_8250_port *up, int value)
> {
> serial_out(up, UART_MCR, value);
> +
> + if (up->gpios) {
> + int mctrl_gpio = 0;
> +
> + if (value & UART_MCR_RTS)
> + mctrl_gpio |= TIOCM_RTS;
> + if (value & UART_MCR_DTR)
> + mctrl_gpio |= TIOCM_DTR;
> +
> + mctrl_gpio_set(up->gpios, mctrl_gpio);
> + }
> }
>
> static inline int serial8250_in_MCR(struct uart_8250_port *up)
> {
> - return serial_in(up, UART_MCR);
> + int mctrl;
> +
> + mctrl = serial_in(up, UART_MCR);
> +
> + if (up->gpios) {
> + int mctrl_gpio = 0;
> +
> + /* save current MCR values */
> + if (mctrl & UART_MCR_RTS)
> + mctrl_gpio |= TIOCM_RTS;
> + if (mctrl & UART_MCR_DTR)
> + mctrl_gpio |= TIOCM_DTR;
> +
> + mctrl_gpio = mctrl_gpio_get_outputs(up->gpios, &mctrl_gpio);
> + if (mctrl_gpio & TIOCM_RTS)
> + mctrl |= UART_MCR_RTS;
> + else
> + mctrl &= ~UART_MCR_RTS;
> +
> + if (mctrl_gpio & TIOCM_DTR)
> + mctrl |= UART_MCR_DTR;
> + else
> + mctrl &= ~UART_MCR_DTR;
> + }
> +
> + return mctrl;
> }
These are using OR logic with potentially volatile data. Shouldn't we mask
unused bits in UART_MCR in case of up->gpios != NULL?
> + if (up->gpios == 0)
This is type inconsistency with this check as far as I understand.
I guess you have to do either (up->gpios == NULL), or (!up->gpios).
> ret = 0;
+ Blank line.
> + if (up->gpios)
> + return mctrl_gpio_get(up->gpios, &ret);
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2019-06-11 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 10:56 [PATCH 1/2 v5] serial: mctrl_gpio: Check if GPIO property exisits before requesting it Stefan Roese
2019-06-11 10:56 ` [PATCH 2/2 v5] tty/serial/8250: use mctrl_gpio helpers Stefan Roese
2019-06-11 12:44 ` Andy Shevchenko [this message]
2019-06-11 14:02 ` Stefan Roese
2019-06-11 14:48 ` Andy Shevchenko
2019-06-12 8:13 ` Stefan Roese
2019-06-12 9:16 ` Andy Shevchenko
2019-06-13 5:32 ` Stefan Roese
2019-06-13 11:05 ` Andy Shevchenko
2019-06-18 7:49 ` Greg Kroah-Hartman
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=20190611124415.GT9224@smile.fi.intel.com \
--to=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=mika.westerberg@linux.intel.com \
--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).