04 Apr, 2015
1 commit
-
Fix build errors when HW_RANDOM is not enabled:
drivers/built-in.o: In function `chaoskey_disconnect':
chaoskey.c:(.text+0x5f3f00): undefined reference to `hwrng_unregister'
drivers/built-in.o: In function `chaoskey_probe':
chaoskey.c:(.text+0x5f42a6): undefined reference to `hwrng_register'Signed-off-by: Randy Dunlap
Signed-off-by: Greg Kroah-Hartman
26 Mar, 2015
1 commit
-
This is a hardware random number generator. The driver provides both a
/dev/chaoskeyX entry and hooks the entropy source up to the kernel
hwrng interface. More information about the device can be found at
http://chaoskey.orgThe USB ID for ChaosKey was allocated from the OpenMoko USB vendor
space and is visible as 'USBtrng' here:http://wiki.openmoko.org/wiki/USB_Product_IDs
v2: Respond to review from Oliver Neukum
* Delete extensive debug infrastructure and replace it with calls to
dev_dbg.* Allocate I/O buffer separately from device structure to obey
requirements for non-coherant architectures.* Initialize mutexes before registering device to ensure that open
cannot be invoked before the device is ready to proceed.* Return number of bytes read instead of -EINTR when partial read
operation is aborted due to a signal.* Make sure device mutex is unlocked in read error paths.
* Add MAINTAINERS entry for the driver
Signed-off-by: Keith Packard
Cc: Oliver Neukum
Signed-off-by: Greg Kroah-Hartman
18 Jul, 2014
1 commit
-
OTG3 and EH Compliance Plan 1.0 talks about Super Speed OTG Verification
system (SS-OVS) which consists of an excersizer and analyzer.USB Compliance Suite from Lecroy or Ellisys can act as such SS-OVS for
Link Layer Validation (LVS).Some modifications are needed for an embedded Linux USB host to pass all
these tests. Most of these tests require just Link to be in U0. They do
not work with default Linux USB stack since, default stack does port
reset and then starts sending setup packet, which is not expected by
Link Layer Validation (LVS) device of Lecroy Compliance Suit. Then,
There are many Link Layer Tests which need host to generate specific
traffic.This patch supports specific traffic generation cases. As of now all the
host Lecroy Link Layer-USBIF tests (except TD7.26) passes
with this patch for single run using Lecroy USB Compliance Suite
Version 1.98 Build 239 and Lecroy USB Protocol Analyzer version 4.80
Build 1603. Therefore patch seems to be a good candidate for inclusion.
Further modification can be done on top of it.lvstest driver will not bind to any device by default. It can bind
manually to a super speed USB host controller root hub. Therefore, regular
hub driver must be unbound before this driver is bound. For example, if
2-0:1.0 is the xhci root hub, then execute following to unbind hub driver.echo 2-0:1.0 > /sys/bus/usb/drivers/hub/unbind
Then write Linux Foundation's vendor ID which is used by root hubs and
SS root hub's device ID into new_id file. Writing IDs into new_id file
will also bind the lvs driver with any available SS root hub interfaces.echo "1D6B 3" > /sys/bus/usb/drivers/lvs/new_id
Now connect LVS device with root hub port.
Test case specific traffic can be generated as follows whenever needed:
1. To issue "Get Device descriptor" command for TD.7.06:
echo > /sys/bus/usb/devices/2-0\:1.0/get_dev_desc2. To set U1 timeout to 127 for TD.7.18
echo 127 > /sys/bus/usb/devices/2-0\:1.0/u1_timeout3. To set U2 timeout to 0 for TD.7.18
echo 0 > /sys/bus/usb/devices/2-0\:1.0/u2_timeout4. To issue "Hot Reset" for TD.7.29
echo > /sys/bus/usb/devices/2-0\:1.0/hot_reset5. To issue "U3 Entry" for TD.7.35
echo > /sys/bus/usb/devices/2-0\:1.0/u3_entry6. To issue "U3 Exit" for TD.7.36
echo > /sys/bus/usb/devices/2-0\:1.0/u3_exitSigned-off-by: Pratyush Anand
Acked-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman
12 Feb, 2014
1 commit
-
The Kconfig entries for USB_U132_HCD and USB_FTDI_ELAN default to
(uppercase) "M". But in Kconfig (lowercase) "m" is a magic symbol. "M"
is an ordinary symbol. As "M" is never set these Kconfig symbols will
also not be set by default.Since I'm not aware of a reason why these driver should be set by
default, let's just drop these lines (that basically do nothing).Signed-off-by: Paul Bolle
Signed-off-by: Greg Kroah-Hartman
17 Oct, 2013
1 commit
-
The USB3503 driver had an incorrect depedency on REGMAP, instead of
REGMAP_I2C. This caused the build to fail since the necessary regmap
i2c pieces were not available.Signed-off-by: Matthew Dawson
Signed-off-by: Greg Kroah-Hartman
13 Aug, 2013
1 commit
-
This will give access to the diagnostic infrastructure regmap has but
the main point is to support future refactoring.Signed-off-by: Mark Brown
Signed-off-by: Greg Kroah-Hartman
26 Jul, 2013
1 commit
-
An Embedded Host High-Speed Electrical Test (EHSET) test fixture is
used to initiate test modes on a host controller in order to perform
the high speed electrical testing procedure for USB-IF compliance.
When this test fixture is connected to a host, it can enumerate as
one of several selectable VID/PID pairs, each corresponding to one
of the following test modes:* TEST_SE0_NAK
* TEST_J
* TEST_K
* TEST_PACKET
* HS_HOST_PORT_SUSPEND_RESUME
* SINGLE_STEP_GET_DEV_DESC
* SINGLE_STEP_SET_FEATUREThe USB EHSET procedure can be found here:
http://www.usb.org/developers/onthego/EHSET_v1.01.pdfSigned-off-by: Manu Gautam
[jackp@codeaurora.org: imported from commit 073c9409 on codeaurora.org;
minor cleanup and updated author email]
Signed-off-by: Jack Pham
Signed-off-by: Greg Kroah-Hartman
10 Apr, 2013
1 commit
-
This patch removes the depends on USB from all config symbols in
drivers/usb/host/Kconfig and replace that with an if USB / endif block
as suggested by Alan Stern. Some source ... Kconfig lines have been
shuffled around to permit a better regroupment of the Kconfig files
depending on "config USB" item. No functionnal change is introduced.Acked-by: Alan Stern
Signed-off-by: Florian Fainelli
Signed-off-by: Greg Kroah-Hartman
12 Jan, 2013
1 commit
-
This patch adds new driver of SMSC USB3503 USB 2.0 hub controller with HSIC
upstream connectivity and three USB 2.0 downstream ports. The specification
can be found from 'http://www.smsc.com/index.php?tid=295&pid=325'.The current version have been tested very basic features switching the modes,
HUB-MODE and STANDBY-MODE.Signed-off-by: Dongjin Kim
Signed-off-by: Greg Kroah-Hartman
27 Nov, 2012
1 commit
-
This fixes an error during modpost, when ezusb is built into the kernel
while USB is built as module.Signed-off-by: René Bürgel
Cc: stable
--
Signed-off-by: Greg Kroah-Hartman
27 Sep, 2012
1 commit
-
This patch
- moves drivers/usb/serial/ezusb.c to drivers/usb/misc/
- renamed CONFIG_USB_EZUSB to CONFIG_USB_EZUSB_FX2 to avoid build errors
- adapts Makefiles and Kconfigs switching from bool to tristate for CONFIG_USB_EZUSB_FX2Signed-off-by: René Bürgel
Signed-off-by: Greg Kroah-Hartman
23 Oct, 2010
1 commit
-
Meywa-Denki/Kayac YUREX is a leg-shakes sensor device.
See http://bbu.kayac.com/en/about/ for further information.
This driver support read/write the leg-shakes counter in the device
via a device file /dev/yurex[0-9]*.[minor coding style cleanups fixed by gregkh]
Signed-off-by: Tomoki Sekiyama
Cc: Jiri Kosina
Signed-off-by: Greg Kroah-Hartman
03 Mar, 2010
2 commits
-
This patch removes the vstusb driver and support from the Linux tree.
This driver provided support for Vernier Software & Technology devices
and spectrometers (Ocean Optics). This driver is being replaced by a
user space - libusb - implementation.Signed-off-by: Jim Collar
Signed-off-by: Greg Kroah-Hartman -
The Barry project's userspace program, bcharge, can better handle this
device and functionality, and it also works with the latest phones,
which this driver does not support. So remove it, as the userspace code
should be used instead.Cc: Chris Frey
Signed-off-by: Greg Kroah-Hartman
29 Jul, 2009
1 commit
-
THis patch (as1270) allows the usbtest module to be built even when
USB_DEVICEFS isn't configured. Tests can be performed without
USB_DEVICEFS, using the /dev/bus/usb/*/* device files.Signed-off-by: Alan Stern
Signed-off-by: Greg Kroah-Hartman
25 Mar, 2009
1 commit
-
These devices are better controlled with the LGPL userspace library
found at:
http://www.phidgets.com/downloads.php?os_id=3
and full documentation at:
http://www.phidgets.com/documentation/web/cdoc/index.htmlCc: Chester Fitchett
Acked-by: Sean Young
Signed-off-by: Greg Kroah-Hartman
18 Oct, 2008
2 commits
-
This patch adds the vstusb driver to the drivers/usb/misc directory.
This driver provides support for Vernier Software & Technology
spectrometers, all made by Ocean Optics. The driver provides both IOCTL
and read()/write() methods for sending raw data to spectrometers across
the bulk channel. Each method allows for a configured timeout.From: Stephen Ware
Signed-off-by: Dennis O'Brien
Signed-off-by: Greg Kroah-Hartman -
Added basic support for a Delcom USB 7-segment LED Display
Signed-off by: Harrison Metzger
Signed-off-by: Greg Kroah-Hartman
14 Aug, 2008
1 commit
-
This patch removes the auerswald USB driver from the linux kernel
2.6.26.This driver was included into the kernel mainly to connect to the ISDN
framework. This was done in linux 2.4.x. For 2.6.x, due to the fragile
and moving ISDN support, this connection was never realized, and the
only use of this driver was for device configuration. In the age of DSL,
the demand of ISDN support is getting very low.Meanwhile, with the advent of libusb, an userspace driver was done for
the device configuration which works fine for linux and mac. (Thanks to
the libusb developers!). The userspace driver is downloadable from the
auerswald web site.So this driver is obsolete now and has to be removed. Many thanks to all
developers which helped me to bring this driver up and working.Signed-off-by: Wolfgang Muees
Signed-off-by: Greg Kroah-Hartman
12 Jun, 2008
1 commit
-
USB: fix build bug in USB_ISIGHTFW
-tip tree testing found this build bug:
drivers/built-in.o: In function `isight_firmware_load':
isight_firmware.c:(.text+0x1ade08): undefined reference to `request_firmware'
isight_firmware.c:(.text+0x1adf9c): undefined reference to `release_firmware'select FW_LOADER in USB_ISIGHTFW.
From: Ingo Molnar
Signed-off-by: Greg Kroah-Hartman
30 May, 2008
1 commit
-
Uninitialised Apple iSight drivers present with a distinctive USB ID.
Once firmware has been uploaded, they disconnect and reconnect with a
new ID. At this point they can be driven by the uvcvideo driver. As this
is unique to the Apple cameras and not functionality shared by any other
UVC devices, it makes sense to provide the firmware loading
functionality in a separate driver. This driver will read an isight.fw
file extracted from the Apple driver using the tools at
http://bersace03.free.fr/ift/ and upload it to the camera. It will also
handle the case where the device loses its firmware during hibernation
and must have it reloaded.Signed-off-by: Matthew Garrett
Signed-off-by: Greg Kroah-Hartman
25 Apr, 2008
1 commit
-
Since nothing under the USB misc/ seems to be obviously experimental,
remove the EXPERIMENTAL dependency from those Kconfig entries.Signed-off-by: Robert P. J. Day
Signed-off-by: Greg Kroah-Hartman
24 Feb, 2007
1 commit
-
The ioctl is commented out for now, until we verify some userspace
application issues.Cc: Christian Lucht
Cc: Robert Marquardt
Signed-off-by: Greg Kroah-Hartman
17 Feb, 2007
1 commit
-
A simple driver to turn on the charging capability of a USB BlackBerry
device when it is plugged into the machine. It does not bind to the
device, so all userspace programs can still sync properly with it.Note, if CONFIG_USB_SUSPEND is enabled, it can play havoc with this
device as the power to the port will be shut down. This device id will
have to be added to the global blacklist table when it is created.Signed-off-by: Greg Kroah-Hartman
18 Oct, 2006
1 commit
-
It's not a input driver, so it doesn't belong in the input directory.
Cc: Sam Hocevar
Cc: Dmitry Torokhov
Signed-off-by: Greg Kroah-Hartman
28 Sep, 2006
4 commits
-
This "ftdi-elan" module is one half of the "driver" for
ELAN's Uxxx series adapters which are USB to PCMCIA CardBus
adapters. Currently only the U132 adapter is available and
it's module is called "u132-hcd".When the USB hot plug subsystem detects a Uxxx series adapter
it should load this module.Upon a successful device probe() the jtag device file interface
is created and the status workqueue started up.The jtag device file interface exists for the purpose of
updating the firmware in the Uxxx series adapter, but as
yet it had never been used.The status workqueue initializes the Uxxx and then sits there
polling the Uxxx until a supported PCMCIA CardBus device is
detected it will start the command and respond workqueues
and then load the module that handles the device. This will
initially be only the u132-hcd module. The status workqueue
then just polls the Uxxx looking for card ejects.The command and respond workqueues implement a command
sequencer for communicating with the firmware on the other
side of the FTDI chip in the Uxxx. This "ftdi-elan" module
exports some functions to interface with the sequencer.Note that this module is a USB client driver.
Note that the "u132-hcd" module is a (cut-down OHCI)
host controller.Thus we have a topology with the parent of a host controller
being a USB client! This really stresses the USB subsystem
semaphore/mutex handling in the module removal.Signed-off-by: Tony Olech
Signed-off-by: Greg Kroah-Hartman -
This patch adds support for Ontrak ADU USB devices.
Fixed for printk issues by Randy Dunlap
Signed-off-by: Steven Haigh
Signed-off-by: Greg Kroah-Hartman -
This patch creates a device class phidget and add the phidget drivers to
them.Signed-off-by: Sean Young
Signed-off-by: Greg Kroah-Hartman -
This driver add support for the Phidgets Inc., MotorControl via sysfs. Also
some minor fixes for the InterfaceKit.Signed-off-by: Sean Young
Signed-off-by: Greg Kroah-Hartman
13 Jul, 2006
1 commit
-
This is a new driver for the Cypress CY7C63xxx mirco controller series.
It currently supports the pre-programmed CYC63001A-PC by AK Modul-Bus
GmbH. It's based on a kernel 2.4 driver (cyport) by Marcus Maul which I
ported to kernel 2.6 using sysfs. I intend to support more controllers
of this family (and more features) as soon as I get hold of the required
IDs etc. Please see the source code's header for more information.Signed-off-by: Oliver Bock
Signed-off-by: Greg Kroah-Hartman
22 Jun, 2006
2 commits
-
This is a new driver for the Cypress CY7C63xxx mirco controller series.
It currently supports the pre-programmed CYC63001A-PC by AK Modul-Bus
GmbH. It's based on a kernel 2.4 driver (cyport) by Marcus Maul which I
ported to kernel 2.6 using sysfs. I intend to support more controllers
of this family (and more features) as soon as I get hold of the required
IDs etc. Please see the source code's header for more information.Signed-off-by: Oliver Bock
Signed-off-by: Greg Kroah-Hartman -
This is a driver to control the brightness of an Apple Cinema Display over
USB. It updates the local brightness value if the user presses a button on
the display.Signed-off-by: Michael Hanselmann
Cc: Oliver Neukum
Cc: Paul Mackerras
Cc: Benjamin Herrenschmidt
Signed-off-by: Andrew Morton
Signed-off-by: Greg Kroah-Hartman
14 Feb, 2006
1 commit
-
Signed-off-by: Michael Hund
Signed-off-by: Greg Kroah-Hartman
13 Jul, 2005
1 commit
-
The following driver provides complete interrupt-in and interrupt-out
reports (raw data) to a user program. Until now it uses the
HIDIOCGDEVINFO ioctl call, because I don't know better :-(. Perhaps, it
will be ok for you - and I will be happy, if you assign 8 minor numbers.I have tested it in several environments and it works very well for me.
However, it has a problem with two or more devices at the same hub, if
the two or more devices need 1 ms interrupt-in transfers. Unfortunately
more than one interrupt-in transfer every ms isn't possible (ehci
driver?). This is why the min_interrupt_in_interval and
min_interrupt_out_interval are increased to 2 ms (see the corresponding
module parameters). This way, I can use two devices simultaneously at
the same hub.Signed-off-by: Michael Hund
Signed-off-by: Greg Kroah-Hartman
17 Apr, 2005
1 commit
-
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.Let it rip!
