- 26 Apr, 2011 40 commits
-
-
Aaro Koskinen authored
Replace orXGIIDXREG() with xgifb_reg_or(). Signed-off-by:
Aaro Koskinen <aaro.koskinen@iki.fi> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Aaro Koskinen authored
Replace outXGIIDXREG() with xgifb_reg_set(). Signed-off-by:
-
Aaro Koskinen authored
Replace inXGIIDXREG() with xgifb_reg_get(). Signed-off-by:
-
Aaro Koskinen authored
Replace outXGIREG() with outb(). Signed-off-by:
-
wwang authored
Call rtsx_clear_sd_error if sd_read_data fail when reading sd lba0. Signed-off-by:
wwang <wei_wang@realsil.com.cn> Signed-off-by:
-
Michał Mirosław authored
Driver sets .get_sg and .get_tx_csum ethtool_ops to their default values anyway. Those fields are deprecated, starting in 2.6.39. Signed-off-by:
Michał Mirosław <mirq-linux@rere.qmqm.pl> Signed-off-by:
-
Jonathan Cameron authored
This was only used for triggering and hence should never have been done this way in the first place. Needs to go prior to cleaning out some of the registration functions. Untested but identical in form to those that have been. Signed-off-by:
Jonathan Cameron <jic23@cam.ac.uk> Acked-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Jonathan Cameron authored
Untested but identical in form to those that have been. Signed-off-by:
-
Jonathan Cameron authored
Untested but identical in form to those that have been. Signed-off-by:
-
Jonathan Cameron authored
Untested but identical in form to those that have been. Signed-off-by:
-
Jonathan Cameron authored
Whilst the adis16204 does indeed support events, currently the driver does not. The trigger code should never use that infrastructure. Untested but identical in form to those that have been. Signed-off-by:
-
Jonathan Cameron authored
Whilst the adis16203 does indeed support events, currently the driver does not. The trigger code should never use that infrastructure. Untested, but identical in form to those that have been so should be fine. Signed-off-by:
-
Jonathan Cameron authored
Whilst the adis16260 does indeed support events, currently the driver does not. The trigger code should never use that infrastructure. Untested - but identical in form to those that have been. Signed-off-by:
-
Jonathan Cameron authored
Whilst the adis16400 does indeed support events, currently the driver does not. The trigger code should never use that infrastructure. Tested indirectly via the IMU driver merge to follow. Signed-off-by:
-
Jonathan Cameron authored
Whilst the adis163500 does indeed support events, currently the driver does not. The trigger code should never use that infrastructure. Signed-off-by:
-
Jonathan Cameron authored
Whilst the adis16300 does indeed support events, currently the driver does not. The trigger code should never use that infrastructure. Tested indirectly via the IMU driver merge to follow. Signed-off-by:
-
Jonathan Cameron authored
Trivial cleanup. Signed-off-by:
-
Jonathan Cameron authored
Signed-off-by:
-
Jonathan Cameron authored
Without this all hell breaks loose if you have no data. Signed-off-by:
-
Jonathan Cameron authored
The only fiddly bit in here was ensuring the regulator was available until after the free had occured. Signed-off-by:
-
Jonathan Cameron authored
Either name is fine, so went with the most common. Signed-off-by:
-
Jonathan Cameron authored
Not only was this not compliant with the abi, it was also missconfiguring the buffer. Signed-off-by:
-
Jonathan Cameron authored
Suggested by Arnd Bergmann. Note this will break ALL drivers that are out of mainline. The fix is trivial change of iio_allocate_device() -> iio_allocate_device(0) Sorry if this causes issues for any one! V2: Include new drivers in the update Signed-off-by:
Arnd Bergmann <arnd@arndb.de> Signed-off-by:
-
Jonathan Cameron authored
Change suggested by Arnd Bergmann, Related patch to remove pointless (now) dead_offset parameter will have await proper fix for the sca3000 driver. That depends on some intermediate patches so may be a little while. Signed-off-by:
-
Jonathan Cameron authored
Signed-off-by:
-
Jonathan Cameron authored
Trivial reorganization. Signed-off-by:
-
Michael Hennerich authored
Signed-off-by:
-
Jon Brenner authored
Added suspend/resume functions. Changed attribute names to match existing where applicable and updated or documented new ABI as discussed. Changed integration time ABI from using index (0 to 3) to use actual gain values (1x,8x, etc.). Removed various unused variables, declarations, and functions. Revised code to accommodate different endianess (le16_to_cpu). Updated error return codes in various functions. Changed from mdelay to msleep after determining that longer wait would be acceptable. V5: Makefile and Kconfig cleanups by Jonathan Cameron. Signed-off-by:
Jon August Brenner <jbrenner@taosinc.com> Acked-by:
-
Michael Hennerich authored
Signed-off-by:
-
Alan Cox authored
For Moorestown at least we may not have stolen RAM with which to back the initial framebuffer. Allow a GEM backing. At this point we should have all the bits in place needed to make it work once it has been debugged. Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
This then kills off the old bo_ interfaces Signed-off-by:
-
Alan Cox authored
Do a first pass over the cursor code and rework it to use GEM objects for the cursor buffer as we need. Signed-off-by:
-
Alan Cox authored
There are two chunks of code we need to do this. The first one is the code to insert and remove the pages from the GART, the second is the code to build page table lists from the GEM object. Surprisingly this latter one doesn't seem to have a nice GEM helper. While we are at it we can begin dismantling the semi redundant struct pg, and finish pruning out the old now unused gtt code as well as the last bits of helper glue from the old driver base. Signed-off-by:
-
Alan Cox authored
This puts in place the infrastructure for GEM allocators. Our implementation is fairly simplistic at this point and we don't deal with things like evicting objects from the GART to make space, nor compaction. We extent our gtt_range struct to include a GEM object and that allows GEM to do all the handle management and most of the memory mapping work for us. This patch also doesn't load GEM pages into the GART so the GEM side isn't very useful. Before we can do that a fair bit of work is needed reworking the internal GTT code. Signed-off-by:
-
Alan Cox authored
We will will need this for doing a GEM allocator. It should also avoid any crashes with the current code if the stolen area is too small. Signed-off-by:
-
Alan Cox authored
Now we can do allocations we need to shuffle the fb resource into the fb so we can one day have multiple frame buffer objects. Signed-off-by:
-
Alan Cox authored
At the moment we don't do any page backing for the GTT so only the stolen area pages will actually work. That is fine for our initial framebuffer and a bit of testing but will need resolution (including alternate mmap methods and the like for s/g areas) eventually. Rather than use some of the overcomplex stuff in the DRM we use the existing Linux resource allocators to hand out framebuffers and the like. This also has the nice result that /proc/iomem shows the allocations. Signed-off-by:
-
Alan Cox authored
The current bl code checks for backlight types and warns if they are not properly set. Set ours to avoid the warning spew (This one alone is probably 2.6.39 candidate) Signed-off-by:
-
