From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Alex Williamson <alex.williamson@hp.com>
Cc: David Vrabel <dvrabel@arcom.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: serial: 8250 fails to detect Exar XR16L2551 correctly
Date: Thu, 14 Jul 2005 14:46:04 +0100 [thread overview]
Message-ID: <20050714144604.A7314@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1121274296.4334.58.camel@tdi>; from alex.williamson@hp.com on Wed, Jul 13, 2005 at 11:04:56AM -0600
On Wed, Jul 13, 2005 at 11:04:56AM -0600, Alex Williamson wrote:
> On Mon, 2005-07-11 at 15:17 -0600, Alex Williamson wrote:
> > No, I think this is a problem with the broken A2 UARTs getting
> > confused in serial8250_set_sleep(). If I remove either UART_CAP_SLEEP
> > or UART_CAP_EFR from the capabilities list for this UART, it behaves
> > normally. Also, just commenting out the UART_CAP_EFR chunks of
> > set_sleep make it behave. I'll ping Exar for more data. Thanks,
>
> Hi Russell,
>
> I don't know enough about the extended UART programming model, but I
> notice that when UART_CAP_EFR and UART_CAP_SLEEP are set on a UART, we
> set the UART_IERX_SLEEP bit in the UART_IER immediately after it's found
> and configured.
Ah, I see what's happening. We're detecting the port and doing the
autoconfig. Then we're checking to see if it's the console, and if
not putting it into low power mode.
Then we try to register the console, which may result in this UART
becoming a console. So now we have a console which is in low power
mode. Bad bad bad. No cookie for the serial layer today.
> Are there known working configs where a UART w/ EFR and SLEEP are
> able to be used as a serial console?
No idea - I'm completely reliant on other folk to report problems
with the 8250 driver with their random versions of UARTs which are
out in the field. I only have 16450, 16550A and 16750 UARTs here.
Hmm, I need to consider killing register_serial() and the associated
code in serial_core.c earlier so I can sanely fix this problem. I
think it's time to give the remaining register_serial() users an
extra push... I haven't seen _any_ activity from the remaining users,
so I might have to take the attitude that "if they don't care, I don't
care about breaking their code" which would be rather shameful as far
as the users go. (but hey, user pressure might wake up the maintainers.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-07-14 13:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 14:19 serial: 8250 fails to detect Exar XR16L2551 correctly David Vrabel
2005-07-06 18:57 ` Russell King
2005-07-06 20:20 ` Alex Williamson
2005-07-07 13:20 ` David Vrabel
2005-07-11 19:00 ` Alex Williamson
2005-07-11 19:46 ` Russell King
2005-07-11 20:00 ` Alex Williamson
2005-07-11 20:17 ` Russell King
2005-07-11 21:17 ` Alex Williamson
2005-07-13 17:04 ` Alex Williamson
2005-07-13 18:03 ` Alex Williamson
2005-07-14 14:40 ` David Vrabel
2005-07-14 13:46 ` Russell King [this message]
2005-07-15 20:39 ` Alex Williamson
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=20050714144604.A7314@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=alex.williamson@hp.com \
--cc=dvrabel@arcom.com \
--cc=linux-kernel@vger.kernel.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