litmus-rt.git - The LITMUS^RT kernel.

index : litmus-rt.git

The LITMUS^RT kernel.

Bjoern Brandenburg

about summary refs log tree commit diff stats

path: root/lib/fault-inject.c

diff options

author	Angelo Arrifano <miknix@gmail.com>	2009-09-24 19:23:14 -0400
committer	Tony Lindgren <tony@atomide.com>	2009-09-24 19:23:14 -0400
commit	501e9bd5ff00ea726e91cef7df61f889bdec2105 (patch)
tree	86f6cd6534a1239c05e3f518843dbd9db6f08b80 /lib/fault-inject.c
parent	f5ee2fc7931c692da7315d65675399f2e46af1e7 (diff)

omap: Fix a OMAP_MPUIO_VBASE typo for 850

This was crashing omap850 devices. Reported-by: Alistair Buxton <a.j.buxton@gmail.com> Signed-off-by: Angelo Arrifano <miknix@gmail.com> Signed-obb-by: Tony Lindgren <tony@atomide.com>

Diffstat (limited to 'lib/fault-inject.c')

0 files changed, 0 insertions, 0 deletions

ch do the DMA mapping and apply other tweaks to make scatterlist i/o be fast. - Some drivers may prefer to work with the model that they're mapping large buffers, synchronizing their safe re-use. (If there's no re-use, then let usbcore do the map/unmap.) Large periodic transfers make good examples here, since it's cheaper to just synchronize the buffer than to unmap it each time an urb completes and then re-map it on during resubmission. These calls all work with initialized urbs: urb->dev, urb->pipe, urb->transfer_buffer, and urb->transfer_buffer_length must all be valid when these calls are used (urb->setup_packet must be valid too if urb is a control request): struct urb *usb_buffer_map (struct urb *urb); void usb_buffer_dmasync (struct urb *urb); void usb_buffer_unmap (struct urb *urb); The calls manage urb->transfer_dma for you, and set URB_NO_TRANSFER_DMA_MAP so that usbcore won't map or unmap the buffer. The same goes for urb->setup_dma and URB_NO_SETUP_DMA_MAP for control requests.