device 0421:069a is supported, in fact.

Dear "linux-usb" mailing list people,

I was directed here by the email-bot of Greg Kroah-Hartman.

First I was contactim him directly, since at [1] it is written that things regarding the usbserial driver should be directed to him, which in turn I was getting from a question on where-to-address-this which I asked here [2].

Here the issue I want to address:

I have a device which is ignored by any in-kernel driver, but when I tell usbserial manually to drive that device (via modprobe usbserial vendor=0x0421 product=0x069a), it provides two serial ports where useful things can be made via the second.

It is a Nokia 130 mobile phone, and it provides an "AT"-style serial interface where things like address book synchronisation can be made.

It has the following vendor:product number 0421:069a.

So I suggest to you to add that device as a supported device to usbserial, so that hotplug works.

In lsusb it shows up as
Nokia Mobile Phones 130 [RM-1035] (Charging only), so the string (Charging only) should be removed then, too.

(The phone itself has two USB modes: "Memory card" (which will make it behave as mass storage with access to the microSD-card) and a mode which is called in the phone's menu as "Charging only", which is the mode interesting here and which in fact is more than "carging only").

I have also made a Linux bugtracker issue out of this [3], but my experience is that issues posted there are sometimes very unreliably noticed (depending on the subsystem, some parts of the bugtracker seem to not get attention at all). That's why I followed the suggestion in
[1] instead at first. I am still confused about what is the correct way to give this information to the people able to deal with it properly.

[1] Linux kernel documentation "USB serial":
http://kernel.org/doc/html/latest/usb/usb-serial.html#generic-serial-driver

[2] Answer to the question where to address this on stackexchange:
http://unix.stackexchange.com/a/689577/133286

[3] Enhancement-Issue of this at the Linux bugtracker:
http://bugzilla.kernel.org/show_bug.cgi?id=215579

| sed 's/\([Mm]\)an[n]*/\1ensch/g'

Can you provide the output of lsusb -v -d 0421:069a for us?

thanks,

greg k-h

On Tue, 8 Feb 2022 16:20:33 +0100, Greg KH <[email protected]> wrote about "Re: [usbserial] device 0421:069a is supported, in fact.":

Attached (without usbserial loaded to specifically drive this phone):
lsusb_0421:069a.nodriver.log

This email has been sent from a computer.

Bus 001 Device 009: ID 0421:069a Nokia Mobile Phones 130 [RM-1035] (Charging only) Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00

  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0421 Nokia Mobile Phones
  idProduct          0x069a 130 [RM-1035] (Charging only)
  bcdDevice            1.00
  iManufacturer           1 Nokia
  iProduct                2 Nokia 130 (RM-1035)
  iSerial                 0 
  bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0037
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 0
Device Status: 0x0000
(Bus Powered)

Thanks for reporting this. I've just sent you a patch adding a new "simple" driver for Nokia phones that should allow you to use this device without adding the device id manually.

You just need to remember to enable the USB_SERIAL_SIMPLE Kconfig option in your kernel build.

Will you be able to test the patch and let us know if it works as intended?

Johan

On Thu, 24 Feb 2022 14:35:48 +0100, Johan Hovold <[email protected]> wrote about "Re: [usbserial] device 0421:069a is supported, in fact.":

Yes, with some delay, I will come back to you.

I suppose also other Nokia phones will work like that, but I cannot name any specific.

Regards & thanks!

Mamihlapinatapai:

"Der Blick zwischen zwei Personen, von denen jede wünschte, die andere
würde etwas initiieren, was beide begehren, aber keine wagt den ersten
Schritt zu tun."

"The look shared by two people, each wishing that the other will
initiate something that they both desire, but are unwilling to suggest
or start themselves."

(Ein Wort aus der Sprache der "Yaghan" / A word from the language of
the "Yaghan").

Hej,

On Thu, 24 Feb 2022 14:35:48 +0100, Johan Hovold <[email protected]> wrote about "Re: [usbserial] device 0421:069a is supported, in fact.":

It works, but different than when I loaded the usbserial driver (not usb-serial-simple) with the device ID manually:

I now get 4 (instead of 2) USB interfaces.

dmesg output when I connect the phone:

```
[  160.876977] usb 1-2: new full-speed USB device number 9 using xhci_hcd
[  161.060539] usb 1-2: New USB device found, idVendor=0421, idProduct=069a, bcdDevice= 1.00
[  161.060549] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[  161.060552] usb 1-2: Product: Nokia 130 (RM-1035)
[  161.060554] usb 1-2: Manufacturer: Nokia
[  161.140899] usbcore: registered new interface driver usbserial_generic
[  161.140915] usbserial: USB Serial support registered for generic
[  161.147248] usbcore: registered new interface driver usb_serial_simple
[  161.147265] usbserial: USB Serial support registered for carelink
[  161.147273] usbserial: USB Serial support registered for zio
[  161.147282] usbserial: USB Serial support registered for funsoft
[  161.147292] usbserial: USB Serial support registered for flashloader
[  161.147304] usbserial: USB Serial support registered for google
[  161.147312] usbserial: USB Serial support registered for libtransistor
[  161.147320] usbserial: USB Serial support registered for vivopay
[  161.147327] usbserial: USB Serial support registered for moto_modem
[  161.147337] usbserial: USB Serial support registered for motorola_tetra
[  161.147346] usbserial: USB Serial support registered for nokia
[  161.147355] usbserial: USB Serial support registered for novatel_gps
[  161.147364] usbserial: USB Serial support registered for hp4x
[  161.147374] usbserial: USB Serial support registered for suunto
[  161.147382] usbserial: USB Serial support registered for siemens_mpi
[  161.147412] usb_serial_simple 1-2:1.0: nokia converter detected
[  161.147514] usb 1-2: nokia converter now attached to ttyUSB0
[  161.147582] usb 1-2: nokia converter now attached to ttyUSB1
[  161.147610] usb_serial_simple 1-2:1.1: nokia converter detected
[  161.147665] usb 1-2: nokia converter now attached to ttyUSB2
[  161.152908] usb 1-2: nokia converter now attached to ttyUSB3
```

and in this case it is /dev/ttyUSB2 which responds to AT-commands.

Via this interface, I can sync contacts.

Regards!

I'll catch you if you fall.
                      - floor

Yeah, that's a mistake on my part. I didn't look closely enough at the lsusb output when preparing the patch. Should be fixed in v2:

	https://lore.kernel.org/r/[email protected]

Thanks for testing.

Johan