g_ether missing eem support

Bug #1864132 reported by Enoch Leung
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-raspi (Ubuntu)
Invalid
High
Hui Wang
Eoan
Invalid
Undecided
Unassigned
Focal
Invalid
Undecided
Unassigned

Bug Description

I am looking into enabling EEM with g_ether by module option use_eem=1, and g_ether won't be loaded because it has no EEM support compiled.

Expected: EEM is compiled with g_ether (no such option for g_cdc) so that it can be enabled by use_eem=1.

My "/sys/module/g_ether/parameters":
-r--r--r-- 1 root root 4096 Feb 20 13:40 bcdDevice
-r--r--r-- 1 root root 4096 Feb 20 13:40 dev_addr
-r--r--r-- 1 root root 4096 Feb 20 13:40 host_addr
-r--r--r-- 1 root root 4096 Feb 20 13:40 iManufacturer
-r--r--r-- 1 root root 4096 Feb 20 13:40 iProduct
-r--r--r-- 1 root root 4096 Feb 20 13:40 iSerialNumber
-r--r--r-- 1 root root 4096 Feb 20 13:40 idProduct
-r--r--r-- 1 root root 4096 Feb 20 13:40 idVendor
-rw-r--r-- 1 root root 4096 Feb 20 14:08 qmult

modinfo g_ether:
parm: idVendor:USB Vendor ID (ushort)
parm: idProduct:USB Product ID (ushort)
parm: bcdDevice:USB Device version (BCD) (ushort)
parm: iSerialNumber:SerialNumber string (charp)
parm: iManufacturer:USB Manufacturer string (charp)
parm: iProduct:USB Product string (charp)
parm: qmult:queue length multiplier at high/super speed (uint)
parm: dev_addr:Device Ethernet Address (charp)
parm: host_addr:Host Ethernet Address (charp)
parm: use_eem:use CDC EEM mode (bool)

dmesg:
...
[ 4.474689] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers
...
[ 5.768660] dwc2 fe980000.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM
[ 5.772414] g_ether fe980000.usb: failed to start g_ether: -2
...

---- should it be another bug? -----
There is another issue that when my laptop is connected and the with my Pi 4 reboot, the cdc_ether function provided to my laptop will not be available again until I reconnect the cable (I have USB Y-cable + type-c adapter so I can unplug on laptop side w/o Pi 4 losing power). I remember it was working as expected when I was testing out OTG function.

Enoch Leung (leun0036)
affects: libvirt (Ubuntu) → linux-raspi2 (Ubuntu)
Hui Wang (hui.wang)
Changed in linux-raspi2 (Ubuntu):
importance: Undecided → High
assignee: nobody → Hui Wang (hui.wang)
Revision history for this message
Juerg Haefliger (juergh) wrote :

What series/kernel is this?

Revision history for this message
Hui Wang (hui.wang) wrote :

at least, it is for eoan.

Revision history for this message
Juerg Haefliger (juergh) wrote :

Is this still an issue with a current focal image from http://cdimage.ubuntu.com/releases/20.04/release/?

Revision history for this message
Enoch Leung (leun0036) wrote :

Sorry I cannot tell, as the OTG issue just come back after I upgraded to Focal via do-release-upgrade. Pls. refer to bug #1861070

Revision history for this message
Enoch Leung (leun0036) wrote :

I just updated kernel to have OTG working again as per #1861070, and can tell that EEM support is still missing.

/sys/module/g_ether/parameters has no entry of use_eem has per "modinfo g_ether" mentioned. g_cdc / g_multi has no use_eem as per modinfo, and I am not sure if it is also a good place to ask for that being added to these two modules or not.

Juerg Haefliger (juergh)
affects: linux-raspi2 (Ubuntu) → linux-raspi (Ubuntu)
Revision history for this message
Juerg Haefliger (juergh) wrote :

/sys/module/g_ether/parameters/use_eem is not visible because the driver doesn't make it available to sysfs. That might be by design or a defect but it doesn't really matter here. EEM support is built-in and can be turned on by loading the driver with 'modprobe g_ether use_eem=1'.

Note that we will not add EEM support to any other drivers since that is a feature request which we typically don't allow for stable kernels.

Changed in linux-raspi (Ubuntu):
status: New → Invalid
Changed in linux-raspi (Ubuntu Focal):
status: New → Invalid
Changed in linux-raspi (Ubuntu Eoan):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.