[coreboot] w83627 uart port is not workable with coreboot in linux

Mon Jul 25 10:34:58 CEST 2016

Hi Zoran

TTYS1 is also not workable. I also change io resource from 3f8 to 3e8  irq
from 4 to 5. but result is the same.

Thank you

2016-07-25 13:57 GMT+08:00 Zoran Stojsavljevic <
zoran.stojsavljevic at gmail.com>:

> Hello Chen,
>
> I see. Also learning, reading and trying to get to the root of the problem.
>
> > [    1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200)
> is a 16550A
> > [    1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud =
> 115200) is a 16550A
>
> Please, try to experiment with ttyS1. But I guess, you already know what I
> just wrote. Maybe this also can help:
> http://forums.debian.net/viewtopic.php?f=7&t=111355
>
> Zoran
>
> On Mon, Jul 25, 2016 at 7:08 AM, cheng yichen <blessyichen at gmail.com>
> wrote:
>
>> Hi Zoran
>>
>> The ttyS0 is superIo uart. Because I add uart asl code in coreboot system
>> will show "00:05: ttyS0"
>> If I remove asl code system will show "serial8250:ttty"    Thank you
>>
>> 2016-07-25 12:10 GMT+08:00 Zoran Stojsavljevic <
>> zoran.stojsavljevic at gmail.com>:
>>
>>> > home# dmesg | grep -i tty
>>> > [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic
>>> root=UUID=b2b7f7fa-b1db-4e97-
>>> > 941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet splash
>>> vt.handoff=7
>>> > [    0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic
>>> root=UUID=b2b7f7fa-b1db-
>>> > 4e97-941f-8aaee291f3dc ro console=tty1 console=ttyS0,115200n8 quiet
>>> splash vt.handoff=7
>>> > [    0.000000] console [tty1] enabled
>>> > [    0.000000] console [ttyS0] enabled
>>> > [    1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud =
>>> 115200) is a 16550A
>>> > [    1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud =
>>> 115200) is a 16550A
>>> > [    3.412478] fbcon: Remapping primary device, fb1, to tty 1-63
>>> > [   44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice.
>>> > [   44.380198] systemd[1]: Created slice system-getty.slice.
>>> _______
>>>
>>> Hello Cheng,
>>>
>>> Please, try to do the following: lspci -vv (to find your serial on
>>> PCIe), then try to remap your IRQs, to see if this will somehow work.
>>>
>>> Example:
>>> setserial /dev/ttyS0 port 0xd800 UART 16550A irq 5
>>> setserial /dev/ttyS0 -av
>>> /dev/ttyS0, Line 0, UART: 16550A, Port: 0xd800, IRQ: 5
>>>         Baud_base: 115200, close_delay: 5000, divisor: 0
>>>         closing_wait: 37856
>>>         Flags: spd_normal skip_test
>>>
>>> Something like described on this web pointer:
>>> https://forums.gentoo.org/viewtopic-t-249041-start-0.html
>>>
>>> Please, report your attempts/results here.
>>>
>>> Thank you,
>>> Zoran
>>>
>>> On Mon, Jul 25, 2016 at 4:33 AM, cheng yichen <blessyichen at gmail.com>
>>> wrote:
>>>
>>>> Hi all
>>>>
>>>> After i follow kontron/ktqm77 setting. I can't solve the issue.
>>>> I try to change iqr(for com1) to 5 or 6. but system can't print linux
>>>> message and minicom is not workable.
>>>>
>>>>
>>>>
>>>> dump from superiotool
>>>> Found Winbond W83627DHG-P/-PT (id=0xb0, rev=0x73) at 0x2e
>>>> Register dump:
>>>> idx 02 20 21 22 23 24 25 26  27 28 29 2a 2b 2c 2d 2e  2f
>>>> val ff b0 73 ff 00 42 00 00  ff 50 80 00 00 eb 21 00  ff
>>>> def 00 b0 NA ff 00 MM 00 MM  RR 50 00 00 RR e2 21 00  00
>>>> LDN 0x00 (Floppy)
>>>> idx 30 60 61 70 74 f0 f1 f2  f4 f5
>>>> val 01 03 f0 06 02 8e 00 ff  00 00
>>>> def 01 03 f0 06 02 8e 00 ff  00 00
>>>> LDN 0x01 (Parallel port)
>>>> idx 30 60 61 70 74 f0
>>>> val 01 03 78 07 04 3f
>>>> def 01 03 78 07 04 3f
>>>> LDN 0x02 (COM1)
>>>> idx 30 60 61 70 f0
>>>> val 01 03 f8 04 40
>>>> def 01 03 f8 04 00
>>>> LDN 0x03 (COM2)
>>>> idx 30 60 61 70 f0 f1
>>>> val 01 02 f8 03 40 00
>>>> def 01 02 f8 03 00 00
>>>> LDN 0x05 (Keyboard)
>>>>
>>>>
>>>> dump from dmesg
>>>>
>>>> home# dmesg | grep -i tty
>>>> [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic
>>>> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1
>>>> console=ttyS0,115200n8 quiet splash vt.handoff=7
>>>> [    0.000000] Kernel command line:
>>>> BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic
>>>> root=UUID=b2b7f7fa-b1db-4e97-941f-8aaee291f3dc ro console=tty1
>>>> console=ttyS0,115200n8 quiet splash vt.handoff=7
>>>> [    0.000000] console [tty1] enabled
>>>> [    0.000000] console [ttyS0] enabled
>>>> [    1.637664] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200)
>>>> is a 16550A
>>>> [    1.658835] serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud =
>>>> 115200) is a 16550A
>>>> [    3.412478] fbcon: Remapping primary device, fb1, to tty 1-63
>>>> [   44.378835] systemd[1]: Created slice system-serial\x2dgetty.slice.
>>>> [   44.380198] systemd[1]: Created slice system-getty.slice.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> 2016-07-22 20:24 GMT+08:00 Kyösti Mälkki <kyosti.malkki at gmail.com>:
>>>>
>>>>> On Fri, Jul 22, 2016 at 1:14 PM, cheng yichen <blessyichen at gmail.com>
>>>>> wrote:
>>>>> > Hi all
>>>>> >
>>>>> > My platform is braswell SOC with W83627dhg superIO. In post stage I
>>>>> can get
>>>>> > debug message over w83627 uart1(3f8/irq4). but after boot to linux,
>>>>> uart
>>>>> > port is not woarkable. I test the function by minicom but I can't
>>>>> receive
>>>>> > and send data. I can get uart information by dmesg command.
>>>>> > How to initial it in corebooot?
>>>>>
>>>>> Does not sound like a coreboot issue to me.
>>>>>
>>>>> Do you have CTS/RTS hardware handshake disabled in minicom
>>>>> configuration? If you directed kernel console to serial port, you
>>>>> should not (cannot) use the port for user apps.
>>>>>
>>>>> HTH,
>>>>> Kyösti
>>>>>
>>>>
>>>>
>>>> --
>>>> coreboot mailing list: coreboot at coreboot.org
>>>> https://www.coreboot.org/mailman/listinfo/coreboot
>>>>
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.coreboot.org/pipermail/coreboot/attachments/20160725/d4063ea3/attachment.html>