From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-serial@vger.kernel.org, linux-gpio@vger.kernel.org,
Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Sascha Weisenberger <sascha.weisenberger@siemens.com>
Subject: Re: [PATCH 1/8] serial: exar: Preconfigure xr17v35x MPIOs as output
Date: Fri, 26 May 2017 20:38:14 +0200 [thread overview]
Message-ID: <20170526183814.GD16490@kroah.com> (raw)
In-Reply-To: <9bb8d972-6535-1611-8fa7-f5fe89760531@siemens.com>
On Fri, May 26, 2017 at 03:04:26PM +0200, Jan Kiszka wrote:
> Greg,
>
> On 2017-05-13 09:28, Jan Kiszka wrote:
> > This is the safe default for GPIOs with unknown external wiring.
> >
> > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > ---
> > drivers/tty/serial/8250/8250_exar.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/tty/serial/8250/8250_exar.c b/drivers/tty/serial/8250/8250_exar.c
> > index 1270ff163f63..b4fa585156c7 100644
> > --- a/drivers/tty/serial/8250/8250_exar.c
> > +++ b/drivers/tty/serial/8250/8250_exar.c
> > @@ -177,13 +177,13 @@ static void setup_gpio(u8 __iomem *p)
> > writeb(0x00, p + UART_EXAR_MPIOLVL_7_0);
> > writeb(0x00, p + UART_EXAR_MPIO3T_7_0);
> > writeb(0x00, p + UART_EXAR_MPIOINV_7_0);
> > - writeb(0x00, p + UART_EXAR_MPIOSEL_7_0);
> > + writeb(0xff, p + UART_EXAR_MPIOSEL_7_0);
> > writeb(0x00, p + UART_EXAR_MPIOOD_7_0);
> > writeb(0x00, p + UART_EXAR_MPIOINT_15_8);
> > writeb(0x00, p + UART_EXAR_MPIOLVL_15_8);
> > writeb(0x00, p + UART_EXAR_MPIO3T_15_8);
> > writeb(0x00, p + UART_EXAR_MPIOINV_15_8);
> > - writeb(0x00, p + UART_EXAR_MPIOSEL_15_8);
> > + writeb(0xff, p + UART_EXAR_MPIOSEL_15_8);
> > writeb(0x00, p + UART_EXAR_MPIOOD_15_8);
> > }
> >
> >
>
> Please drop from this tty-next, it may break Commtech adapters. I have
> an update ready.
>
> I may also send a fix on top if that is preferred, just let me know.
I need a fixup patch, I can't drop a patch, only revert it.
thanks,
greg k-h
next prev parent reply other threads:[~2017-05-26 18:38 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 7:28 [PATCH 0/8] serial/gpio: exar: Fixes and support for IOT2000 Jan Kiszka
2017-05-13 7:28 ` [PATCH 1/8] serial: exar: Preconfigure xr17v35x MPIOs as output Jan Kiszka
2017-05-22 15:38 ` Linus Walleij
2017-05-26 13:04 ` Jan Kiszka
2017-05-26 14:22 ` Andy Shevchenko
2017-05-26 18:38 ` Greg Kroah-Hartman [this message]
2017-05-13 7:29 ` [PATCH 2/8] gpio: exar: Fix passing in of parent PCI device Jan Kiszka
2017-05-13 13:25 ` Andy Shevchenko
2017-05-14 8:11 ` Jan Kiszka
2017-05-13 7:29 ` [PATCH 3/8] gpio: exar: Allocate resources on behalf of the platform device Jan Kiszka
2017-05-13 13:26 ` Andy Shevchenko
2017-05-22 15:39 ` Linus Walleij
2017-05-13 7:29 ` [PATCH 4/8] gpio: exar: Fix iomap request Jan Kiszka
2017-05-13 13:28 ` Andy Shevchenko
2017-05-13 7:29 ` [PATCH 5/8] gpio: exar: Fix reading of directions and values Jan Kiszka
2017-05-13 13:36 ` Andy Shevchenko
2017-05-18 5:20 ` Jan Kiszka
2017-05-18 10:11 ` Andy Shevchenko
2017-05-18 10:16 ` Jan Kiszka
2017-05-18 10:23 ` Andy Shevchenko
2017-05-18 10:28 ` Jan Kiszka
2017-05-13 7:29 ` [PATCH 6/8] serial: uapi: Add support for bus termination Jan Kiszka
2017-05-13 7:29 ` [PATCH 7/8] gpio-exar/8250-exar: Make set of exported GPIOs configurable Jan Kiszka
2017-05-13 13:50 ` Andy Shevchenko
2017-05-13 7:29 ` [PATCH 8/8] serial: exar: Add support for IOT2040 device Jan Kiszka
2017-05-13 13:54 ` Andy Shevchenko
2017-05-18 5:06 ` Jan Kiszka
2017-05-18 10:17 ` Andy Shevchenko
2017-05-18 10:37 ` Jan Kiszka
2017-05-18 10:56 ` Andy Shevchenko
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=20170526183814.GD16490@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andy.shevchenko@gmail.com \
--cc=gnurou@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sascha.weisenberger@siemens.com \
--cc=sudip.mukherjee@codethink.co.uk \
/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