kernel/linux.git/drivers/usb/misc/usb3503.c, branch v4.9.331

usb: misc: usb3503: make sure reset is low for at least 100us

2018-01-17T08:38:55+00:00

commit b8626f1dc29d3eee444bfaa92146ec7b291ef41c upstream. When using a GPIO which is high by default, and initialize the driver in USB Hub mode, initialization fails with: [ 111.757794] usb3503 0-0008: SP_ILOCK failed (-5) The reason seems to be that the chip is not properly reset. Probe does initialize reset low, however some lines later the code already set it back high, which is not long enouth. Make sure reset is asserted for at least 100us by inserting a delay after initializing the reset pin during probe. Signed-off-by: Stefan Agner Signed-off-by: Greg Kroah-Hartman

usb: misc: usb3503: Clean up on driver unbind

2016-06-08T05:19:59+00:00

The driver should clean up after itself by unpreparing the clock when it is unbound. Signed-off-by: Krzysztof Kozlowski Reviewed-by: Javier Martinez Canillas Signed-off-by: Greg Kroah-Hartman

usb: misc: usb3503: Set platform data

2016-06-08T05:19:59+00:00

Driver supports two paths of device instantiation: as platform and i2c device. In the platform path it lacks of storing the driver specific structure as drvdata. Signed-off-by: Krzysztof Kozlowski Signed-off-by: Greg Kroah-Hartman

usb: misc: usb3503: Use i2c_add_driver helper macro

2015-10-25T02:53:53+00:00

Use i2c_add_driver as it will add THIS_MODULE for us. Signed-off-by: Andrew F. Davis Signed-off-by: Greg Kroah-Hartman

usb/misc/usb3503: Always read refclk frequency from DT

2015-03-26T09:50:52+00:00

This is necessary to set REF_SEL appropriately in uses where refclk is always available. Signed-off-by: Ben Gamari Acked-by: Marek Szyprowski Signed-off-by: Greg Kroah-Hartman

Merge tag 'driver-core-3.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core

2014-12-15T00:10:09+00:00

Pull driver core update from Greg KH: "Here's the set of driver core patches for 3.19-rc1. They are dominated by the removal of the .owner field in platform drivers. They touch a lot of files, but they are "simple" changes, just removing a line in a structure. Other than that, a few minor driver core and debugfs changes. There are some ath9k patches coming in through this tree that have been acked by the wireless maintainers as they relied on the debugfs changes. Everything has been in linux-next for a while" * tag 'driver-core-3.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (324 commits) Revert "ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries" fs: debugfs: add forward declaration for struct device type firmware class: Deletion of an unnecessary check before the function call "vunmap" firmware loader: fix hung task warning dump devcoredump: provide a one-way disable function device: Add dev__once variants ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries ath: use seq_file api for ath9k debugfs files debugfs: add helper function to create device related seq_file drivers/base: cacheinfo: remove noisy error boot message Revert "core: platform: add warning if driver has no owner" drivers: base: support cpu cache information interface to userspace via sysfs drivers: base: add cpu_device_create to support per-cpu devices topology: replace custom attribute macros with standard DEVICE_ATTR* cpumask: factor out show_cpumap into separate helper function driver core: Fix unbalanced device reference in drivers_probe driver core: fix race with userland in device_add() sysfs/kernfs: make read requests on pre-alloc files use the buffer. sysfs/kernfs: allow attributes to request write buffer be pre-allocated. fs: sysfs: return EGBIG on write if offset is larger than file size ...

usb: misc: usb3503: delete unnecessary 'out of memory' messages

2014-11-03T23:42:05+00:00

The memory subsystem has already had similar message for it. Signed-off-by: Peter Chen Signed-off-by: Greg Kroah-Hartman

usb: misc: drop owner assignment from platform_drivers

2014-10-20T14:21:49+00:00

A platform_driver does not need to set an owner, it will be populated by the driver core. Signed-off-by: Wolfram Sang

usb3503: clarify what the registers 'PDS' and 'CFG1' really do

2014-09-24T05:15:18+00:00

The current comment sounds like you have to disable some of the ports to be able to use self-powered mode. This is misleading, so change the wording to reflect this. Signed-off-by: Tobias Jakobi Signed-off-by: Greg Kroah-Hartman

usb3503: correct error message in probe ('connect' to 'interrupt')

2014-09-24T05:15:18+00:00

intn is obviously the interrupt pin. Signed-off-by: Tobias Jakobi Signed-off-by: Greg Kroah-Hartman