[Letux-kernel] Status of JZ4780/CI20 upstream support

Maarten ter Huurne maarten at treewalker.org
Tue Jul 9 02:57:11 CEST 2019

On Tuesday, 9 July 2019 00:22:18 CEST Paul Boddie wrote:

> ohci-jz4740.c needs to be brought in from 3.18 (or elsewhere, maybe)
> and included within ohci-hcd.c in a not particularly pleasant
> fashion, but this just seems to be the way things are done with the
> OHCI support.

I removed ohci-jz4740.c from mainline 3 years ago, because it is not 
needed to be able to use the OHCI controller on the JZ47xx SoCs: the 
generic OHCI platform driver can be used instead.

Details can be found in these commits:

commit b071c5d7998a79919e83565ddfb98fdf6fa804bc
Author: Maarten ter Huurne <maarten at treewalker.org>
Date:   Mon Apr 18 20:58:53 2016 +0200

    USB: ohci-jz4740: Remove obsolete driver
    The ohci-platform driver can control the clock, while usb-nop-xceiv
    as the PHY can control the vbus regulator. So this JZ4740-specific
    glue is not needed anymore.
commit 9d1e7875fafc45dbcbe3d816b022aa1f17219f32
Author: Maarten ter Huurne <maarten at treewalker.org>
Date:   Mon Apr 18 20:58:52 2016 +0200

    MIPS: JZ4740: Probe OHCI platform device via DT
    The DT fragment will select the ohci-platform driver, since that can
    handle the JZ4740 OHCI just fine. While I don't have a JZ4740-based
    board with anything connected to the USB host controller, I did test
    the generic OHCI driver successfully on a JZ4770-based board.
    The device is disabled by default; boards that want to use it can
    override the "status" property. The mass-production Qi LB60 boards
    don't use the USB host controller.

Example DeviceTree fragments can be found here:

Define OHCI in SoC file:


Enable OHCI in device file:



More information about the Letux-kernel mailing list