Linux Media Controller development
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	ben.hutchings@codethink.co.uk, gregkh@linuxfoundation.org,
	mchehab@s-opensource.com, linux-media@vger.kernel.org
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] [Patch v2] usbtv: Fix refcounting mixup
Date: Wed, 16 May 2018 11:23:43 +0200	[thread overview]
Message-ID: <1526462623.25281.5.camel@suse.com> (raw)
In-Reply-To: <1ee4b00d-9a55-92cf-e708-1e0c60ca4bfd@xs4all.nl>

Am Dienstag, den 15.05.2018, 18:01 +0200 schrieb Hans Verkuil:
> On 05/15/2018 05:46 PM, Oliver Neukum wrote:
> > Am Dienstag, den 15.05.2018, 16:28 +0200 schrieb Hans Verkuil:
> > > On 05/15/18 15:07, Oliver Neukum wrote:

> > > >  usbtv_audio_fail:
> > > >  	/* we must not free at this point */
> > > > -	usb_get_dev(usbtv->udev);
> > > > +	v4l2_device_get(&usbtv->v4l2_dev);
> > > 
> > > This is very confusing. I think it is much better to move the
> > 
> > Yes. It confused me.
> > 
> > > v4l2_device_register() call from usbtv_video_init to this probe function.
> > 
> > Yes, but it is called here. So you want to do it after registering the
> > audio?
> 
> No, before. It's a global data structure, so this can be done before the
> call to usbtv_video_init() as part of the top-level initialization of the
> driver.

Eh, but we cannot create a V4L device before the first device
is connected and we must certainly create multiple V4L devices if
multiple physical devices are connected.

Maybe I am dense. Please elaborate.
It seem to me that the driver is confusing because it uses
multiple refcounts.

	Regards
		Oliver

  reply	other threads:[~2018-05-16  9:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 13:07 [PATCH] [Patch v2] usbtv: Fix refcounting mixup Oliver Neukum
2018-05-15 14:28 ` Hans Verkuil
2018-05-15 15:46   ` Oliver Neukum
2018-05-15 16:01     ` Hans Verkuil
2018-05-16  9:23       ` Oliver Neukum [this message]
2018-05-16 10:27         ` Hans Verkuil
2020-09-16 13:47           ` Oliver Neukum
2020-09-21  9:10           ` Oliver Neukum

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=1526462623.25281.5.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=ben.hutchings@codethink.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@s-opensource.com \
    --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