From: Antti Palosaari <crope@iki.fi>
To: Malcolm Priestley <tvboxspy@gmail.com>
Cc: Mauro Carvalho Chehab <mchehab@redhat.com>, linux-media@vger.kernel.org
Subject: Re: [PATCH 2/3] dvb-usb: multi-frontend support (MFE)
Date: Thu, 28 Jul 2011 01:23:06 +0300 [thread overview]
Message-ID: <4E308FCA.9090509@iki.fi> (raw)
In-Reply-To: <1311804451.9058.20.camel@localhost>
On 07/28/2011 01:07 AM, Malcolm Priestley wrote:
> On Wed, 2011-07-27 at 16:06 -0300, Mauro Carvalho Chehab wrote:
>> Em 25-07-2011 21:17, Antti Palosaari escreveu:
>>> Signed-off-by: Antti Palosaari<crope@iki.fi>
>>> + adap->fe[i] = NULL;
>>> + /* In error case, do not try register more FEs,
>>> + * still leaving already registered FEs alive. */
>>
>> I think that the proper thing to do is to detach everything, if one of
>> the attach fails. There isn't much sense on keeping the device partially
>> initialized.
>>
>> From memory, I recall the existing code doesn't detach the frontend even
> if the device driver forces an error. So, the device driver must detach
> the frontend first.
Yes, if you return for example error (or fe == NULL) for .tuner_attach()
it does not detach or deregister it - just silently discard all. I
thought very many times those when implementing this and keep very
careful not to change old functionality.
> The trouble is that dvb-usb is becoming dated as new drivers tend to
> work around it. No one likes to touch it, out of fear of breaking
> existing drivers.
Yes, so true. I have thought that too. There is a lot of things I want
to change but those are very hard without massive work.
* We should have priv at the very first. No priv for FW DL example.
* Remote keytable should be property of certain device model not adapter
* There should be way to set count of adapter (and fe) in runtime (this
is why I allowed to fail 2nd FE attach silently)
* no probe (read eeprom etc) callback (I think read MAC could be renamed
for probe)
* no FE power control (GPIOs etc) that MFE patch adds this too
* maybe probe1 and probe2 callbacks needed. sequence something like plug
device => probe1 => download FW => probe2 => attach demod
> I think perhaps some kind of legacy wrapper is needed here, with the
> moving of dvb-usb to its own core, so more development work can be done.
Wish like to thank you these comments Malcolm!
regards
Antti
--
http://palosaari.fi/
next prev parent reply other threads:[~2011-07-27 22:23 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
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 [this message]
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=4E308FCA.9090509@iki.fi \
--to=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=tvboxspy@gmail.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