From: Ricardo Ribalda <ribalda@chromium.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans de Goede <hdegoede@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Ricardo Ribalda <ribalda@chromium.org>
Subject: [PATCH 2/4] media: uvcvideo: Refactor uvc_queue_streamon
Date: Fri, 09 May 2025 18:24:14 +0000 [thread overview]
Message-ID: <20250509-uvc-followup-v1-2-73bcde30d2b5@chromium.org> (raw)
In-Reply-To: <20250509-uvc-followup-v1-0-73bcde30d2b5@chromium.org>
Do uvc_pm_get before we call uvc_queue_streamon. Although the current
code is correct, uvc_ioctl_streamon is allways called after uvc_pm_get,
this change makes the code more resiliant to future changes.
Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
---
drivers/media/usb/uvc/uvc_v4l2.c | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/media/usb/uvc/uvc_v4l2.c b/drivers/media/usb/uvc/uvc_v4l2.c
index 668a4e9d772c6d91f045ca75e2744b3a6c69da6b..862b4e34e5b629cf324479a9bb59ebe8784ccd5d 100644
--- a/drivers/media/usb/uvc/uvc_v4l2.c
+++ b/drivers/media/usb/uvc/uvc_v4l2.c
@@ -853,15 +853,16 @@ static int uvc_ioctl_streamon(struct file *file, void *fh,
if (handle->is_streaming)
return 0;
- ret = uvc_queue_streamon(&stream->queue, type);
+ ret = uvc_pm_get(stream->dev);
if (ret)
return ret;
- ret = uvc_pm_get(stream->dev);
+ ret = uvc_queue_streamon(&stream->queue, type);
if (ret) {
- uvc_queue_streamoff(&stream->queue, type);
+ uvc_pm_put(stream->dev);
return ret;
}
+
handle->is_streaming = true;
return 0;
--
2.49.0.1015.ga840276032-goog
next prev parent reply other threads:[~2025-05-09 18:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 18:24 [PATCH 0/4] media: uvcvideo: Follow-up patches for next-media-uvc-20250509 Ricardo Ribalda
2025-05-09 18:24 ` [PATCH 1/4] media: uvcvideo: Refactor uvc_ctrl_set_handle() Ricardo Ribalda
2025-05-23 8:53 ` Laurent Pinchart
2025-05-23 10:58 ` Ricardo Ribalda
2025-05-23 12:04 ` Laurent Pinchart
2025-05-26 13:30 ` [PATCH v1.1 " Laurent Pinchart
2025-05-09 18:24 ` Ricardo Ribalda [this message]
2025-05-23 8:54 ` [PATCH 2/4] media: uvcvideo: Refactor uvc_queue_streamon Laurent Pinchart
2025-05-09 18:24 ` [PATCH 3/4] media: uvcvideo: Refactor uvc_v4l2_compat_ioctl32 Ricardo Ribalda
2025-05-23 11:56 ` Laurent Pinchart
2025-05-09 18:24 ` [PATCH 4/4] media: uvcvideo: Populate all errors in uvc_probe() Ricardo Ribalda
2025-05-23 11:57 ` Laurent Pinchart
2025-05-23 12:24 ` Ricardo Ribalda
2025-05-23 12:58 ` Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250509-uvc-followup-v1-2-73bcde30d2b5@chromium.org \
--to=ribalda@chromium.org \
--cc=hdegoede@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).