diff options
author | Wang YanQing <udknight@gmail.com> | 2013-03-05 23:16:48 +0800 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-03-15 13:27:35 -0700 |
commit | 8b5c913f7ee6464849570bacb6bcd9ef0eaf7dce (patch) | |
tree | a6e5606366198d24be5ece4bce3bfe0ae677716d /fs/xfs/xfs_sysctl.c | |
parent | 503bded92da283b2f31d87e054c4c6d30c3c2340 (diff) | |
download | op-kernel-dev-8b5c913f7ee6464849570bacb6bcd9ef0eaf7dce.zip op-kernel-dev-8b5c913f7ee6464849570bacb6bcd9ef0eaf7dce.tar.gz |
serial: 8250_pci: Add WCH CH352 quirk to avoid Xscale detection
The code in 8250.c for detecting ARM/XScale UARTs says:
* Try writing and reading the UART_IER_UUE bit (b6).
* If it works, this is probably one of the Xscale platform's
* internal UARTs.
If the above passes, it then goes on to:
* It's an Xscale.
* We'll leave the UART_IER_UUE bit set to 1 (enabled).
However, the CH352 uses the UART_IER_UUE as the LOWPOWER function,
so it is readable and writable. According to the datasheet:
"LOWPOWER:When the bit is 1, close the internal benchmark
clock of serial port to set into low-power status.
So it essentially gets mis-detected as Xscale, and gets
powered down in the process. The device in question where
this was seen is listed by lspci as:
Serial controller: Device 4348:3253 (rev 10) (prog-if 02 [16550])
Re-using the 353 quirk which just sets flags to fixed and type
to 16550 is suitable for fixing the 352 as well.
Signed-off-by: Wang YanQing <udknight@gmail.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/xfs/xfs_sysctl.c')
0 files changed, 0 insertions, 0 deletions