public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Andy Walls <awalls@md.metrocast.net>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [RFCv1 PATCH 7/7] tuner-core: s_tuner should not change tuner mode.
Date: Sun, 12 Jun 2011 08:53:06 -0400	[thread overview]
Message-ID: <1307883186.2592.10.camel@localhost> (raw)
In-Reply-To: <201106121430.03114.hverkuil@xs4all.nl>

On Sun, 2011-06-12 at 14:30 +0200, Hans Verkuil wrote:
> On Sunday, June 12, 2011 14:13:30 Mauro Carvalho Chehab wrote:
> > Em 12-06-2011 08:59, Mauro Carvalho Chehab escreveu:
> > > Em 12-06-2011 08:36, Hans Verkuil escreveu:
> > >>>> What about this:
> > >>>>
> > >>>> Opening /dev/radio effectively starts the radio mode. So if there is TV
> > >>>> capture in progress, then the open should return -EBUSY. Otherwise it
> > >>>> switches the tuner to radio mode. And it stays in radio mode until the
> > >>>> last filehandle of /dev/radio is closed. At that point it will automatically
> > >>>> switch back to TV mode (if there is one, of course).
> > >>>
> > >>> No. This would break existing applications. The mode switch should be done
> > >>> at S_FREQUENCY (e. g. when the radio application is tuning into a channel).
> > >>
> > >> This is not what happens today as the switch to radio occurs as soon as you open
> > >> the radio node. It's the reason for the s_radio op.
> > > 
> > > The s_radio op is something that I wanted to remove. It was there in the past to feed
> > > the TV/radio hint logic. I wrote a patch for it, but I ended by discarding from my
> > > final queue (I can't remember why).
> > > 
> > > I think that the hint logic were completely removed, but we may need to take a look
> > > on the callers for s_radio. I'll check it right now.
> > > 
> > 
> > The s_radio callback requires some care, as it is used on several places. It is probably
> > safe to remove it from tuner, but a few sub-drivers like msp3400 needs it. The actual
> > troubles seem to happen at the bridge drivers that call it during open(). It should be
> > called only at s_frequency. I opted to keep the callback just to avoid having a bridge
> > driver switching its registers to radio mode, and not having the tuner following it.
> > 
> > If we move the radio mode switch at the bridge drivers to s_frequency only, we can just
> > remove this callback from tuner, letting it to be implemented only at the audio decoders.
> 
> Why would the audio decoders need it? If we do the mode switch when s_freq is
> called, then the audio decoders can do the same and s_radio can disappear completely.
> 
> I would like that, but I'm a bit afraid of application breakage since we're changing
> the behavior of /dev/radio. It seems that pretty much every video driver with radio
> capability is calling s_radio during open(): bttv, ivtv, saa7134, usbvision, em28xx,
> cx18, cx88, cx231xx and tm6000.

I think ivtvhopper relies on it:

http://www.gateways-home.org/wb/pages/mycoding/--ivtvhopper-java.php

Also, per my recommendation, ivtvhopper changes radio freq by
using /dev/video24, since V4L2 priorities got in the way:

http://ivtvdriver.org/pipermail/ivtv-users/2010-December/010097.html

Regards,
Andy



  reply	other threads:[~2011-06-12 12:52 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-11 13:34 [RFCv1 PATCH 0/7] tuner-core: fix g_freq/s_std and g/s_tuner Hans Verkuil
2011-06-11 13:34 ` [RFCv1 PATCH 1/7] tuner-core: rename check_mode to supported_mode Hans Verkuil
2011-06-11 13:34   ` [RFCv1 PATCH 2/7] tuner-core: change return type of set_mode_freq to bool Hans Verkuil
2011-06-11 13:34   ` [RFCv1 PATCH 3/7] tuner-core: fix g_frequency support Hans Verkuil
2011-06-11 13:44     ` Mauro Carvalho Chehab
2011-06-11 13:53       ` Hans Verkuil
2011-06-11 13:34   ` [RFCv1 PATCH 4/7] tuner-core: simplify the standard fixup Hans Verkuil
2011-06-11 13:34   ` [RFCv1 PATCH 5/7] tuner-core: fix s_std and s_tuner Hans Verkuil
2011-06-11 13:34   ` [RFCv1 PATCH 6/7] tuner-core: fix g_tuner Hans Verkuil
2011-06-11 13:48     ` Mauro Carvalho Chehab
2011-06-11 13:34   ` [RFCv1 PATCH 7/7] tuner-core: s_tuner should not change tuner mode Hans Verkuil
2011-06-11 13:54     ` Mauro Carvalho Chehab
2011-06-11 17:27       ` Hans Verkuil
2011-06-11 18:21         ` Andy Walls
2011-06-11 19:04         ` Mauro Carvalho Chehab
2011-06-12 11:36           ` Hans Verkuil
2011-06-12 11:59             ` Mauro Carvalho Chehab
2011-06-12 12:13               ` Mauro Carvalho Chehab
2011-06-12 12:30                 ` Hans Verkuil
2011-06-12 12:53                   ` Andy Walls [this message]
2011-06-12 13:23                     ` Hans Verkuil
2011-06-12 13:44                       ` Andy Walls
2011-06-12 13:57                         ` Devin Heitmueller
2011-06-12 14:28                           ` Mauro Carvalho Chehab
2011-06-12 15:34                           ` Andy Walls
2011-06-12 17:38                             ` Mauro Carvalho Chehab
2011-06-12 14:06                         ` Hans Verkuil
2011-06-12 12:23               ` Hans Verkuil
2011-06-12 14:11                 ` Mauro Carvalho Chehab
2011-06-12 14:33                   ` Hans Verkuil
2011-06-12 15:29                     ` Andy Walls

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=1307883186.2592.10.camel@localhost \
    --to=awalls@md.metrocast.net \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.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