USB controllers & peripherals

PCI OHCI host-controller class

PCI OHCI provides a standardized USB 1.1 controller path for low- and full-speed peripherals.

On this page
  1. Overview & identity
  2. Driver & binding
  3. Firmware
  4. Read-only diagnostics
  5. Limitations & related issues
  6. References

Overview & identity

Programming interface 0c0310 is an OHCI class observation. It identifies controller architecture and does not establish an exact board or the driver used by a connected keyboard, modem or audio adapter.

This is an explicit class, transport or driver-context profile. It is not an exact numeric product match.

A numeric match establishes a candidate family within the reviewed evidence. Marketing names, board variants, subsystem conditions and successful operation remain separate questions.

Driver & binding

The PCI class table selects ohci_pci; controller code is provided by ohci_hcd. The source applies PCI-specific quirks during initialization, which is distinct from USB interface probing.

  • ohci_pci — kernel driver/module candidate
  • ohci_hcd — kernel driver/module candidate

Detected, bound, operational: learn the difference

Firmware

No host payload established here

No external firmware filename was established in the checked driver path. This does not describe firmware stored inside the device.

Inspect firmware packaging on your distribution

Read-only diagnostics

Run one displayed command at a time. Replace uppercase placeholders with the affected device, interface or module from your own output. Commands are never executed here. Read-only output can still contain private identifiers.

Inspect the PCI function and binding

lspci -nnk -s BDF

Replace BDF with the complete address, for example 0000:00:14.0. This read-only query needs pciutils and normally no sudo. “Kernel driver in use” is observed binding; “Kernel modules” lists candidates.

Inspect interfaces and negotiated speed

lsusb -t

This read-only usbutils query normally needs no sudo. Driver belongs to the displayed interface, while speed is the negotiated connection. Other interfaces of the same physical device may use other drivers.

Limitations & related issues

A low-/full-speed connection is expected here. USB 2 or 3 branding on the physical device does not mean this controller can negotiate high-speed or SuperSpeed operation.

These guides are linked for relevant observations, not as known defects of every device in this family.

Choose a hardware diagnostic workflow · Inspect a log excerpt in Fix Lab

References

Source review records a checked implementation or document, not a reproduced hardware test. Version-specific tables do not establish a minimum kernel or guaranteed operation.