Re: [PATCH v2] OHCI: add a quirk for ULi M5237 blocking on reset

2014-12-23 Thread Nikita Yushchenko
> In my case root cause was elsewhere - USB port that I thought was driven > by ULI, actually was not. And ULI's builtin OHCI was not > hardware-enabled (but still was available on bus). I workarounded it by > masking entire device in platform-specific quirk. For reference, here is the patch that

Re: [PATCH v2] OHCI: add a quirk for ULi M5237 blocking on reset

2014-12-22 Thread Nikita Yushchenko
23.12.2014 08:36, Arseny Solokha пишет: >> On Sat, 6 Dec 2014, Arseny Solokha wrote: >> >>> From: Arseny Solokha >>> >>> Commit 8dccddbc2368 ("OHCI: final fix for NVIDIA problems (I hope)") >>> introduced into 3.1.9 broke boot on e.g. Freescale P2020DS development >>> board. The code path that was

Re: [PATCH v2] OHCI: add a quirk for ULi M5237 blocking on reset

2014-12-22 Thread Arseny Solokha
> On Sat, 6 Dec 2014, Arseny Solokha wrote: > >> From: Arseny Solokha >> >> Commit 8dccddbc2368 ("OHCI: final fix for NVIDIA problems (I hope)") >> introduced into 3.1.9 broke boot on e.g. Freescale P2020DS development >> board. The code path that was previously specific to NVIDIA controllers >>

Re: [PATCH v2] OHCI: add a quirk for ULi M5237 blocking on reset

2014-12-06 Thread Alan Stern
On Sat, 6 Dec 2014, Arseny Solokha wrote: > From: Arseny Solokha > > Commit 8dccddbc2368 ("OHCI: final fix for NVIDIA problems (I hope)") > introduced into 3.1.9 broke boot on e.g. Freescale P2020DS development > board. The code path that was previously specific to NVIDIA controllers > had then

[PATCH v2] OHCI: add a quirk for ULi M5237 blocking on reset

2014-12-05 Thread Arseny Solokha
From: Arseny Solokha Commit 8dccddbc2368 ("OHCI: final fix for NVIDIA problems (I hope)") introduced into 3.1.9 broke boot on e.g. Freescale P2020DS development board. The code path that was previously specific to NVIDIA controllers had then become taken for all chips. However, the M5237 install