From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
javier@osg.samsung.com,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Greg KH <greg@kroah.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Subject: Re: [PATCH RFC] omap3isp: prevent releasing MC too early
Date: Thu, 15 Dec 2016 10:37:34 -0200 [thread overview]
Message-ID: <20161215103734.716a0619@vento.lan> (raw)
In-Reply-To: <3043978.ViByGAdkJL@avalon>
Em Thu, 15 Dec 2016 14:13:42 +0200
Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
> Hi Mauro,
>
> (CC'ing Greg)
>
> On Wednesday 14 Dec 2016 13:14:06 Mauro Carvalho Chehab wrote:
> > Avoid calling streamoff without having the media structs allocated.
> >
> > Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
>
> The driver has a maintainer listed in MAINTAINERS, and you know that Sakari is
> also actively involved here. You could have CC'ed us.
Yes, sure.
>
> > ---
> >
> > Javier,
> >
> > Could you please test this patch?
> >
> > Thanks!
> > Mauro
> >
> > drivers/media/platform/omap3isp/ispvideo.c | 10 ++++++++--
> > 1 file changed, 8 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/platform/omap3isp/ispvideo.c
> > b/drivers/media/platform/omap3isp/ispvideo.c index
> > 7354469670b7..f60995ed0a1f 100644
> > --- a/drivers/media/platform/omap3isp/ispvideo.c
> > +++ b/drivers/media/platform/omap3isp/ispvideo.c
> > @@ -1488,11 +1488,17 @@ int omap3isp_video_register(struct isp_video *video,
> > struct v4l2_device *vdev) "%s: could not register video device (%d)\n",
> > __func__, ret);
> >
> > + /* Prevent destroying MC before unregistering */
> > + kobject_get(vdev->v4l2_dev->mdev->devnode->dev.parent);
>
> This doesn't even compile. Please make sure to at least compile-test patches
> you send for review, otherwise you end up wasting time for all reviewers and
> testers. I assume you meant
>
> kobject_get(&vdev->mdev->devnode->dev.parent->kobj);
>
> and similarly below.
Yes.
Btw, Javier tested it yesterday with the above fix, but it didn't solve the
issue, because the problem is elsewhere.
What happens is that omap3isp driver calls media_device_unregister()
too early. Right now, it is called at omap3isp_video_device_release(),
with happens when a driver unbind is ordered by userspace, and not after
the last usage of all /dev/video?? devices.
There are two possible fixes:
1) at omap3isp_video_device_release(), streamoff all streams and mark
that the media device will be gone.
2) instead of using video_device_release_empty for the video->video.release,
create a omap3isp_video_device_release() that will call
media_device_unregister() when destroying the last /dev/video?? devnode.
I have a half-baked patch for (2). I'll try to finish it and do some
tests.
Unfortunately, I don't have any OMAP3 device that has a camera
module, except for a N9 device with a damaged display.
Sakari,
Is there a way for me to use the N9 device to test it without a
display? AFAIKT, the device is operational, and I *guess* it is
on developer's mode, but not really sure.
Thanks,
Mauro
next prev parent reply other threads:[~2016-12-15 12:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-14 15:14 [PATCH RFC] omap3isp: prevent releasing MC too early Mauro Carvalho Chehab
2016-12-15 12:13 ` Laurent Pinchart
2016-12-15 12:31 ` Greg KH
2016-12-15 15:07 ` Laurent Pinchart
2016-12-15 16:58 ` Mauro Carvalho Chehab
2016-12-15 12:37 ` Mauro Carvalho Chehab [this message]
2016-12-15 12:42 ` Javier Martinez Canillas
2016-12-15 12:57 ` Mauro Carvalho Chehab
2016-12-15 13:44 ` Greg KH
2016-12-15 14:17 ` Mauro Carvalho Chehab
2016-12-16 8:21 ` Sakari Ailus
2016-12-16 11:44 ` Sakari Ailus
2016-12-15 14:04 ` Laurent Pinchart
2016-12-16 11:18 ` Mauro Carvalho Chehab
2016-12-16 16:06 ` Laurent Pinchart
2016-12-15 13:24 ` 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=20161215103734.716a0619@vento.lan \
--to=mchehab@s-opensource.com \
--cc=greg@kroah.com \
--cc=javier@osg.samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shuahkh@osg.samsung.com \
/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).