summaryrefslogtreecommitdiffstats
path: root/drivers/media/video/pwc
diff options
context:
space:
mode:
authorAndres Salomon <dilinger@queued.net>2007-09-19 02:44:18 -0300
committerMauro Carvalho Chehab <mchehab@infradead.org>2007-10-09 22:14:49 -0300
commit23869e236846657415654e8f5fbda9faec8d19e4 (patch)
tree4a8b81e51670712760643c0930783b1fa2ae3e1a /drivers/media/video/pwc
parent4562fbeac61468f80a8d05e5ed50660bd97b4859 (diff)
downloadblackbird-op-linux-23869e236846657415654e8f5fbda9faec8d19e4.tar.gz
blackbird-op-linux-23869e236846657415654e8f5fbda9faec8d19e4.zip
V4L/DVB (6235): cafe_ccic: default to allocating DMA buffers at probe time
By default, we allocate DMA buffers when actually reading from the video capture device. On a system with 128MB or 256MB of ram, it's very easy for that memory to quickly become fragmented. We've had users report having 30+MB of memory free, but the cafe_ccic driver is still unable to allocate DMA buffers. Our workaround has been to make use of the 'alloc_bufs_at_load' parameter to allocate DMA buffers during device probing. This patch makes DMA buffer allocation happen during device probe by default, and changes the parameter to 'alloc_bufs_at_read'. The camera hardware is there, if the cafe_ccic driver is enabled/loaded it should do its best to ensure that the camera is actually usable; delaying DMA buffer allocation saves an insignicant amount of memory, and causes the driver to be much less useful. Signed-off-by: Andres Salomon <dilinger@debian.org> Acked-by: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Mauro Carvalho Chehab <mchehab@infradead.org>
Diffstat (limited to 'drivers/media/video/pwc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud