public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <m.chehab@samsung.com>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: "Antti Palosaari" <crope@iki.fi>,
	LMML <linux-media@vger.kernel.org>,
	"Frank Schäfer" <fschaefer.oss@googlemail.com>
Subject: Re: em28xx list_add corruption reported by list debug
Date: Sun, 22 Dec 2013 13:55:31 -0200	[thread overview]
Message-ID: <20131222135531.6af60f77@samsung.com> (raw)
In-Reply-To: <20131222130600.652f468a@samsung.com>

Em Sun, 22 Dec 2013 13:06:00 -0200
Mauro Carvalho Chehab <m.chehab@samsung.com> escreveu:

> Em Sun, 22 Dec 2013 00:27:21 +0200
> Antti Palosaari <crope@iki.fi> escreveu:
> 
> > I ran also this kind of bug. Device was PCTV 290e, which has that video 
> > unused. I have no any analog em28xx webcam to test if that happens here too.
> > 
> > Fortunately I found one video device which does not crash nor dump debug 
> > bug warnings. It is some old gspca webcam. Have to look example how 
> > those videobuf callbacks are implemented there..
> > 
> > regards
> > Antti
> > 
> > 
> > [crope@localhost linux]$ cat /dev/video0
> > cat: /dev/video0: Invalid argument
> > [crope@localhost linux]$ cat /dev/video0
> > cat: /dev/video0: Device or resource busy
> > [crope@localhost linux]$
> > 
> > 
> > joulu 22 00:08:24 localhost.localdomain kernel: em28174 #0: no endpoint 
> > for analog mode and transfer type 0
> 
> It seems that there's something bad on em28174 registration: it should not
> be creating a v4l2 device, if the device is DVB only.
> 
> The thing is that, when this driver was created, all devices were either
> analog only or hybrid. Only very recently, pure DVB devices got added.
> 
> It shouldn't be that hard to split em28xx_init_dev() into a few routines
> that would only register v4l2 if the device has analog support.
> 
> Again, this changeset:
> 	https://patchwork.linuxtv.org/patch/17967/
> 
> Seems to be part of such solution, as it already splits the v4l2
> register logic into a separate function. 

Ok, if I didn't make any mistake, this changeset should do the trick:
	https://patchwork.linuxtv.org/patch/21282/

Please notice that this is compile-tested only.

Regards,
Mauro
-- 

Cheers,
Mauro

  reply	other threads:[~2013-12-22 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21 22:27 em28xx list_add corruption reported by list debug Antti Palosaari
2013-12-22 15:06 ` Mauro Carvalho Chehab
2013-12-22 15:55   ` Mauro Carvalho Chehab [this message]
2013-12-22 16:17     ` Antti Palosaari
2013-12-22 16:22       ` Antti Palosaari
2013-12-22 17:09       ` Mauro Carvalho Chehab

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=20131222135531.6af60f77@samsung.com \
    --to=m.chehab@samsung.com \
    --cc=crope@iki.fi \
    --cc=fschaefer.oss@googlemail.com \
    --cc=linux-media@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