diff options
| author | Olav Kongas <ok@artecdesign.ee> | 2005-08-04 17:02:54 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2005-09-08 16:22:48 -0700 |
| commit | f8d23d309809ae69c763520dababb7e845938272 (patch) | |
| tree | 0c07570e6de7e6978bd336be9fabfe1ecfee802b /include | |
| parent | 9d233d9faedfd8a4ee22288c1fdc698a6f75db21 (diff) | |
| download | kernel_samsung_aries-f8d23d309809ae69c763520dababb7e845938272.zip kernel_samsung_aries-f8d23d309809ae69c763520dababb7e845938272.tar.gz kernel_samsung_aries-f8d23d309809ae69c763520dababb7e845938272.tar.bz2 | |
[PATCH] USB: isp116x-hcd: remove clock() and reset()
This patch removes support for user-provided platform-specific hardware reset
and clock starting/stopping functions. Hardware reset was needed earlier as
getting the software reset working was tricky due to the lack of documentation.
Recently, a number of people using isp116x have said the software reset is
working for them.
I haven't heard of anybody using the clock starting/stopping.
Signed-off-by: Olav Kongas <ok@artecdesign.ee>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'include')
| -rw-r--r-- | include/linux/usb_isp116x.h | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/include/linux/usb_isp116x.h b/include/linux/usb_isp116x.h index 8f0b3c2..436dd8a 100644 --- a/include/linux/usb_isp116x.h +++ b/include/linux/usb_isp116x.h @@ -19,15 +19,6 @@ struct isp116x_platform_data { prevents stopping internal clock, increasing thereby power consumption in suspended state. */ unsigned remote_wakeup_enable:1; - /* Hardware reset set/clear. If implemented, this function must: - if set == 0, deassert chip's HW reset pin - otherwise, assert chip's HW reset pin */ - void (*reset) (struct device * dev, int set); - /* Hardware clock start/stop. If implemented, this function must: - if start == 0, stop the external clock - otherwise, start the external clock - */ - void (*clock) (struct device * dev, int start); /* Inter-io delay (ns). The chip is picky about access timings; it expects at least: 150ns delay between consecutive accesses to DATA_REG, |