From: Antti Palosaari <crope@iki.fi>
To: Mauro Carvalho Chehab <mchehab@redhat.com>,
Michael Krufky <mkrufky@kernellabs.com>
Cc: linux-media@vger.kernel.org,
Jose Alberto Reguero <jareguero@telefonica.net>
Subject: Re: [PATCH 2/3] dvb-usb: multi-frontend support (MFE)
Date: Wed, 07 Sep 2011 19:51:55 +0300 [thread overview]
Message-ID: <4E67A12B.8020908@iki.fi> (raw)
In-Reply-To: <4E360E53.80107@redhat.com>
On 08/01/2011 05:24 AM, Mauro Carvalho Chehab wrote:
> Em 31-07-2011 22:22, Antti Palosaari escreveu:
>> On 08/01/2011 03:46 AM, Mauro Carvalho Chehab wrote:
>>> One bad thing I noticed with the API is that it calls adap->props.frontend_attach(adap)
>>> several times, instead of just one, without even passing an argument for the driver to
>>> know that it was called twice.
>>>
>>> IMO, there are two ways of doing the attach:
>>>
>>> 1) call it only once, and, inside the driver, it will loop to add the other FE's;
>>> 2) add a parameter, at the call, to say what FE needs to be initialized.
>>>
>>> I think (1) is preferred, as it is more flexible, allowing the driver to test for
>>> several types of frontends.
I am planning to change DVB USB MFE call .frontend_attach() only once.
Is there any comments about that?
Currently there is anysee, ttusb2 and cx88 drivers which uses MFE and
change is needed ASAP before more MFE devices are coming.
Also .num_frontends can be removed after that, since DVB USB will just
loop through 0 to MAX FEs and register all FEs found (fe pointer !NULL).
CURRENTLY:
==========
.frontend_attach()
if (adap->fe_adap[0].fe == NULL)
adap->fe_adap[0].fe = dvb_attach(DVB-T)
else if (adap->fe_adap[1].fe == NULL)
adap->fe_adap[1].fe = dvb_attach(DVB-C)
else if (adap->fe_adap[2].fe == NULL)
adap->fe_adap[2].fe = dvb_attach(DVB-S)
PLANNED:
========
.frontend_attach()
adap->fe_adap[0].fe = dvb_attach(DVB-T)
adap->fe_adap[1].fe = dvb_attach(DVB-C)
adap->fe_adap[2].fe = dvb_attach(DVB-S)
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2011-09-07 16:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 0:17 [PATCH 2/3] dvb-usb: multi-frontend support (MFE) Antti Palosaari
2011-07-27 19:06 ` Mauro Carvalho Chehab
2011-07-27 19:49 ` Antti Palosaari
2011-07-27 20:06 ` Mauro Carvalho Chehab
2011-07-27 20:19 ` Antti Palosaari
2011-08-01 0:46 ` Mauro Carvalho Chehab
2011-08-01 1:22 ` Antti Palosaari
2011-08-01 2:24 ` Mauro Carvalho Chehab
2011-09-07 16:51 ` Antti Palosaari [this message]
2011-09-07 17:41 ` Michael Krufky
2011-09-07 17:45 ` Michael Krufky
2011-09-07 18:04 ` Michael Krufky
2011-09-07 18:20 ` Antti Palosaari
2011-09-07 18:36 ` Michael Krufky
2011-09-07 21:10 ` Antti Palosaari
2011-09-07 21:32 ` Michael Krufky
2011-07-27 22:07 ` Malcolm Priestley
2011-07-27 22:23 ` Antti Palosaari
2011-07-31 18:28 ` Patrick Boettcher
2011-08-01 1:28 ` Antti Palosaari
-- strict thread matches above, loose matches on Subject: below --
2011-07-28 21:35 Antti Palosaari
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=4E67A12B.8020908@iki.fi \
--to=crope@iki.fi \
--cc=jareguero@telefonica.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=mkrufky@kernellabs.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