USB Ethernet gadget on Nokia n900

Hi!
From 3.6 to 3.10, USB networking works on Nokia N900. With
3.11, it fails with messages on the host. I also tried to
get it to work on 3.14 and 3.17, with no luck.
Any ideas? Does it work for you? Any config options to watch
for?

With 3.17, I get
omap_musb_mailbox: musb core is not yet ready
message. It looks related...?

Can you try tree https://gitorious.org/linux-n900/linux-n900/ ?

I think with rx51_defconfig from above tree it worked fine for
3.10 - 3.13 versions.

--
Pali RohÃ¡r
***@gmail.com

Pavel Machek

2014-10-19 20:50:36 UTC

Post by Pali RohÃ¡r

Hi!
=20
From 3.6 to 3.10, USB networking works on Nokia N900. With
3.11, it fails with messages on the host. I also tried to
get it to work on 3.14 and 3.17, with no luck.
=20
Any ideas? Does it work for you? Any config options to watch for?

=20
With 3.17, I get
=20
omap_musb_mailbox: musb core is not yet ready
=20
message. It looks related...?

=20
Can you try tree https://gitorious.org/linux-n900/linux-n900/ ?
=20
I think with rx51_defconfig from above tree it worked fine for=20
3.10 - 3.13 versions.

=46rom your tree, I am trying 815039686baffff6432b45028dd405b1981a9112
(3.16 based). I attempted to make gadget drivers build-in and enabled
nfsroot. I could not detect nokia on USB after bootup.

Are you sure about defconfig? AFAICT defconfig will always be
unsuitable for nfsroot, as it will not contain nfs support built-in...

