The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Hans de Goede <hdegoede@redhat.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, Douglas Anderson <dianders@chromium.org>
Subject: Re: [PATCH v3 1/2] media: uvcvideo: Fix deferred probing error
Date: Wed, 23 Apr 2025 02:05:13 +0300	[thread overview]
Message-ID: <20250422230513.GX17813@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCuO+dHOBtW4yvy1n25QWEs-WdQ9H8Lh2rUtcPbUq3hBkQ@mail.gmail.com>

On Wed, Apr 23, 2025 at 06:50:10AM +0800, Ricardo Ribalda wrote:
> On Wed, 23 Apr 2025 at 02:06, Laurent Pinchart wrote:
> > On Thu, Mar 13, 2025 at 12:20:39PM +0000, Ricardo Ribalda wrote:
> > > uvc_gpio_parse() can return -EPROBE_DEFER when the GPIOs it depends on
> > > have not yet been probed. This return code should be propagated to the
> > > caller of uvc_probe() to ensure that probing is retried when the required
> > > GPIOs become available.
> > >
> > > Currently, this error code is incorrectly converted to -ENODEV,
> > > causing some internal cameras to be ignored.
> > >
> > > This commit fixes this issue by propagating the -EPROBE_DEFER error.
> > >
> > > Cc: stable@vger.kernel.org
> > > Fixes: 2886477ff987 ("media: uvcvideo: Implement UVC_EXT_GPIO_UNIT")
> > > Reviewed-by: Douglas Anderson <dianders@chromium.org>
> > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> > > ---
> > >  drivers/media/usb/uvc/uvc_driver.c | 27 +++++++++++++++++++--------
> > >  1 file changed, 19 insertions(+), 8 deletions(-)
> > >
> > > diff --git a/drivers/media/usb/uvc/uvc_driver.c b/drivers/media/usb/uvc/uvc_driver.c
> > > index deadbcea5e227c832976fd176c7cdbfd7809c608..e966bdb9239f345fd157588ebdad2b3ebe45168d 100644
> > > --- a/drivers/media/usb/uvc/uvc_driver.c
> > > +++ b/drivers/media/usb/uvc/uvc_driver.c
> > > @@ -2231,13 +2231,16 @@ static int uvc_probe(struct usb_interface *intf,
> > >  #endif
> > >
> > >       /* Parse the Video Class control descriptor. */
> > > -     if (uvc_parse_control(dev) < 0) {
> > > +     ret = uvc_parse_control(dev);
> > > +     if (ret < 0) {
> > > +             ret = -ENODEV;
> >
> > Why do you set ret to -ENODEV here...
> >
> > >               uvc_dbg(dev, PROBE, "Unable to parse UVC descriptors\n");
> > >               goto error;
> > >       }
> > >
> > >       /* Parse the associated GPIOs. */
> > > -     if (uvc_gpio_parse(dev) < 0) {
> > > +     ret = uvc_gpio_parse(dev);
> > > +     if (ret < 0) {
> > >               uvc_dbg(dev, PROBE, "Unable to parse UVC GPIOs\n");
> > >               goto error;
> > >       }
> > > @@ -2263,24 +2266,32 @@ static int uvc_probe(struct usb_interface *intf,
> > >       }
> > >
> > >       /* Register the V4L2 device. */
> > > -     if (v4l2_device_register(&intf->dev, &dev->vdev) < 0)
> > > +     ret = v4l2_device_register(&intf->dev, &dev->vdev);
> > > +     if (ret < 0)
> >
> > ... but not here ? The code below is also not very consistant.
> 
> For all the "external" functions I was looking into populating their
> error code to probe(). Other drivers (check vivid for example) do
> exactly this.
> 
> There is more value in returning the real cause of the error (ENOMEM,
> EINVAL) that the plain ENODEV.

Yes, I got that, my question was why you override the return value of
e.g. uvc_parse_control() or uvc_scan_device() with -ENODEV, but not for
e.g. uvc_gpio_parse() or v4l2_device_register(). There's no explanation
in the commit message regarding why they're treated differently.

> > >               goto error;
> > >
> > >       /* Scan the device for video chains. */
> > > -     if (uvc_scan_device(dev) < 0)
> > > +     if (uvc_scan_device(dev) < 0) {
> > > +             ret = -ENODEV;
> > >               goto error;
> > > +     }
> > >
> > >       /* Initialize controls. */
> > > -     if (uvc_ctrl_init_device(dev) < 0)
> > > +     if (uvc_ctrl_init_device(dev) < 0) {
> > > +             ret = -ENODEV;
> > >               goto error;
> > > +     }
> > >
> > >       /* Register video device nodes. */
> > > -     if (uvc_register_chains(dev) < 0)
> > > +     if (uvc_register_chains(dev) < 0) {
> > > +             ret = -ENODEV;
> > >               goto error;
> > > +     }
> > >
> > >  #ifdef CONFIG_MEDIA_CONTROLLER
> > >       /* Register the media device node */
> > > -     if (media_device_register(&dev->mdev) < 0)
> > > +     ret = media_device_register(&dev->mdev);
> > > +     if (ret < 0)
> > >               goto error;
> > >  #endif
> > >       /* Save our data pointer in the interface data. */
> > > @@ -2314,7 +2325,7 @@ static int uvc_probe(struct usb_interface *intf,
> > >  error:
> > >       uvc_unregister_video(dev);
> > >       kref_put(&dev->ref, uvc_delete);
> > > -     return -ENODEV;
> > > +     return ret;
> > >  }
> > >
> > >  static void uvc_disconnect(struct usb_interface *intf)

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2025-04-22 23:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 12:20 [PATCH v3 0/2] media: uvcvideo: Fix Fix deferred probing error Ricardo Ribalda
2025-03-13 12:20 ` [PATCH v3 1/2] media: uvcvideo: " Ricardo Ribalda
2025-04-22 18:06   ` Laurent Pinchart
2025-04-22 22:50     ` Ricardo Ribalda
2025-04-22 23:05       ` Laurent Pinchart [this message]
2025-04-22 23:18         ` Ricardo Ribalda
2025-04-28 13:28           ` Hans de Goede
2025-03-13 12:20 ` [PATCH v3 2/2] media: uvcvideo: Use dev_err_probe for devm_gpiod_get_optional Ricardo Ribalda
2025-04-22 18:08   ` Laurent Pinchart
2025-04-07 13:33 ` [PATCH v3 0/2] media: uvcvideo: Fix Fix deferred probing error Hans de Goede

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=20250422230513.GX17813@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=dianders@chromium.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+huawei@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ribalda@chromium.org \
    --cc=stable@vger.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