On 28 November 2016 at 19:00, Felipe Balbi <felipe.balbi@xxxxxxxxxxxxxxx> wrote: > Instead of always defaulting to a 256-entry array, > we can dynamically allocate devs based on what HW > tells us it supports. > > Note that we can't, yet, purge MAX_HC_SLOTS > completely because of struct > xhci_device_context_array reliance on it. > > Signed-off-by: Felipe Balbi <felipe.balbi@xxxxxxxxxxxxxxx> > --- > drivers/usb/host/xhci-hub.c | 2 +- > drivers/usb/host/xhci-mem.c | 4 ++-- > drivers/usb/host/xhci-ring.c | 2 +- > drivers/usb/host/xhci.c | 19 +++++++++++++++---- > drivers/usb/host/xhci.h | 2 +- > 5 files changed, 20 insertions(+), 9 deletions(-) > > Changes since v1: > - accounted for invalid slot 0 which driver assumes to exist. Tested on my dwc3 platform, it can work well as host role. Tested-by: Baolin Wang <baolin.wang@xxxxxxxxxx> -- Baolin.wang Best Regards -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
