Skip to content

usb: sm501 ohci controller patches V4/V2

Magnus Damm linux-sh 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 5 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2usb: dma bounce buffer support V4drivers/usb/core/buffer.c drivers/usb/core/hcd.c drivers/usb/core/hcd.h+163 -230 replies
2/2usb: ohci-sm501 driver V2drivers/usb/host/ohci-hcd.c drivers/usb/host/ohci-sm501.c+269 -05 replies

Reviews trailers per patch

1 of 2 patches has a Reviewed-by or Acked-by.

PatchAlan SternDavid Brownell
1/2A-b A-b
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH][0/2] usb: sm501 ohci controller patches V4/V2

usb: sm501 ohci controller patches V4/V2

[1/2] usb: dma bounce buffer support V4
[2/2] usb: ohci-sm501 driver V2

The sm501 usb host controller is a regular ohci implementation but with the exception that it can only do dma to a certain area of memory. This memory is sm501 specific and the mfd driver for sm501 currently divides this memory between the framebuffer and the usb host controller.

To support the sm501 usb host controller we need to allocate all usb data from this sm501 memory. The function dma_declare_coherent_memory() helps us with that - all dma_alloc_coherent() calls will end up allocating such memory.

The USB core does however allocate data using kmalloc, so to fully support such a behaviour we need dma bounce buffer support. These bounce buffers can be requested using the flag HCD_LOCAL_MEM.

---

 drivers/usb/core/buffer.c     |    9 -
 drivers/usb/core/hcd.c        |  176 ++++++++++++++++++++++++---
 drivers/usb/core/hcd.h        |    1 
 drivers/usb/host/ohci-hcd.c   |    5 
 drivers/usb/host/ohci-sm501.c |  264 +++++++++++++++++++++++++++++++++++++++++
 5 files changed, 432 insertions(+), 23 deletions(-)