- 08 Dec, 2011 40 commits
-
-
Aaro Koskinen authored
Delete XGIfb_GetXG21LVDSData() and code which duplicates xgifb_read_vbios(). Signed-off-by:
Aaro Koskinen <aaro.koskinen@iki.fi> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Aaro Koskinen authored
Rename the function to xgifb_read_vbios(). Signed-off-by:
-
Aaro Koskinen authored
Only a single LVDS table entry is needed by the driver. Signed-off-by:
-
Aaro Koskinen authored
Check the BIOS size to avoid out of bounds array access. Disable LVDS in case errors are detected. Signed-off-by:
-
Aaro Koskinen authored
Use u8 for video BIOS data. Signed-off-by:
-
Aaro Koskinen authored
Delete a redundant struct member. Signed-off-by:
-
Aaro Koskinen authored
Delete a redundant struct member. Signed-off-by:
-
Aaro Koskinen authored
We need the video BIOS only on XG21 and only during the init, so let's do everything at the same place. Signed-off-by:
-
Aaro Koskinen authored
Remove video BIOS access from the routine, use the flag instead which is initialized according to the BIOS data. Signed-off-by:
-
Aaro Koskinen authored
Use a pointer variable to make some lines shorter and more readable. Signed-off-by:
-
Aaro Koskinen authored
Rename pVideoMemory to vbios, and also remove volatile at the same go. Signed-off-by:
-
Aaro Koskinen authored
Use ARRAY_SIZE. Signed-off-by:
-
Aaro Koskinen authored
Rearrange code to avoid deep nesting. Signed-off-by:
-
Aaro Koskinen authored
If the count (j) is 0xff, just do the loop once. Signed-off-by:
-
Greg Kroah-Hartman authored
-
Lars-Peter Clausen authored
When updating the scan mask we have to check the actual scan mask for if the channel is already enabled, not the matching scan mask from the available scan masks. The bit will already be set there and as a result the actual scan mask will not get updated and the channel stays disabled. Also fix the return value of iio_scan_el_store which would return 1 instead of the number of bytes written if the channel was already active in the scan mask. Acked-by:
Jonathan Cameron <jic23@kernel.org> Signed-off-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Greg Kroah-Hartman authored
-
Lars-Peter Clausen authored
The sw_ring does not properly handle the case where the write pointer already has wrapped around, the read pointer has not and the remaining buffer space at the end is enough to fill the read buffer: +-----------------------------------+ | | |##data##| | +-----------------------------------+ write_p read_p In this case the current code will copy all available data to the buffer and as a result will write beyond the bounds of the buffer and cause a memory corruption. To address this issue this patch adds code to calculate the available buffer space and makes sure that the number of bytes to copy does not exceed this number. This allows the code which copies the data around to be simplified as it only has to consider two cases: Read wraps around and read does not wrap around. Signed-off-by: -
Lars-Peter Clausen authored
Fix a small typo in the iio_modifer enum. Signed-off-by:
-
Jonathan Cameron authored
These docs have lagged recent developments. Signed-off-by:
-
Jonathan Cameron authored
In all existing cases, the calls are coming from a location where the indio_dev is already available. Signed-off-by:
-
Jonathan Cameron authored
Now buffers do not have a specific dev structure, this is garbage. Signed-off-by:
Jonathan Cameron <jic23@cam.ac.uk> Signed-off-by:
-
Jonathan Cameron authored
No longer needed now we don't allow sysfs acccess to buffer data. Signed-off-by:
-
Jonathan Cameron authored
No longer needed as we don't have drivers providing sysfs access to buffered data. Signed-off-by:
-
Jonathan Cameron authored
No known use case and makes in kernel interface work more complex. Signed-off-by:
-
Jonathan Cameron authored
No known use case and makes in kernel interface work more complex. Signed-off-by:
-
Jonathan Cameron authored
No known use case and complicates in kernel interface work. Signed-off-by:
-
Jonathan Cameron authored
No known usecase and makes in kernel interface work more complex. Signed-off-by:
-
Jonathan Cameron authored
No known use case and complicates in kernel interface work. Signed-off-by:
-
Jonathan Cameron authored
No known use case and complicates in kernel interface work. Signed-off-by:
-
Jonathan Cameron authored
No known use case and complicates in kernel interface work. Signed-off-by:
-
Jonathan Cameron authored
No known use case and complicates in kernel interface work. Signed-off-by:
-
Jonathan Cameron authored
No obvious usecase and complicates in kernel interface work. Signed-off-by:
-
Jonathan Cameron authored
Legacy of having multiple chrdevs that never got cleaned up. Signed-off-by:
-
Jonathan Cameron authored
Obviously drivers should only use this for pushing to buffers. They need buffer->scan_mask for pulling from them post demux. Signed-off-by:
-
Jonathan Cameron authored
These callbacks should not be buffer instance specific. Hence move them out of the buffer. Signed-off-by:
-
Jonathan Cameron authored
There are no known reasons why userspace should want this value. It can be established from the buffer description anyway. Signed-off-by:
-
Jonathan Cameron authored
Has no remaining users. Signed-off-by:
-
Jonathan Cameron authored
Kind of obvious for this device but useful for testing purposes. Signed-off-by:
-
Jonathan Cameron authored
This allows for matching against the name given on a datasheet, however silly/inconsistent it might be. Useful for in kernel interfaces. Signed-off-by:
-
