Re: Adding support for USB Device Class Definition for Personal Healthcare Devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Tue, Nov 23, 2010 at 12:20:37PM +0100, Bartolome Marin Sanchez wrote:
DMESG:
[  755.041027] usb usb2: usb wakeup-resume
[  755.041036] usb usb2: usb auto-resume
[  755.041039] usb usb2: wakeup_rh
[  755.079163] hub 2-0:1.0: hub_resume
[  755.079179] uhci_hcd 0000:00:1d.0: port 1 portsc 0083,00
[  755.079184] hub 2-0:1.0: port 1: status 0101 change 0001
[  755.183109] hub 2-0:1.0: state 7 ports 2 chg 0002 evt 0000
[  755.183124] hub 2-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
[  755.294745] usb 2-1: new full speed USB device using uhci_hcd and address 4
[  755.429687] usb 2-1: skipped 2 descriptors after interface
[  755.429693] usb 2-1: skipped 1 descriptor after endpoint
[  755.429696] usb 2-1: skipped 1 descriptor after endpoint
[  755.431931] usb 2-1: default language 0x0409
[  755.439100] usb 2-1: udev 4, busnum 2, minor = 131
[  755.439103] usb 2-1: New USB device found, idVendor=1c3d, idProduct=0002
[  755.439105] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  755.439107] usb 2-1: Product: Nonin Pulse Oximeter
[  755.439108] usb 2-1: Manufacturer: Nonin Medical Inc.
[  755.439110] usb 2-1: SerialNumber: 00000158
[  755.439217] usb 2-1: usb_probe_device
[  755.439220] usb 2-1: configuration #1 chosen from 1 choice
[  755.497893] usb 2-1: adding 2-1:1.0 (config #1, interface 0)

This device is a OxyOximeter blood oxygen monitor from Nonin that
implements the personal healthcare standard (ISO/IEEE 11073-10101,
Health Informatices and ISO/IEEE 11073-20601 Optimized Exchange
Protocol) to exchange the information.

The specification for usb is at:
http://www.usb.org/developers/devclass_docs => Personal Healthcare =>
Personal Healthcare Rev. 1.0, Errata for USB Personal Health Care
Device Class and Personal Healthcare Adopters Agreement.

For this device usb only is used to bypass the information from the
device to the application manager (at user space).

My question is about how I must adding support for it. I must
implement a kernel device driver or at user space with libusb?

Personally, I'd like a kernel driver better. But add all the constants
and data structures from the Specification to a common header, something
like include/linux/usb/health.h, so that it can be re-used for both host
and gadget drivers.

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


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux