From: Sebastian Frias <sf84@laposte.net>
To: "Måns Rullgård" <mans@mansr.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Magnus Damm <damm@opensource.se>,
linux-serial@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Mason <slash.tmp@free.fr>
Subject: Re: [PATCH] use callbacks to access UART_DLL/UART_DLM
Date: Thu, 17 Dec 2015 19:07:05 +0100 [thread overview]
Message-ID: <5672F9C9.1010601@laposte.net> (raw)
In-Reply-To: <yw1xoadpcbbn.fsf@unicorn.mansr.com>
On 12/17/2015 05:02 PM, Måns Rullgård wrote:
> Sebastian Frias <sf84@laposte.net> writes:
>
>> ---
>> resending as plain-text
>> ---
>> drivers/tty/serial/8250/8250_core.c | 17 +++++++----------
>> 1 file changed, 7 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/tty/serial/8250/8250_core.c
>> b/drivers/tty/serial/8250/8250_core.c
>> index 2c46a21..9ca863c 100644
>> --- a/drivers/tty/serial/8250/8250_core.c
>> +++ b/drivers/tty/serial/8250/8250_core.c
>> @@ -791,22 +791,19 @@ static int size_fifo(struct uart_8250_port *up)
>> */
>> static unsigned int autoconfig_read_divisor_id(struct uart_8250_port *p)
>
> What tree are you working against? Current mainline has that function
> in 8250_port.c.
Sorry, wrong patch. On mainline is about the same, I'll post it.
>
>> {
>> - unsigned char old_dll, old_dlm, old_lcr;
>> + unsigned char old_lcr;
>> unsigned int id;
>> + unsigned int old_dl;
>
> Your patch is messed up. Consider using "git send-email" instead.
I don't know what happened there, thanks for the suggestion.
>
>> old_lcr = serial_in(p, UART_LCR);
>> - serial_out(p, UART_LCR, UART_LCR_CONF_MODE_A);
>> -
>> - old_dll = serial_in(p, UART_DLL);
>> - old_dlm = serial_in(p, UART_DLM);
>>
>> - serial_out(p, UART_DLL, 0);
>> - serial_out(p, UART_DLM, 0);
>> + serial_out(p, UART_LCR, UART_LCR_CONF_MODE_A);
>>
>> - id = serial_in(p, UART_DLL) | serial_in(p, UART_DLM) << 8;
>> + old_dl = serial_dl_read(p);
>> + serial_dl_write(p, 0);
>> + id = serial_dl_read(p);
>> + serial_dl_write(p, old_dl);
>>
>> - serial_out(p, UART_DLL, old_dll);
>> - serial_out(p, UART_DLM, old_dlm);
>> serial_out(p, UART_LCR, old_lcr);
>>
>> return id;
>> --
>
> If you left the blank lines alone, the patch would end up much easier to
> understand. In this diff, some of the lines listed as added or removed
> have actually not changed, and that's not immediately obvious.
>
The old code had some blank lines, which I suppose were there for clarity.
I attempted to follow the same idea.
But I don't mind changing the code as you wish.
next prev parent reply other threads:[~2015-12-17 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 15:45 [PATCH] use callbacks to access UART_DLL/UART_DLM Sebastian Frias
2015-12-17 16:02 ` Måns Rullgård
2015-12-17 18:07 ` Sebastian Frias [this message]
2015-12-17 18:09 ` Måns Rullgård
2015-12-17 19:14 ` Mason
2015-12-18 10:46 ` [PATCH v2] " Sebastian Frias
2015-12-18 16:06 ` Peter Hurley
2015-12-18 16:27 ` Sebastian Frias
2015-12-18 16:34 ` Peter Hurley
2015-12-18 16:35 ` Sebastian Frias
2015-12-18 16:40 ` [PATCH v3] " Sebastian Frias
2015-12-18 16:42 ` Peter Hurley
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=5672F9C9.1010601@laposte.net \
--to=sf84@laposte.net \
--cc=damm@opensource.se \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mans@mansr.com \
--cc=slash.tmp@free.fr \
/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