diff options
| author | Lee Jones <joneslee@google.com> | 2023-01-18 15:49:24 +0000 |
|---|---|---|
| committer | Michael Bestas <mkbestas@lineageos.org> | 2023-04-08 17:12:21 +0200 |
| commit | d1f19956d6b9d29e0355fe10aa8eb29c75a0851a (patch) | |
| tree | fc6d5a7a7cf34d57261c337b6be9b40a80073e7c /tools/perf/scripts/python/check-perf-trace.py | |
| parent | 2d3ce4f7a366c50d2af5bdaf5a0088ec6bc50500 (diff) | |
ANDROID: usb: f_accessory: Check buffer size when initialised via composite
When communicating with accessory devices via USBFS, the initialisation
call-stack looks like:
ConfigFS > Gadget ConfigFS > UDC > Gadget ConfigFS > Composite
Eventually ending up in composite_dev_prepare() where memory for the
data buffer is allocated and initialised. The default size used for the
allocation is USB_COMP_EP0_BUFSIZ (4k). When handling bulk transfers,
acc_ctrlrequest() needs to be able to handle buffers up to
BULK_BUFFER_SIZE (16k). Instead of adding new generic attributes to
'struct usb_request' to track the size of the allocated buffer, we can
simply split off the affected thread of execution to travel via a
knowledgeable abstracted function acc_ctrlrequest_composite() where we
can complete the necessary specific checks.
Bug: 264029575
Signed-off-by: Lee Jones <joneslee@google.com>
Change-Id: Ia1280f85499621d3fa57f7262b4a2c80f4be7773
Signed-off-by: Lee Jones <joneslee@google.com>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions
