usb: gadget: uvc: configfs: Add bFrameIndex attributes
PATCH 2/2 usb: gadget: uvc: configfs: Add bFrameIndex attributes
Hi Joel,
Quoted 116 lines · On Sunday, 10 June 2018 14:06:28 EEST Joel Pepper wrote:
@Laurent, I accidentally hit "Reply" instead of "Reply All", please disregard the previous copy of this email
Hi Laurent and Paul,
Quoted 72 lines · Laurent Pinchart
Hi Joel and Paul,
Quoted 69 lines · On Friday, 8 June 2018 22:12:56 EEST Laurent Pinchart wrote:
From: Paul Elder <[email protected]>
The UVC frame descriptions are numbered using the descriptor's bFrameIndex field. The index is used in UVC requests, and is thus needed to handle requests in userspace. Make it dynamically discoverable by exposing it in a bFrameIndex configfs attribute of the frame config item.
However, the bFrameIndex value is never set to begin with. Set these values when linking the stream class header in the configfs hierarchy, and store it in the config item private data.
Signed-off-by Paul Elder <[email protected]>---
drivers/usb/gadget/function/uvc_configfs.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)(quoted diff) +0
-0
b/drivers/usb/gadget/function/uvc_configfs.cindex0ad6ea57d0b7..882d9963b244100644drivers/usb/gadget/function/uvc_configfs.c +2
-0@@ -1152,6 +1152,8 @@ UVC_ATTR(uvcg_frame_, cname, aname);#define noop_conversion (x) (x) +UVCG_FRAME_ATTR_RO (b_frame_index, bFrameIndex, noop_conversion, + noop_conversion,8 ); UVCG_FRAME_ATTR(bm_capabilities, bmCapabilities, noop_conversion,drivers/usb/gadget/function/uvc_configfs.c +1
-0noop_conversion, 8);UVCG_FRAME_ATTR (w_width, wWidth, le16_to_cpu, cpu_to_le16,16 );@@ -1298,6 +1300,7 @@ static ssize_t uvcg_frame_dw_frame_interval_store(struct config_item *item,UVC_ATTR (uvcg_frame_, dw_frame_interval, dwFrameInterval);static struct configfs_attribute *uvcg_frame_attrs[] = { + &uvcg_frame_attr_b_frame_index,drivers/usb/gadget/function/uvc_configfs.c +3
-2&uvcg_frame_attr_bm_capabilities, &uvcg_frame_attr_w_width, &uvcg_frame_attr_w_height,@@ -2130,12 +2133,15 @@ static int __uvcg_fill_strm(void *priv1, void *priv2, void *priv3, int n, sizeof(*frm->dw_frame_interval);memcpy (*dest, frm->dw_frame_interval, sz); *dest += sz; -if (frm->fmt_type ==UVCG_UNCOMPRESSED ) +if (frm->fmt_type ==UVCG_UNCOMPRESSED ) { h->bLength =UVC_DT_FRAME_UNCOMPRESSED_SIZE ( frm->frame.b_frame_interval_type); -else if (frm->fmt_type ==UVCG_MJPEG ) + frm->frame.b_frame_index = n +1 ; + }else if (frm->fmt_type ==UVCG_MJPEG ) { h->bLength =UVC_DT_FRAME_MJPEG_SIZE ( frm->frame.b_frame_interval_type);Quoted 8 lines
drivers/usb/gadget/function/uvc_configfs.c
Quoted 6 lines
drivers/usb/gadget/function/uvc_configfs.c +2
-0+ frm->frame.b_frame_index = n +1 ; + } }break ; }This approach looks simpler to me than the patch that Joel submitted.
However,
Quoted 3 lines
this patch lacks ABI documentation, which is included in Joel's patch.
Joel, as you were first, I propose taking your patch and modifying it
with the
Quoted 2 lines
approach followed here, using the
UVCG_FRAME_ATTR_ROmacro and settingb_frame_indexin__uvcg_fill_strm(). Would that be OK with you ? Or isthere a
Quoted 1 line
reason why the approach taken in your patch would be better ?
I've compared Paul's implementation to mine, and as far as I can tell, they are functionally equivalent except for two points:
1) I specifically opted against using a generic
UVCG_FRAME_ATTR_ROmacro, because the index has no well defined value until they are all set at once, as such reading the attribute beforehand should return-EBUSYbefore that point (instead of 1 for all indexes, which would be the case now). All other attributes can be read immediately after creation. Because my approach sets the frame indexes when the parent format is linked, I check thetarget_fmt->linkedflag; For Paul's approach we would have to check whether__uvcg_fill_strm()has already been called. Considering, that the format indices are set in the same fashion, we should probably do the same for bFormatIndex.
Quoted 7 lines
2) My approach creates the bFrameIndexes as soon as a format has been finalized and linked. Depending on how an application sets up the gadget, this might make it easier to take note of the created indices at the earliest possible time instead of rescanning everything at the end. I do not think however this is a significant enough advantage to warrant taking a different approach compared to the way format indices are already being set.
Those are very valid points. I agree that your version is better.