* Loongson3 PCI/EHCI
@ 2021-12-07 16:29 Thomas Bogendoerfer
2021-12-08 1:49 ` Huacai Chen
0 siblings, 1 reply; 2+ messages in thread
From: Thomas Bogendoerfer @ 2021-12-07 16:29 UTC (permalink / raw)
To: linux-mips
Hi,
I'm getting lots of
[ 2.940587] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.946478] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.952374] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.958270] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.964166] pci 0000:00:04.1: EHCI: unrecognized capability ff
[ 2.970062] pci 0000:00:04.1: EHCI: unrecognized capability ff
while booting on a Loongson-3A R4 (Loongson-3A4000) @ 1800MHz system.
What I'm missing ?
I'm also seeing
[ 1.222546] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 m
ay corrupt adjacent RW1C bits
[ 1.232314] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 m
ay corrupt adjacent RW1C bits
which look suspicous...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Loongson3 PCI/EHCI
2021-12-07 16:29 Loongson3 PCI/EHCI Thomas Bogendoerfer
@ 2021-12-08 1:49 ` Huacai Chen
0 siblings, 0 replies; 2+ messages in thread
From: Huacai Chen @ 2021-12-08 1:49 UTC (permalink / raw)
To: Thomas Bogendoerfer; +Cc: open list:MIPS
Hi, Thomas,
On Wed, Dec 8, 2021 at 8:58 AM Thomas Bogendoerfer
<tsbogend@alpha.franken.de> wrote:
>
> Hi,
>
> I'm getting lots of
>
> [ 2.940587] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 2.946478] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 2.952374] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 2.958270] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 2.964166] pci 0000:00:04.1: EHCI: unrecognized capability ff
> [ 2.970062] pci 0000:00:04.1: EHCI: unrecognized capability ff
>
> while booting on a Loongson-3A R4 (Loongson-3A4000) @ 1800MHz system.
> What I'm missing ?
This is a hardware issue of LS7A bridge.
>
> I'm also seeing
>
> [ 1.222546] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 m
> ay corrupt adjacent RW1C bits
> [ 1.232314] pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 m
> ay corrupt adjacent RW1C bits
>
> which look suspicous...
This can be avoid and I have send a patch, but hasn't accepted yet.
https://lore.kernel.org/linux-pci/20211011074604.854340-2-chenhuacai@loongson.cn/T/#u
Huacai
>
> Thomas.
>
> --
> Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
> good idea. [ RFC1925, 2.3 ]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-12-08 1:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2021-12-07 16:29 Loongson3 PCI/EHCI Thomas Bogendoerfer
2021-12-08 1:49 ` Huacai Chen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox