Use the upstream dwc2 driver on arm64
Bug #1900665 reported by
Juerg Haefliger
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| linux-raspi (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| Focal |
Won't Fix
|
Undecided
|
Unassigned | ||
| Groovy |
Won't Fix
|
Undecided
|
Unassigned | ||
| Hirsute |
Won't Fix
|
Undecided
|
Unassigned | ||
| Impish |
Fix Released
|
Undecided
|
Unassigned | ||
| Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
We currently use the dwc_otg driver from raspberrypi on 5.4 and 5.8 armhf and arm64 kernels. That driver supports FIQ interrupt handling (presumable for better performance) but lacks the maintenance and bug fixing of the vanilla upstream dwc driver. Turns out that FIQ handling is disabled in the dwc_otg driver on arm64 so it makes little sense to use that driver on arm64.
In fact, upstream raspberrypi recommends to use the dwc2 driver on arm64.
| Changed in linux-raspi (Ubuntu Focal): | |
| status: | New → Won't Fix |
| Changed in linux-raspi (Ubuntu Groovy): | |
| status: | New → Won't Fix |
| description: | updated |
| summary: |
- Switch to the upstream dwc driver on arm64 + Use the upstream dwc2 driver on arm64 |
Revision history for this message
| Dave Jones (waveform) wrote | #1 |
| Changed in linux-raspi (Ubuntu Hirsute): | |
| status: | New → Won't Fix |
| Changed in linux-raspi (Ubuntu Jammy): | |
| status: | New → Fix Released |
| Changed in linux-raspi (Ubuntu Impish): | |
| status: | New → Fix Released |
To post a comment you must log in.
I think this was fixed in impish, was it not? It's certainly in jammy anyway.