linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Kleine-Budde <mkl@blackshift.org>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Du Huanpeng <u74147@gmail.com>,
	linux-mips@vger.kernel.org
Cc: zhangj@wch.cn, linux@rempel-privat.de
Subject: Re: loongson ls2k1000: PCIe serial card WCH CH382L not working, maybe ioports problem
Date: Fri, 7 Aug 2020 10:35:40 +0200	[thread overview]
Message-ID: <ad026820-6b57-15a1-a31e-2d8c8829b7f4@blackshift.org> (raw)
In-Reply-To: <88921f60-1458-ab04-2ed9-bce57ce7101d@flygoat.com>


[-- Attachment #1.1: Type: text/plain, Size: 1875 bytes --]

On 8/7/20 10:01 AM, Jiaxun Yang wrote:
>> I'm testing a PCIe card to two uarts (WCH CH382L compatible,
>>           https://item.jd.com/48547850173.html) on a loongson ls2k1000 board.
>>
>> With the card inserted the kernel detects the two new uarts:
>>
>> [    2.060884] pci 0000:00:04.1: EHCI: unrecognized capability ff
>> [    2.066721] pci 0000:00:04.1: EHCI: capability loop?
>> [    2.066745] pci 0000:00:04.1: quirk_usb_early_handoff+0x0/0xa60 took 358764 usecs
>> [    2.074542] pcieport 0000:00:09.0: PME: Signaling with IRQ 2
>> [    2.080651] pcieport 0000:00:0a.0: PME: Signaling with IRQ 3
>> [    2.086648] pcieport 0000:00:0b.0: PME: Signaling with IRQ 4
>> [    2.092616] pcieport 0000:00:0c.0: PME: Signaling with IRQ 5
>> [    2.098579] pcieport 0000:00:0d.0: PME: Signaling with IRQ 6
>> [    2.104557] pcieport 0000:00:0e.0: PME: Signaling with IRQ 7
>> [    2.113728] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
>> [    2.120891] serial 0000:06:00.0: limiting MRRS to 256
>> [    2.126314] 0000:06:00.0: ttyS0 at I/O 0xc0 (irq = 7, base_baud = 115200) is a XR16850
>> [    2.134618] 0000:06:00.0: ttyS1 at I/O 0xc8 (irq = 7, base_baud = 115200) is a XR16850
>> [    2.143130] 1fe00000.serial: ttyS2 at MMIO 0x1fe00000 (irq = 1, base_baud = 7812500) is a 16550A
>> [    2.151946] printk: console [ttyS2] enabled
>> [    2.160255] printk: bootconsole [early0] disabled
>> [    2.170112] [drm] radeon kernel modesetting enabled.
>>
>> However a write to the serial fails:
>> / # echo "hello" >/dev/ttyS0
>> [ 9369.631915] serial 0000:06:00.0: LSR safety check engaged!
>> sh: write error: Input/output error
> 
> I assume you're using my out-of-tree fork to support LS2K.
> I messed with Logic PIO in that fork.
> I'll fix it in mainline, sorry for the issue...

Do you have a tree that we can test?

Marc


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-08-07  8:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-07  3:08 loongson ls2k1000: PCIe serial card WCH CH382L not working, maybe ioports problem Du Huanpeng
2020-08-07  8:01 ` Jiaxun Yang
2020-08-07  8:35   ` Marc Kleine-Budde [this message]
2020-08-07  9:39     ` Jiaxun Yang
2020-08-07  9:43       ` Marc Kleine-Budde
2020-08-12  6:34         ` Marc Kleine-Budde

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=ad026820-6b57-15a1-a31e-2d8c8829b7f4@blackshift.org \
    --to=mkl@blackshift.org \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux@rempel-privat.de \
    --cc=u74147@gmail.com \
    --cc=zhangj@wch.cn \
    /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).