Em 11-11-2011 13:06, Andreas Oberritter escreveu:
> On 11.11.2011 15:43, Mauro Carvalho Chehab wrote:
>> Em 11-11-2011 12:30, Andreas Oberritter escreveu:
>>> On 11.11.2011 07:26, Manu Abraham wrote:
>>>> diff -r b6eb04718aa9 linux/drivers/media/dvb/dvb-core/dvb_frontend.c
>>>> --- a/linux/drivers/media/dvb/dvb-core/dvb_frontend.c Wed Nov 09 19:52:36 2011 +0530
>>>> +++ b/linux/drivers/media/dvb/dvb-core/dvb_frontend.c Fri Nov 11 06:05:40 2011 +0530
>>>> @@ -973,6 +973,8 @@
>>>> _DTV_CMD(DTV_GUARD_INTERVAL, 0, 0),
>>>> _DTV_CMD(DTV_TRANSMISSION_MODE, 0, 0),
>>>> _DTV_CMD(DTV_HIERARCHY, 0, 0),
>>>> +
>>>> + _DTV_CMD(DTV_DELIVERY_CAPS, 0, 0),
>>>> };
>>>>
>>>> static void dtv_property_dump(struct dtv_property *tvp)
>>>> @@ -1226,7 +1228,11 @@
>>>> c = &cdetected;
>>>> }
>>>>
>>>> + dprintk("%s\n", __func__);
>>>> +
>>>> switch(tvp->cmd) {
>>>> + case DTV_DELIVERY_CAPS:
>>>
>>> It would be nice to have a default implementation inserted at this point, e.g. something like:
>>>
>>> static void dtv_set_default_delivery_caps(const struct dvb_frontend *fe, struct dtv_property *p)
>>> {
>>> const struct dvb_frontend_info *info = &fe->ops.info;
>>> u32 ncaps = 0;
>>>
>>> switch (info->type) {
>>> case FE_QPSK:
>>> p->u.buffer.data[ncaps++] = SYS_DVBS;
>>> if (info->caps & FE_CAN_2G_MODULATION)
>>> p->u.buffer.data[ncaps++] = SYS_DVBS2;
>>> if (info->caps & FE_CAN_TURBO_FEC)
>>> p->u.buffer.data[ncaps++] = SYS_TURBO;
>>> break;
>>> case FE_QAM:
>>> p->u.buffer.data[ncaps++] = SYS_DVBC_ANNEX_AC;
>>> break;
>>> case FE_OFDM:
>>> p->u.buffer.data[ncaps++] = SYS_DVBT;
>>> if (info->caps & FE_CAN_2G_MODULATION)
>>> p->u.buffer.data[ncaps++] = SYS_DVBT2;
>>> break;
>>> case FE_ATSC:
>>> if (info->caps & (FE_CAN_8VSB | FE_CAN_16VSB))
>>> p->u.buffer.data[ncaps++] = SYS_ATSC;
>>> if (info->caps & (FE_CAN_QAM_16 | FE_CAN_QAM_64 | FE_CAN_QAM_128 | FE_CAN_QAM_256))
>>> p->u.buffer.data[ncaps++] = SYS_DVBC_ANNEX_B;
>>> }
>>>
>>> p->u.buffer.len = ncaps;
>>> }
>>>
>>> I think this would be sufficient for a lot of drivers and would thus save a lot of work.
>>>
>>>> + break;
>>>> case DTV_FREQUENCY:
>>>> tvp->u.data = c->frequency;
>>>> break;
>>>> @@ -1350,7 +1356,7 @@
>>>> if (r < 0)
>>>> return r;
>>>> }
>>>> -
>>>> +done:
>>>
>>> This label is unused now and should be removed.
>>>
>>>> dtv_property_dump(tvp);
>>>>
>>>> return 0;
>>>> diff -r b6eb04718aa9 linux/drivers/media/dvb/frontends/stb0899_drv.c
>>>> --- a/linux/drivers/media/dvb/frontends/stb0899_drv.c Wed Nov 09 19:52:36 2011 +0530
>>>> +++ b/linux/drivers/media/dvb/frontends/stb0899_drv.c Fri Nov 11 06:05:40 2011 +0530
>>>> @@ -1605,6 +1605,22 @@
>>>> return DVBFE_ALGO_CUSTOM;
>>>> }
>>>>
>>>> +static int stb0899_get_property(struct dvb_frontend *fe, struct dtv_property *p)
>>>> +{
>>>> + switch (p->cmd) {
>>>> + case DTV_DELIVERY_CAPS:
>>>> + p->u.buffer.data[0] = SYS_DSS;
>>>> + p->u.buffer.data[1] = SYS_DVBS;
>>>> + p->u.buffer.data[2] = SYS_DVBS2;
>>>> + p->u.buffer.len = 3;
>>>> + break;
>>>> + default:
>>>> + return -EINVAL;
>>>
>>> You should ignore all unhandled properties. Otherwise all properties handled
>>> by the core will have result set to -EINVAL.
>>
>> IMHO, the better is to set all parameters via stb0899_get_property(). We should
>> work on deprecate the old way, as, by having all frontends implementing the
>> get/set property ops, we can remove part of the legacy code inside the DVB core.
>
> I'm not sure what "legacy code" you're referring to. If you're referring
> to the big switch in dtv_property_process_get(), which presets output
> values based on previously set tuning parameters, then no, please don't
> deprecate it. It doesn't improve driver code if you move this switch
> down into every driver.
What I mean is that drivers should get rid of implementing get_frontend() and
set_frontend(), restricting the usage of struct dvb_frontend_parameters for DVBv3
calls from userspace.
In other words, it should be part of the core logic to get all the parameters
passed from userspace and passing them via one single call to something similar
to set_property.
In other words, ideally, the implementation for DTV set should be
like:
static int dtv_property_process_set(struct dvb_frontend *fe,
struct dtv_property *tvp,
struct file *file)
{
struct dtv_frontend_properties *c = &fe->dtv_property_cache;
switch(tvp->cmd) {
case DTV_CLEAR:
dvb_frontend_clear_cache(fe);
break;
case DTV_FREQUENCY:
c->frequency = tvp->u.data;
break;
case DTV_MODULATION:
c->modulation = tvp->u.data;
break;
case DTV_BANDWIDTH_HZ:
c->bandwidth_hz = tvp->u.data;
break;
...
case DTV_TUNE:
/* interpret the cache of data */
if (fe->ops.new_set_frontend) {
r = fe->ops.new_set_frontend(fe);
if (r < 0)
return r;
}
break;
E. g. instead of using the struct dvb_frontend_parameters, the drivers would
use struct dtv_frontend_properties (already stored at the frontend
struct as fe->dtv_property_cache).
Btw, with such change, it would actually make sense the original proposal
from Manu of having a separate callback for supported delivery systems.
> Of course, a driver can and should override any property it knows about
> in its get_property callback, if - and only if - the property value
> possibly differs from the value set by the default implementation in
> dvb_frontend.
>
> However, all of this is out of scope of Manu's patch.
Yes. The above change would require more work than what the current
patch is trying to address.
Regards,
Mauro
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
