[RFC] Probing ttys by default

[Sven Köhler]

Am 21.03.2014 15:36, schrieb Bjørn Mork:
> Sven Köhler <sven.koehler at gmail.com> writes:
> 
>> The value of ATTR{bmCapabilities} you find below may be from the CDC ACM
>> descriptor instead of the CDC Call Management descriptor.
>> At least for my UMTS card that is true, and I see a value of 7 instead
>> of 3. My best guess is, that udev doesn't handle it very well if there
>> are two fields of the same name in different descriptors of the same device.
> 
> Ah, you're right.  Thanks for clearing that up.  Then it's not going to
> be that simple to write a rule processing the CDC Call Management 
> bmCapabilities.
> 
> This doesn't really have much to do with udev.  It's the driver that
> parses the descriptors and export some functional descriptor fields as
> sysfs attributes.

Is it an option to change the driver so that exports call management
data too? It wouldn't help on system running older kernels, but it would
help for future systems.

> The code making this appear in sysfs/udev is:
> 
> static ssize_t show_caps
> (struct device *dev, struct device_attribute *attr, char *buf)
> {
> 	struct usb_interface *intf = to_usb_interface(dev);
> 	struct acm *acm = usb_get_intfdata(intf);
> 
> 	return sprintf(buf, "%d", acm->ctrl_caps);
> }
> static DEVICE_ATTR(bmCapabilities, S_IRUGO, show_caps, NULL);
> 
> ..
> 		case USB_CDC_ACM_TYPE:
> 			ac_management_function = buffer[3];
> 			break;
> 		case USB_CDC_CALL_MANAGEMENT_TYPE:
> 			call_management_function = buffer[3];
> 			call_interface_num = buffer[4];
> 			if ((quirks & NOT_A_MODEM) == 0 && (call_management_function & 3) != 3)
> 				dev_err(&intf->dev, "This device cannot do calls on its own. It is not a modem.\n");
> 			break;
> ..
> 
> 	acm->ctrl_caps = ac_management_function;
> 	if (quirks & NO_CAP_LINE)
> 		acm->ctrl_caps &= ~USB_CDC_CAP_LINE;
> 
> 
> 
> So the driver parse and use USB_CDC_CALL_MANAGEMENT_TYPE descriptor, but
> it doesn't export any of it.  If MM or other userspace tools want to
> inspect it, then the only option is to parse it again out of either the
> "descriptors" sysfs field or the /dev/bus/usb character device.
> 
> 
> Bjørn
>