kernel.git/drivers/dma/dw_dmac.c, branch linux-3.8.y

Drivers: dma: remove __dev* attributes.

2013-01-03T23:57:15Z

CONFIG_HOTPLUG is going away as an option. As a result, the __dev* markings need to be removed. This change removes the use of __devinit, __devexit_p, __devinitconst, and __devexit from these drivers. Based on patches originally written by Bill Pemberton, but redone by me in order to handle some of the coding style issues better, by hand. Cc: Bill Pemberton Cc: Viresh Kumar Cc: Dan Williams Cc: Vinod Koul Cc: Barry Song Cc: Jeff Kirsher Cc: Alexander Duyck Cc: Russell King Cc: Linus Walleij Cc: Jassi Brar Cc: Dave Jiang Cc: Bill Pemberton Cc: Guennadi Liakhovetski Signed-off-by: Greg Kroah-Hartman

dma: remove use of __devinit

2012-11-28T20:42:36Z

CONFIG_HOTPLUG is going away as an option so __devinit is no longer needed. Signed-off-by: Bill Pemberton Cc: Li Yang Cc: Zhang Wei Cc: Barry Song Acked-by: Viresh Kumar Signed-off-by: Greg Kroah-Hartman

dma: remove use of __devexit_p

2012-11-28T20:41:36Z

CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer needed. Signed-off-by: Bill Pemberton Acked-by: Barry Song Acked-by: Viresh Kumar Acked-by: Russell King Signed-off-by: Greg Kroah-Hartman

dw_dmac: fix a regression in dwc_prep_dma_memcpy

2012-10-02T07:48:00Z

Sometimes memory-to-memory test is failed, that's why we need to choose minimum data portion between source and destination limits together. Signed-off-by: Andy Shevchenko Signed-off-by: Vinod Koul

dw_dmac: introduce software emulation of LLP transfers

2012-09-27T10:05:23Z

Some controllers have the reduced functionality where the LLP multi block transfers are not supported. This patch introduces a support of such controllers. In case of memory copy or scatter-gather lists it emulates LLP transfers via bunch of the regular single block ones. Signed-off-by: Andy Shevchenko Acked-by: Viresh Kumar Signed-off-by: Vinod Koul

dw_dmac: autoconfigure data_width or get it via platform data

2012-09-27T10:05:23Z

Not all of the controllers support the 64 bit data width. Make it configurable via platform data. The driver will try to get a value from the component parameters, otherwise it will use the platform data. Signed-off-by: Andy Shevchenko Acked-by: Viresh Kumar Signed-off-by: Vinod Koul

dw_dmac: autoconfigure block_size or use platform data

2012-09-27T10:05:23Z

The maximum block size is a configurable parameter for the chip. So, driver will try to get it from the encoded component parameters. Otherwise it will come from the platform data. Signed-off-by: Andy Shevchenko Acked-by: Viresh Kumar Signed-off-by: Vinod Koul

dw_dmac: get number of channels from hardware if possible

2012-09-27T10:05:23Z

In case the controller has the encoded parameters feature enabled the driver will use it to get the number of channels. In the future it will be used for the other important parameters as well. Signed-off-by: Andy Shevchenko Acked-by: Viresh Kumar Signed-off-by: Vinod Koul

dw_dmac: mark dwc_dump_chan_regs as inline

2012-09-27T10:05:22Z

Signed-off-by: Andy Shevchenko Acked-by: Viresh Kumar Signed-off-by: Vinod Koul

dw_dmac: utilize slave_id to pass request line

2012-09-14T02:59:46Z

There is slave_id field in the generic slave config structure that is dedicated for the uniq slave number. In our case we have the request lines wired to the certain hardware. Therefore the number of the request line is uniq and could be used as slave_id. It allows us in some cases to drop out the usage of the custom slave config structure. Signed-off-by: Andy Shevchenko Acked-by: Viresh Kumar Signed-off-by: Vinod Koul