All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
	Mauro Carvalho Chehab <mchehab@redhat.com>,
	Andreas Oberritter <obi@linuxtv.org>
Subject: Re: PATCH 12/13: 0012-CXD2820r-Query-DVB-frontend-delivery-capabilities
Date: Tue, 22 Nov 2011 00:28:15 +0200	[thread overview]
Message-ID: <4ECAD07F.9010708@iki.fi> (raw)
In-Reply-To: <CAHFNz9KmxyBB4nRQZg1RdU+6wXHmaR9WHejuMqp6g9qrXykjQQ@mail.gmail.com>

Hello

On 11/21/2011 11:09 PM, Manu Abraham wrote:
>   	/* program tuner */
> -	if (fe->ops.tuner_ops.set_params)
> -		fe->ops.tuner_ops.set_params(fe, params);
> +	tstate.delsys = SYS_DVBC_ANNEX_AC;
> +	tstate.frequency = c->frequency;
> +
> +	if (fe->ops.tuner_ops.set_state) {
> +		fe->ops.tuner_ops.set_state(fe,
> +					    DVBFE_TUNER_DELSYS    |
> +					    DVBFE_TUNER_FREQUENCY,
> +					&tstate);

I want to raise that point, switch from .set_params() to .set_state() 
when programming tuner. I don't see it reasonable to introduce (yes, it 
have existed ages but not used) new way to program tuner.

Both demod and tuner got same params;
.set_frontend(struct dvb_frontend *, struct dvb_frontend_parameters *)
.set_params(struct dvb_frontend *, struct dvb_frontend_parameters *)

and can get access to APIv5 property_cache similarly. Both, demod and 
tuner, can read all those params that are now passed using .set_state()

There is some new tuner drivers which are already using APIv5.


regards
Antti

-- 
http://palosaari.fi/

  reply	other threads:[~2011-11-21 22:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21 21:09 PATCH 12/13: 0012-CXD2820r-Query-DVB-frontend-delivery-capabilities Manu Abraham
2011-11-21 22:28 ` Antti Palosaari [this message]
2011-11-21 23:01   ` Manu Abraham
2011-11-21 23:13     ` Michael Krufky
2011-11-22 14:38       ` Antti Palosaari
2011-11-25  1:53     ` 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=4ECAD07F.9010708@iki.fi \
    --to=crope@iki.fi \
    --cc=abraham.manu@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=obi@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.