linux-toradex.git/include/linux/dvb/frontend.h, branch v3.3.5

[media] dvb: deprecate the usage of ops->info.type

2012-01-04T19:30:20+00:00

Mark info.type as deprecated inside the header, recommending
the usage of DTV_ENUM_DELSYS DVBv5 command instead.

Signed-off-by: Mauro Carvalho Chehab

[media] dvb-core: be sure that drivers won't use DVBv3 internally

2011-12-31T12:23:01+00:00

Now that all frontends are implementing DVBv5, don't export the
DVBv3 specific stuff to the drivers. Only the core should be
aware of that, as it will keep providing DVBv3 backward compatibility.

Signed-off-by: Mauro Carvalho Chehab

[media] Remove Annex A/C selection via roll-off factor

2011-12-20T13:50:23+00:00

Instead of using a roll-off factor, change DRX-K & friends to select
the bandwidth filter and the Nyquist half roll-off via delivery system.

This provides a cleaner support for Annex A/C switch.

Signed-off-by: Mauro Carvalho Chehab

[media] DVB: Use a unique delivery system identifier for DVBC_ANNEX_C

2011-12-20T13:49:15+00:00

Use a unique delivery system identifier for DVBC_ANNEX_C, just like any
other.

DVBC_ANNEX_A and DVBC_ANNEX_C have slightly different parameters
and are used in 2 geographically different locations.

Signed-off-by: Manu Abraham 
Signed-off-by: Mauro Carvalho Chehab

[media] DVB: Query DVB frontend delivery capabilities

2011-12-12T17:03:32+00:00

 Currently, for any multi-standard frontend it is assumed that it just
 has a single standard capability. This is fine in some cases, but
 makes things hard when there are incompatible standards in conjuction.
 Eg: DVB-S can be seen as a subset of DVB-S2, but the same doesn't hold
 the same for DSS. This is not specific to any driver as it is, but a
 generic issue. This was handled correctly in the multiproto tree,
 while such functionality is missing from the v5 API update.

 http://www.linuxtv.org/pipermail/vdr/2008-November/018417.html

 Later on a FE_CAN_2G_MODULATION was added as a hack to workaround this
 issue in the v5 API, but that hack is incapable of addressing the
 issue, as it can be used to simply distinguish between DVB-S and
 DVB-S2 alone, or another X vs X2 modulation. If there are more systems,
 then you have a potential issue.

 An application needs to query the device capabilities before requesting
 any operation from the device.

Signed-off-by: Manu Abraham 
Acked-by: Andreas Oberritter 
Acked-by: Oliver Endriss 
Signed-off-by: Mauro Carvalho Chehab

[media] dvb: Allow select between DVB-C Annex A and Annex C

2011-11-11T14:46:23+00:00

DVB-C, as defined by ITU-T J.83 has 3 annexes. The differences between
Annex A and Annex C is that Annex C uses a subset of the modulation
types, and uses a different rolloff factor. A different rolloff means
that the bandwidth required is slicely different, and may affect the
saw filter configuration at the tuners. Also, some demods have different
configurations, depending on using Annex A or Annex C.

So, allow userspace to specify it, by changing the rolloff factor.

Signed-off-by: Mauro Carvalho Chehab

[media] DVB: Add SYS_TURBO for north american turbo code FEC

2011-09-03T21:07:14+00:00

Signed-off-by: Andreas Oberritter 
Signed-off-by: Mauro Carvalho Chehab

[media] DVB: Add basic API support for DVB-T2 and bump minor version

2011-05-20T21:51:09+00:00

[steve@stevekerrison.com: Remove private definitions from cxd2820r that existed before API was defined]
Signed-off-by: Andreas Oberritter 
Signed-off-by: Steve Kerrison 
Signed-off-by: Mauro Carvalho Chehab

V4L/DVB: Add FE_CAN_TURBO_FEC

2010-08-02T18:02:12+00:00

Some (North American) providers use a non-standard mode called
"8psk turbo fec". Since there is no flag in the driver that
would allow an application to determine whether a particular
device can handle "turbo fec", the attached patch introduces
FE_CAN_TURBO_FEC.

Since there is no flag in the SI data that would indicate
that a transponder uses "turbo fec", VDR will assume that
all 8psk transponders on DVB-S use "turbo fec".

Tested-by: Derek Kelly 
Signed-off-by: Klaus Schmidinger 
Signed-off-by: Douglas Schilling Landgraf 
Signed-off-by: Mauro Carvalho Chehab

V4L/DVB (12997): Add the DTV_ISDB_TS_ID property for ISDB_S

2009-09-19T03:51:34+00:00

In ISDB-S, time-devision duplex is used to multiplexing several waves
in the same frequency. Each wave is identified by its own transport
stream ID, or TS ID. We need to provide some way to specify this ID
from user applications to handle ISDB-S frontends.

This code has been tested with the Earthsoft PT1 driver.

[mchehab@infradead.org: Fix merge conflicts with isdbt and rename the new parameter to DTV_ISDBS_TS_ID]
Signed-off-by: HIRANO Takahito 
Signed-off-by: Mauro Carvalho Chehab