From: Mark Lokowich <lokowich-3mWahjwryh5BDgjK7y7TUQ@public.gmane.org>
To: Kevin Hilman <khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org>
Cc: davinci-linux-open-source
<davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org>,
linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/1] Serial: DaVinci: Revert double IIR test
Date: Mon, 11 Aug 2008 14:43:17 -0500 [thread overview]
Message-ID: <48A09655.3020009@acdstar.com> (raw)
In-Reply-To: <48A077D6.1090205-6RQC9ztksjxg9hUCZPvPmw@public.gmane.org>
Philip Balister wrote:
> Kevin Hilman wrote:
>> Mark Lokowich <lokowich-3mWahjwryh5BDgjK7y7TUQ@public.gmane.org> writes:
>>
>>> Revert double IIR test in 8250 driver
>>>
>>
>> Can you give a more detailed description of what the problem is that
>> is being fixed?
>
> Without this patch, serial console behavior is strange. You type and
> nothing is echoed and you hit return and things happen. It feels like
> two processes are grabbing input.
>
> I think someone posted a more technical description, but I couldn't
> find it quickly.
>
> Philip
>
This section of the driver is a test for faulty 16650
implementations that require a backup timer. The patch reverts the
change that compares two states (instead of one, as in 2.6.25.2) of
the IIR to determine if the workaround is required. The DaVinci
UART does not need the backup timer, but the double conditional
passed, enabling the timer and causing interrupt handling errors on
the console and other UARTS.
Mark
>
>> This is in the generic 8250 driver so will affect all platforms. For
>> this to be accepted, it should be discussed on linux-serial[1]
>>
>> Kevin
>>
>>> Acked-by: Jaswinder Singh <jaswinder-TJMEihSVCElBDgjK7y7TUQ@public.gmane.org>
>>> ---
>>> --- linux-2.6/drivers/serial/8250.c
>>> +++ linux-2.6-vanilla/drivers/serial/8250.c
>>> @@ -1867,7 +1867,6 @@
>>> }
>>>
>>> if (is_real_interrupt(up->port.irq)) {
>>> - unsigned char iir1;
>>> /*
>>> * Test for UARTs that do not reassert THRE when the
>>> * transmitter is idle and the interrupt has already
>>> @@ -1881,7 +1880,7 @@
>>> wait_for_xmitr(up, UART_LSR_THRE);
>>> serial_out_sync(up, UART_IER, UART_IER_THRI);
>>> udelay(1); /* allow THRE to set */
>>> - iir1 = serial_in(up, UART_IIR);
>>> + serial_in(up, UART_IIR);
>>> serial_out(up, UART_IER, 0);
>>> serial_out_sync(up, UART_IER, UART_IER_THRI);
>>> udelay(1); /* allow a working UART time to re-assert THRE */
>>> @@ -1894,7 +1893,7 @@
>>> * If the interrupt is not reasserted, setup a timer to
>>> * kick the UART on a regular basis.
>>> */
>>> - if (!(iir1 & UART_IIR_NO_INT) && (iir & UART_IIR_NO_INT)) {
>>> + if (iir & UART_IIR_NO_INT) {
>>> pr_debug("ttyS%d - using backup timer\n", port->line);
>>> up->timer.function = serial8250_backup_timeout;
>>> up->timer.data = (unsigned long)up;
>>>
>>>
>>> _______________________________________________
>>> Davinci-linux-open-source mailing list
>>> Davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org
>>> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>>
>>
>> [1] From MAINTAINERS:
>>
>> 8250/16?50 (AND CLONE UARTS) SERIAL DRIVER
>> L: linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
>> W: http://serial.sourceforge.net
>> S: Orphan
>> _______________________________________________
>> Davinci-linux-open-source mailing list
>> Davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org
>> http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
>>
next parent reply other threads:[~2008-08-11 19:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48A04E34.9040306@acdstar.com>
[not found] ` <87y733eb7n.fsf@deeprootsystems.com>
[not found] ` <48A077D6.1090205@balister.org>
[not found] ` <48A077D6.1090205-6RQC9ztksjxg9hUCZPvPmw@public.gmane.org>
2008-08-11 19:43 ` Mark Lokowich [this message]
2008-08-11 21:47 ` [PATCH 1/1] Serial: DaVinci: Revert double IIR test Kevin Hilman
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=48A09655.3020009@acdstar.com \
--to=lokowich-3mwahjwryh5bdgjk7y7tuq@public.gmane.org \
--cc=davinci-linux-open-source-VycZQUHpC/PFrsHnngEfi1aTQe2KTcn/@public.gmane.org \
--cc=khilman-1D3HCaltpLuhEniVeURVKkEOCMrvLtNR@public.gmane.org \
--cc=linux-serial-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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