linux-serial.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: linux-serial@vger.kernel.org,
	Vineet Gupta <Vineet.Gupta1@synopsys.com>,
	Kevin Cernekee <cernekee@gmail.com>, Jiri Slaby <jslaby@suse.com>,
	Rob Herring <robh@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v2 1/2] serial: 8250_early: do not save and restore IER in write callback
Date: Wed, 28 Oct 2015 10:36:37 -0400	[thread overview]
Message-ID: <5630DD75.30805@hurleysoftware.com> (raw)
In-Reply-To: <CAK7LNASy6Y_Jqqw6JhTdxMy7Nc35PytWSeqHCM8UybrVYp1mnw@mail.gmail.com>

On 10/27/2015 11:27 PM, Masahiro Yamada wrote:
> Hi Peter,
> 
> 2015-10-27 22:54 GMT+09:00 Peter Hurley <peter@hurleysoftware.com>:
>> Hi Masahiro,
>>
>> On 10/24/2015 12:17 AM, Masahiro Yamada wrote:
>>> The IER has already been masked in early_serial8250_setup(), there is
>>> no reason to save and restore it every time early_serial8250_write()
>>> is called.
>>>
>>> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
>>> ---
>>>
>>>  drivers/tty/serial/8250/8250_early.c | 12 ------------
>>>  1 file changed, 12 deletions(-)
>>>
>>> diff --git a/drivers/tty/serial/8250/8250_early.c b/drivers/tty/serial/8250/8250_early.c
>>> index 7aff3d8..559b681 100644
>>> --- a/drivers/tty/serial/8250/8250_early.c
>>> +++ b/drivers/tty/serial/8250/8250_early.c
>>> @@ -99,20 +99,8 @@ static void __init early_serial8250_write(struct console *console,
>>>  {
>>>       struct earlycon_device *device = console->data;
>>>       struct uart_port *port = &device->port;
>>> -     unsigned int ier;
>>> -
>>> -     /* Save the IER and disable interrupts preserving the UUE bit */
>>> -     ier = serial8250_early_in(port, UART_IER);
>>> -     if (ier)
>>> -             serial8250_early_out(port, UART_IER, ier & UART_IER_UUE);
>>>
>>>       uart_console_write(port, s, count, serial_putc);
>>
>>
>>
>>> -
>>> -     /* Wait for transmitter to become empty and restore the IER */
>>> -     wait_for_xmitr(port);
>>
>> This wait_for_xmitr() change needs to be in patch 2/2.
>>
> 
> 
> Why?

Because if someone reports a regression bisected to this commit,
we won't know if the regression is because we're not saving/restoring IER
or because the transmitter is still running.

Regards,
Peter Hurley

  reply	other threads:[~2015-10-28 14:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-24  4:17 [PATCH v2 0/2] serial: 8250_early: simplify serial_putc() Masahiro Yamada
2015-10-24  4:17 ` [PATCH v2 1/2] serial: 8250_early: do not save and restore IER in write callback Masahiro Yamada
2015-10-27 13:54   ` Peter Hurley
2015-10-28  3:27     ` Masahiro Yamada
2015-10-28 14:36       ` Peter Hurley [this message]
2015-10-29  5:21         ` Masahiro Yamada
2015-10-24  4:17 ` [PATCH v2 2/2] serial: 8250_early: squash wait_for_xmitr() into serial_putc() Masahiro Yamada

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=5630DD75.30805@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=cernekee@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=yamada.masahiro@socionext.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).