I am trying c089e5f8ba2d44afd2db2c2042d43ca70205c536 (3.13
based). Same result :-(.

Do you have any tree where usb gadget works for you?

Thanks,
Pavel
--=20
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses=
/blog.html

Pali Rohár

2014-10-19 21:00:20 UTC

Post by Pali RohÃ¡r

Hi!
From 3.6 to 3.10, USB networking works on Nokia N900.
With 3.11, it fails with messages on the host. I also
tried to get it to work on 3.14 and 3.17, with no luck.
Any ideas? Does it work for you? Any config options to
watch for?

With 3.17, I get
omap_musb_mailbox: musb core is not yet ready
message. It looks related...?

Can you try tree
https://gitorious.org/linux-n900/linux-n900/ ?
I think with rx51_defconfig from above tree it worked fine
for 3.10 - 3.13 versions.

From your tree, I am trying
815039686baffff6432b45028dd405b1981a9112 (3.16 based). I
attempted to make gadget drivers build-in and enabled
nfsroot. I could not detect nokia on USB after bootup.
Are you sure about defconfig? AFAICT defconfig will always be
unsuitable for nfsroot, as it will not contain nfs support
built-in...
I am trying c089e5f8ba2d44afd2db2c2042d43ca70205c536 (3.13
based). Same result :-(.
Do you have any tree where usb gadget works for you?
Thanks,
Pavel

My N900 can boot kernel from v3.12-rc5-n900 branch compiled with
arch/arm/configs/rx51_defconfig. Also it can boot full Maemo5
system (with CSSU and some minor system changes) and usb network
via g_nokia.ko gadget working fine...

So if it does not working for you then kernel usb subsystem could
have problems with using gadgets directly from zimage.

--
Pali RohÃ¡r
***@gmail.com

Pavel Machek

2014-10-19 22:30:43 UTC

Hi!

Post by Pali RohÃ¡r

Post by Pavel Machek
omap_musb_mailbox: musb core is not yet ready
message. It looks related...?

Can you try tree
https://gitorious.org/linux-n900/linux-n900/ ?
I think with rx51_defconfig from above tree it worked fine
for 3.10 - 3.13 versions.

Thanks for the info. Network seems to work on this one.

Post by Pali RohÃ¡r
So if it does not working for you then kernel usb subsystem could
have problems with using gadgets directly from zimage.

It seems to work with 3.12, but not with 3.13 (in similar config). If
you could test USB networking in 3.13, that would help...

Thanks,

Pavel

Pavel Machek

2014-10-20 13:08:55 UTC

Hi!

Post by Pali RohÃ¡r
My N900 can boot kernel from v3.12-rc5-n900 branch compiled with
arch/arm/configs/rx51_defconfig. Also it can boot full Maemo5
system (with CSSU and some minor system changes) and usb network
via g_nokia.ko gadget working fine...
So if it does not working for you then kernel usb subsystem could
have problems with using gadgets directly from zimage.

After some hand-bisecting and real-bisecting, I found two commits that
cause problems for 3.13: With these reverted, I get usb networking
back in 3.13 on nokia n900.

(Pali, if you revert these, you should get working usb networking in
your 3.13 branch, too.)

Any ideas?

Pavel

commit 3e3101d57c50f9e4fa1da947e4bd0bc5cbab4141
Author: Kishon Vijay Abraham I <***@ti.com>
Date: Fri Sep 27 11:53:30 2013 +0530

usb: musb: omap2430: use the new generic PHY framework

Use the generic PHY framework API to get the PHY. The
usb_phy_set_resume
and usb_phy_set_suspend is replaced with power_on and
power_off to align with the new PHY framework.

musb->xceiv can't be removed as of now because musb core uses
xceiv.state and
xceiv.otg. Once there is a separate state machine to handle otg,
these can be
moved out of xceiv and then we can start using the generic PHY
framework.

Signed-off-by: Kishon Vijay Abraham I <***@ti.com>
Reviewed-by: Sylwester Nawrocki <***@samsung.com>
Acked-by: Felipe Balbi <***@ti.com>
Signed-off-by: Greg Kroah-Hartman <***@linuxfoundation.org>

commit f1ddc24c9e33813f74b871d73e4d795dcdb95a3c
Author: Kishon Vijay Abraham I <***@ti.com>
Date: Fri Sep 27 11:53:31 2013 +0530

usb: phy: twl4030-usb: remove *set_suspend* and *phy_init* ops

Now that twl4030-usb is adapted to the new generic PHY framework,
*set_suspend* and *phy_init* ops can be removed from twl4030-usb
driver.

Signed-off-by: Kishon Vijay Abraham I <***@ti.com>
Acked-by: Felipe Balbi <***@ti.com>
Reviewed-by: Sylwester Nawrocki <***@samsung.com>
Signed-off-by: Greg Kroah-Hartman <***@linuxfoundation.org>

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Tony Lindgren

2014-10-20 16:45:42 UTC

Post by Pavel Machek
Hi!

Hmm maybe check if current stable kernels work for you without
reverting anything ? Few weeks ago I did the the following two fixes
with cc stable v3.13+:

96be39ab34b7 usb: phy: twl4030-usb: Fix regressions to runtime PM on omaps
85601b8d81e2 usb: phy: twl4030-usb: Fix lost interrupts after ID pin goes down

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Pavel Machek

2014-10-20 22:03:38 UTC

Post by Pavel Machek
Hi!

Hmm maybe check if current stable kernels work for you without
reverting anything ? Few weeks ago I did the the following two fixes
96be39ab34b7 usb: phy: twl4030-usb: Fix regressions to runtime PM on omaps
85601b8d81e2 usb: phy: twl4030-usb: Fix lost interrupts after ID pin goes down

I tried these on top of 3.14 (where my revert fixes stuff) and no, it
does not seem to help. (Trying stable would be a bit more work).

Do you want me to try on 3.13, too?
Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Tony Lindgren

2014-10-20 22:29:43 UTC

Post by Pavel Machek
Hi!

I tried these on top of 3.14 (where my revert fixes stuff) and no, it
does not seem to help. (Trying stable would be a bit more work).
Do you want me to try on 3.13, too?

Sounds like there's something else missing too then. Maybe give
v3.18-rc1 and device tree based boot a try?

FYI, there's some PM support there too since v3.16-rc7, so using
anything pre v3.17 is probably not fun on the battery. Well it works
with omap2plus_defconfig long as serial port timeouts are configured,
no USB cable is connected and and the screen is blanked. When it works,
both keyboard debug LEDs will go off during idle, which really should
be most of the time if you plan to use it as a phone. The left debug
LED goes off for retention idle, when both go off it's hitting
off-idle.

I'm using the following test script here, if it does not idle for
you, there are probably some other drivers loaded that currently
block deeper idle states.

Regards,

Tony

8< ---------------
#!/bin/bash

uarts=$(find /sys/class/tty/ttyO*/device/power/ -type d)
for uart in $uarts; do
echo 3000 > $uart/autosuspend_delay_ms
#echo -1 > $uart/autosuspend_delay_ms
done

uarts=$(find /sys/class/tty/ttyO*/power/ -type d)
for uart in $uarts; do
echo enabled > $uart/wakeup
echo auto > $uart/control
done

echo 255 > /sys/devices/68000000.ocp/48098000.spi/spi_master/spi1/spi1.2/backlight/acx565akm/brightness
echo 1 > /sys/devices/platform/omapfb/graphics/fb0/blank

echo 1 > /sys/kernel/debug/pm_debug/enable_off_mode
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Pavel Machek

2014-10-21 21:52:50 UTC

Hi!

Post by Pavel Machek
After some hand-bisecting and real-bisecting, I found two commits that
cause problems for 3.13: With these reverted, I get usb networking
back in 3.13 on nokia n900.
(Pali, if you revert these, you should get working usb networking in
your 3.13 branch, too.)
Any ideas?

I tried these on top of 3.14 (where my revert fixes stuff) and no, it
does not seem to help. (Trying stable would be a bit more work).
Do you want me to try on 3.13, too?

Sounds like there's something else missing too then. Maybe give
v3.18-rc1 and device tree based boot a try?

Ok, I tried 3.18-rc1 (with dt appended to the zImage) and this should
be the logs from that attempt (on PC).

[205583.689477] usb 4-1: Product: Nokia N900 (Update mode)
[205583.689480] usb 4-1: Manufacturer: Nokia
[205583.689483] usb 4-1: SerialNumber: 4D554D363434323537
[205584.467273] usb 4-1: USB disconnect, device number 72
[205590.120043] usb 4-1: new high-speed USB device number 73 using
ehci-pci
[205605.232034] usb 4-1: device descriptor read/64, error -110
[205620.448036] usb 4-1: device descriptor read/64, error -110
[205620.664032] usb 4-1: new high-speed USB device number 74 using
ehci-pci
[205635.776032] usb 4-1: device descriptor read/64, error -110
[205650.992032] usb 4-1: device descriptor read/64, error -110
[205651.208030] usb 4-1: new high-speed USB device number 75 using
ehci-pci
[205661.616025] usb 4-1: device not accepting address 75, error -110

IOW usb gadget driver loaded (or there would be no "new high-speed USB
device" message, but communication does not work.

I'm attaching the config.

Post by Tony Lindgren
FYI, there's some PM support there too since v3.16-rc7, so using
anything pre v3.17 is probably not fun on the battery. Well it works

My goal is to get nfsroot to work, and then I can play with bluetooth,
userland and power management. For now, power consumption is not
important, as I'm unable to boot useful system.

(I could boot from MMC, but that's too cumbersome to use due to lack
of space, hard communication, and constant fiddling with device
cover).

Best regards,
Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Felipe Balbi

2014-10-19 15:24:14 UTC

Hi,

With 3.17, I get
omap_musb_mailbox: musb core is not yet ready
message. It looks related...?

is musbmhdrc.ko loaded ? Do you have a gadget driver loaded ?

+ Aaro

--
balbi

Pavel Machek

2014-10-19 19:19:37 UTC

Hi!

Post by Felipe Balbi
Hi,

With 3.17, I get
omap_musb_mailbox: musb core is not yet ready
message. It looks related...?

is musbmhdrc.ko loaded ? Do you have a gadget driver loaded ?
+ Aaro

I am trying to use nfsroot, so I can't use modules. I can't find
musbmhdrc.ko; did you mean drivers/usb/musb/musb_hdrc? Yes, that
should be build-in:

CONFIG_USB_MUSB_HDRC=y
CONFIG_USB_MUSB_GADGET=y
CONFIG_USB_MUSB_OMAP2PLUS=y
CONFIG_MUSB_PIO_ONLY=y

Gadget options are:

CONFIG_USB_ULPI=y
CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_DEBUG=y
CONFIG_USB_GADGET_VERBOSE=y
CONFIG_USB_GADGET_DEBUG_FILES=y
CONFIG_USB_GADGET_DEBUG_FS=y
CONFIG_USB_GADGET_VBUS_DRAW=2
CONFIG_USB_GADGET_STORAGE_NUM_BUFFERS=2

CONFIG_USB_LIBCOMPOSITE=y
CONFIG_USB_U_ETHER=y
CONFIG_USB_F_ECM=y
CONFIG_USB_F_EEM=y
CONFIG_USB_F_SUBSET=y
CONFIG_USB_F_RNDIS=y

(I am attaching full config, in case I missed something important).

Best regards,
Pavel

--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Pavel Machek

2014-10-19 19:29:37 UTC

Hi!

Hi,

With 3.17, I get
omap_musb_mailbox: musb core is not yet ready

For the record, I can't see the message in this try. Either it is not
there, or it scrolled away (there's unfortunately no way to scroll
back).

Pavel

Aaro Koskinen

2014-10-20 21:35:18 UTC

Hi,

Post by Pavel Machek
I am trying to use nfsroot, so I can't use modules.

Why not?

Post by Pavel Machek
(I am attaching full config, in case I missed something important).

I'm using the below config with 3.17 and g_ether works OK.

(My initramfs modprobes g_ether, runs busybox ifconfig for usb0
and launches sshd.)

A.

---

CONFIG_LOCALVERSION="-omap3"
CONFIG_KERNEL_LZMA=y
CONFIG_SYSVIPC=y
# CONFIG_CROSS_MEMORY_ATTACH is not set
CONFIG_NO_HZ=y
CONFIG_HIGH_RES_TIMERS=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=20
CONFIG_BLK_DEV_INITRD=y
# CONFIG_RD_GZIP is not set
CONFIG_EXPERT=y
CONFIG_KALLSYMS_ALL=y
CONFIG_PROFILING=y
CONFIG_OPROFILE=m
CONFIG_MODULES=y
CONFIG_MODULE_FORCE_LOAD=y
CONFIG_MODULE_UNLOAD=y
CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_BLK_DEV_BSG is not set
CONFIG_PARTITION_ADVANCED=y
# CONFIG_EFI_PARTITION is not set
# CONFIG_IOSCHED_DEADLINE is not set
CONFIG_OMAP_RESET_CLOCKS=y
CONFIG_OMAP_MUX_DEBUG=y
CONFIG_ARCH_OMAP3=y
# CONFIG_SOC_TI81XX is not set
# CONFIG_MACH_OMAP3_BEAGLE is not set
# CONFIG_MACH_DEVKIT8000 is not set
# CONFIG_MACH_OMAP_LDP is not set
# CONFIG_MACH_OMAP3530_LV_SOM is not set
# CONFIG_MACH_OMAP3_TORPEDO is not set
# CONFIG_MACH_OVERO is not set
# CONFIG_MACH_OMAP3517EVM is not set
# CONFIG_MACH_OMAP3_PANDORA is not set
# CONFIG_MACH_TOUCHBOOK is not set
# CONFIG_MACH_OMAP_3430SDP is not set
# CONFIG_MACH_NOKIA_RX51 is not set
# CONFIG_MACH_CM_T35 is not set
# CONFIG_MACH_CM_T3517 is not set
# CONFIG_MACH_SBC3530 is not set
CONFIG_ARM_THUMBEE=y
CONFIG_PREEMPT=y
# CONFIG_ATAGS is not set
CONFIG_ZBOOT_ROM_TEXT=0x0
CONFIG_ZBOOT_ROM_BSS=0x0
CONFIG_ARM_APPENDED_DTB=y
CONFIG_CMDLINE="console=ttyO2,115200 console=tty"
CONFIG_KEXEC=y
CONFIG_BINFMT_MISC=y
CONFIG_PM_DEBUG=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_INET=y
# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
# CONFIG_INET_XFRM_MODE_TUNNEL is not set
# CONFIG_INET_XFRM_MODE_BEET is not set
# CONFIG_INET_LRO is not set
# CONFIG_INET_DIAG is not set
# CONFIG_IPV6 is not set
# CONFIG_WIRELESS is not set
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
CONFIG_DEVTMPFS=y
CONFIG_MTD=y
CONFIG_MTD_BLOCK=y
CONFIG_MTD_OOPS=y
CONFIG_MTD_CFI=y
CONFIG_MTD_CFI_INTELEXT=y
CONFIG_MTD_NAND=y
CONFIG_MTD_NAND_OMAP2=y
CONFIG_MTD_ONENAND=y
CONFIG_MTD_ONENAND_VERIFY_WRITE=y
CONFIG_MTD_ONENAND_OMAP2=y
CONFIG_MTD_UBI=y
# CONFIG_BLK_DEV is not set
CONFIG_EEPROM_93CX6=y
CONFIG_SENSORS_LIS3_I2C=m
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_SCSI_SCAN_ASYNC=y
CONFIG_INPUT_POLLDEV=y
CONFIG_INPUT_JOYDEV=y
CONFIG_INPUT_EVDEV=y
CONFIG_KEYBOARD_GPIO=y
CONFIG_KEYBOARD_TWL4030=y
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ADS7846=y
CONFIG_TOUCHSCREEN_TSC2005=y
CONFIG_INPUT_MISC=y
CONFIG_INPUT_TWL4030_PWRBUTTON=y
CONFIG_INPUT_UINPUT=y
# CONFIG_LEGACY_PTYS is not set
CONFIG_SERIAL_OMAP=y
CONFIG_SERIAL_OMAP_CONSOLE=y
CONFIG_HW_RANDOM=y
CONFIG_I2C_CHARDEV=y
CONFIG_SPI=y
CONFIG_SPI_OMAP24XX=y
CONFIG_PINCTRL_SINGLE=y
CONFIG_DEBUG_GPIO=y
CONFIG_GPIO_SYSFS=y
CONFIG_GPIO_TWL4030=y
CONFIG_POWER_SUPPLY=y
CONFIG_WATCHDOG=y
CONFIG_OMAP_WATCHDOG=y
CONFIG_TWL4030_WATCHDOG=y
CONFIG_REGULATOR_FIXED_VOLTAGE=y
CONFIG_REGULATOR_TPS65023=y
CONFIG_REGULATOR_TPS6507X=y
CONFIG_REGULATOR_TWL4030=y
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_MODE_HELPERS=y
CONFIG_FB_TILEBLITTING=y
CONFIG_OMAP2_DSS=y
# CONFIG_OMAP2_DSS_DPI is not set
CONFIG_OMAP2_DSS_SDI=y
CONFIG_FB_OMAP2=y
# CONFIG_FB_OMAP2_DEBUG_SUPPORT is not set
CONFIG_DISPLAY_PANEL_SONY_ACX565AKM=y
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=y
CONFIG_LCD_PLATFORM=y
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_LOGO=y
# CONFIG_LOGO_LINUX_VGA16 is not set
# CONFIG_LOGO_LINUX_CLUT224 is not set
CONFIG_USB=y
CONFIG_USB_ANNOUNCE_NEW_DEVICES=y
CONFIG_USB_MUSB_HDRC=y
CONFIG_USB_MUSB_OMAP2PLUS=y
CONFIG_NOP_USB_XCEIV=y
CONFIG_USB_GADGET=y
CONFIG_USB_GADGET_DEBUG=y
CONFIG_USB_GADGET_DEBUG_FILES=y
CONFIG_USB_ETH=m
# CONFIG_USB_ETH_RNDIS is not set
CONFIG_MMC=y
CONFIG_SDIO_UART=y
CONFIG_MMC_OMAP_HS=y
CONFIG_RTC_CLASS=y
CONFIG_RTC_DRV_TWL4030=y
CONFIG_DMADEVICES=y
CONFIG_DMA_OMAP=y
CONFIG_TWL4030_USB=y
CONFIG_EXT4_FS=y
# CONFIG_FILE_LOCKING is not set
# CONFIG_DNOTIFY is not set
# CONFIG_INOTIFY_USER is not set
CONFIG_TMPFS=y
# CONFIG_MISC_FILESYSTEMS is not set
# CONFIG_NETWORK_FILESYSTEMS is not set
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_ISO8859_1=y
CONFIG_PRINTK_TIME=y
CONFIG_DEBUG_INFO=y
CONFIG_DEBUG_FS=y
CONFIG_MAGIC_SYSRQ=y
# CONFIG_SCHED_DEBUG is not set
# CONFIG_DEBUG_BUGVERBOSE is not set
# CONFIG_FTRACE is not set
# CONFIG_ARM_UNWIND is not set
CONFIG_DEBUG_LL=y
CONFIG_DEBUG_OMAP3UART3=y
CONFIG_EARLY_PRINTK=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

Aaro Koskinen

2014-10-20 21:37:31 UTC

Hi,

Post by Aaro Koskinen

Post by Pavel Machek
I am trying to use nfsroot, so I can't use modules.

Why not?

Post by Pavel Machek
(I am attaching full config, in case I missed something important).

I'm using the below config with 3.17 and g_ether works OK.

Also, I'm using DT boot.

A.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Pavel Machek

2014-10-20 22:42:12 UTC