- 05 Sep, 2012 10 commits
-
-
Marcus Karlsson authored
Fix spelling in tmem.c: Transcedent -> Transcendent Signed-off-by:
Marcus Karlsson <mk@acc.umu.se> Acked-by:
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Devendra Naga authored
we are dereferencing the pshmem , and the pci_alloc_consistent can fail returning null, do a memcpy if we have a valid pshmem Signed-off-by:
Devendra Naga <devendra.aaru@gmail.com> Signed-off-by:
-
Devendra Naga authored
this function return void, means return at the end of this function is not needed Signed-off-by:
-
Devendra Naga authored
the locked variable is used for checking whether the function acquired lock, then unlock. actually with out this we can achieve the same lock and unlock senario, remove the locked variable and also cleanup the code around. Signed-off-by:
-
Devendra Naga authored
we are returning -ENOENT when there is no firmware file for a matching device id. then we start calling request_firmware, after this we do checks on the firmware length of corresponding device id, since the default case is handled in the begining itself there is no need of a default case at the firmware length checks Signed-off-by:
-
Wei Yongjun authored
Using list_move_tail() instead of list_del() + list_add_tail(). spatch with a semantic match is used to found this problem. (http://coccinelle.lip6.fr/) Signed-off-by:
Wei Yongjun <yongjun_wei@trendmicro.com.cn> Signed-off-by:
-
Wei Yongjun authored
Using list_move_tail() instead of list_del() + list_add_tail(). spatch with a semantic match is used to found this problem. (http://coccinelle.lip6.fr/) Signed-off-by:
-
Samuel Iglesias Gonsálvez authored
Caused by commit 187e4782 ("Staging: ipack: Read the ID space during device registration"). drivers/staging/ipack/ipack.c: In function 'ipack_device_read_id': drivers/staging/ipack/ipack.c:291:2: error: implicit declaration of function 'ioread8' [-Werror=implicit-function-declaration] drivers/staging/ipack/ipack.c:309:3: error: implicit declaration of function 'ioread16be' [-Werror=implicit-function-declaration] Reported-by:
Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by:
Samuel Iglesias Gonsálvez <siglesias@igalia.com> Signed-off-by:
-
Ian Abbott authored
Remove the pointer to the PCI device from the private data `struct das08_private_struct`. Use `comedi_set_hw_dev()` to save a pointer to the PCI device (actually, its embedded `struct device`) and `comedi_to_pci_dev()` to retrieve it. Signed-off-by:
Ian Abbott <abbotti@mev.co.uk> Signed-off-by:
-
Ian Abbott authored
Now that this driver no longer supports "manual" attachment of PCI devices in its `attach` hook (`das08_attach()`), it no longer has code that searches for a suitable PCI device and increments its reference count. Since the driver no longer has any reason for incrementing and decrementing the PCI device's reference count, the calls to `pci_dev_get()` and `pci_dev_put()` can be removed. Signed-off-by:
-
- 04 Sep, 2012 30 commits
-
-
H Hartley Sweeten authored
The addi_amcc_S5920.c file only has the function i_AddiHeaderRW_ReadEeprom() in it. The addi_amcc_S5920.h file has a prototype for this function and a couple defines for the magic numbers used when accessing the eeprom. The .c file is not actually built by any .config selection, or by an The .h file is only #include'd by the hwdrv_apci3200.c file. That file actually has a local version of the i_AddiHeaderRW_ReadEeprom() function that is identical to the one in the .c file. Just move the #define's from the .h file into hwdrv_apci3200.c and remove the addi_amcc_S5920.[ch] files. Signed-off-by:
H Hartley Sweeten <hsweeten@visionengravers.com> Cc: Ian Abbott <abbotti@mev.co.uk> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
-
H Hartley Sweeten authored
Nothing in the comedi subsystem references this header file. It's actually almost a straight copy of the addi_amcc_s5933.h file anyway. Just remove the file. Signed-off-by:
-
H Hartley Sweeten authored
The Makefile for the comedi subsystem does not compile this file for any .config selection. This file would allow building one big driver to support all the addi-data cards. The addi-data drivers are a big enough mess as-is. Just remove this file. Signed-off-by:
-
Jens Taprogge authored
Signed-off-by:
Jens Taprogge <jens.taprogge@taprogge.org> Signed-off-by:
-
Jens Taprogge authored
Also include it in the hotplug event so that udev can provide the respective driver. Signed-off-by:
-
Jens Taprogge authored
Devices are match based upon their vendor and device ids. Since the individual drivers provide a list of supported ids they do not need to implement the matching themselves. Signed-off-by:
-
Jens Taprogge authored
The modalias entries for the module are now created. Signed-off-by:
-
Jens Taprogge authored
Signed-off-by:
-
Jens Taprogge authored
Rename them in the process. Signed-off-by:
-
Jens Taprogge authored
Also expose the values through sysfs. Signed-off-by:
-
Jens Taprogge authored
We keep a copy of the ID space for later use. Signed-off-by:
-
Jens Taprogge authored
The modaliases look like ipack:fXvNdM, where X is the format version (8 bit) and N and M are the vendor and device ID represented as 32 bit hexadecimal numbers each. Using 32 bits allows us to define IPACK_ANY_ID as (~0) without interfering with the valid ids. The resulting modalias string for ipoctal.ko looks like this (once ipoctal provides a device table): alias: ipack:f01v000000F0d00000048* alias: ipack:f01v000000F0d0000002A* alias: ipack:f01v000000F0d00000022* (output from modinfo) Signed-off-by:
-
Jens Taprogge authored
No need to have a struct when it has only one field. Signed-off-by:
-
Jens Taprogge authored
Define memory address space, fix sparse warnings and mark the structs reflecting hardware memory layout "packed" to be on the safe side. Signed-off-by:
-
Samuel Iglesias Gonsálvez authored
They are not used any longer. Signed-off-by:
-
Jens Taprogge authored
They are not used any longer. Signed-off-by:
-
Jens Taprogge authored
Before it was using the functions in ipack_bus_ops. Signed-off-by:
-
Jens Taprogge authored
During initialization we configure the TPCI200 so it does not swap data lanes on IndustryPack module access. The read and write functions are changed accordingly. We are taking this approach in the hope that all IP Carriers are able to present the Module memory layout unchanged. We can thus directly access the memory and registers of IP Modules without having to rely on the read and write wrappers currently exposed in ipack_bus_opts. A later patch will convert the existing driver and remove the wrappers. Signed-off-by:
-
Jens Taprogge authored
These changes make it easier to add more initialization steps later on. Signed-off-by:
-
Devendra Naga authored
the kzalloc does allocates memory and sets the data at the memory which is allocated to 0, The driver does uses the kmalloc and memset at some points in the code replace them with a single call to kzalloc Signed-off-by:
Marcos Paulo de Souza <marcos.souza.org@gmail.com> Signed-off-by:
-
Devendra Naga authored
as per Documentation/CodingStyle, casting of void pointer to any other pointer is not needed Signed-off-by:
-
Priit Laes authored
Signed-off-by:
Priit Laes <plaes@plaes.org> Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
Priit Laes authored
Signed-off-by:
-
