An error occurred fetching the project authors.
  1. 31 Dec, 2011 3 commits
    • Mauro Carvalho Chehab's avatar
      [media] dvb-core: allow demods to specify the supported delsys · eeacf147
      Mauro Carvalho Chehab authored
      The dvb were originally written for DVB-T/C/S and ATSC. So,
      the original frontend struct has fields to describe only those three
      standards.
      
      While 2nd gen standards are similar to these, new standards
      like DSS, ISDB and CTTB don't fit on any of the above types.
      
      While there's a way for the drivers to explicitly change whatever
      default DELSYS were filled inside the core, still a fake value is
      needed there, and a "compat" code to allow DVBv3 applications to
      work with those delivery systems is needed. This is good for a
      short term solution, while applications aren't using DVBv5 directly.
      
      However, at long term, this is bad, as the compat code runs even
      if the application is using DVBv5. Also, the compat code is not
      perfect, and only works when the frontend is capable of auto-detecting
      the parameters that aren't visible by the faked delivery systems.
      
      So, let the frontend fill the supported delivery systems at the
      device properties directly.
      
      The future plan is that the drivers will stop filling ops->info.type,
      filling, instead, ops->delsys. This will allow multi-frontend
      devices like drx-k to use just one frontend structure for all supported
      delivery systems.
      
      Of course, the core will keep using it, in order to keep allowing
      DVBv3 calls.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      eeacf147
    • Mauro Carvalho Chehab's avatar
      [media] tuners: remove dvb_frontend_parameters from set_params() · 14d24d14
      Mauro Carvalho Chehab authored
      This is a big patch, yet trivial: now that all tuners use the DVBv5
      way to pass parameters (e. g. via fe->dtv_property_cache), the
      extra parameter can be removed from set_params() call.
      
      After this change, very few DVBv3 specific stuff are left at the
      tuners.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      14d24d14
    • Mauro Carvalho Chehab's avatar
      [media] dvb: remove dvb_frontend_parameters from calc_regs() · 249fa0b0
      Mauro Carvalho Chehab authored
      The calc_regs() callback is used by a few frontends (mt352, nxt200x,
      digitv and zl10353). On all places it is called, the parameters are
      set by DVBv5 way. So, just use the DVBv5 struct and remove the
      extra parameter.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      249fa0b0
  2. 03 Sep, 2011 1 commit
    • Mauro Carvalho Chehab's avatar
      [media] dvb-core, tda18271c2dd: define get_if_frequency() callback · 8513e144
      Mauro Carvalho Chehab authored
      Tuners in general convert a high frequency carrier into an Intermediate
      Frequency (IF).
      
      Digital tuners like tda18271, xc3028, etc. generally allow changing the IF
      frequency, although they generally have recommented settings for the IF.
      Analog tuners, have a fixed IF frequency, that depends on the physical
      characteristics of some analog components.
      
      For digital tuners, it makes sense to have ways to configure IF,
      via the tuner's configuration structure, like what's done inside the
      tda18271-fe maps.
      
      The demods need to know what IF is used by the tuner, as it will need
      to convert internally from IF into baseband. Currently, the bridge driver
      needs to fill a per-demod configuration struct for it, or pass it via
      a dvb_attach parameter.
      
      The tda18271 datasheet recommends to use different IF's for different
      delivery system types and for different bandwidths.
      
      The DRX-K demod also needs to know the IF frequency in order to work,
      just like all other demods. However, as it accepts different delivery
      systems (DVB-C and DVB-T), the IF may change if the standard and/or
      bandwidth is changed.
      
      So, the usual procedure of passing it via a config struct doesn't work.
      
      One might try to code it as two separate IF frequencies, or even as a
      table in function of the delivery system and the bandwidth, but this
      will be messy.
      
      So, it is better and simpler to just add a new callback for it and
      require the tuners that can be used with MFE frontends like drx-k
      to implement a new callback to return the used IF.
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      Acked-by: default avatarAntti Palosaari <crope@iki.fi>
      8513e144
  3. 20 May, 2011 1 commit
  4. 21 Mar, 2011 1 commit
  5. 21 Oct, 2010 1 commit
  6. 30 Mar, 2010 1 commit
    • Tejun Heo's avatar
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo authored
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: default avatarTejun Heo <tj@kernel.org>
      Guess-its-ok-by: default avatarChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  7. 09 Feb, 2010 1 commit
  8. 04 Dec, 2009 1 commit
  9. 19 Sep, 2009 2 commits
  10. 29 Dec, 2008 1 commit
  11. 17 Oct, 2008 1 commit
    • Steven Toth's avatar
      V4L/DVB (9222): S2API: Add Multiple-frontend on a single adapter support. · 363c35fc
      Steven Toth authored
      A detailed description from the original patches 2 years ago:
      
      "The WinTV-HVR3000 has a single transport bus which is shared between
      a DVB-T and DVB-S modulator. These patches build on the bus acquisition
      cx88 work from a few weeks ago to add support for this.
      
      So to applications the HVR3000 looks like this:
      /dev/dvb/adapter0/fe0 (cx24123 DVB-S demod)
      /dev/dvb/adapter0/fe1 (cx22702 DVB-T demod)
      
      Additional boards continue as before, eg:
      /dev/dvb/adapter1/fe0 (lgdt3302 ATSC demod)
      
      The basic change is removing the single instance of the videobuf_dvb in
      cx8802_dev and saa7134_dev(?) and replacing it with a list and some
      supporting functions.
      
      *NOTE* This branch was taken before v4l-dvb was closed for 2.6.19 so
      two or three current cx88 patches appear to be reversed by this tree,
      this will be cleaned up in the near future. The patches missing change
      the mutex handing to core->lock, fix an enumeration problem."
      
      It should be recognised that a number of people have been maintaining
      this patchset. Significant levels of Kudos to everyone one involved,
      including but not limited to:
      
      Darron Broad
      Fabio M. Di Nitto
      Carlo Scarfoglio
      Hans Werner
      
      Without the work of these people, and countless others, my two year old
      patches would of died on the Mercurial linuxtv.org vine a long time
      ago.
      
      TODO: Revise these patches a little further so that the need for
      demux1 and dvr0 is optional, not mandatory on the HVR3000.
      
      HISTORY (darron):
      This is the last update to MFE prepared by Hans which is based
      upon the `scratchpad' diff created by Carlo.
      All MFE work prior to that point must be attributed to Fabio
      who ported and maintained Steve's original patch up to that
      time.
      Signed-off-by: default avatarSteven Toth <stoth@linuxtv.org>
      Signed-off-by: default avatarDarron Broad <darron@kewl.org>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@redhat.com>
      363c35fc
  12. 12 Oct, 2008 8 commits
  13. 25 Jan, 2008 6 commits
  14. 10 Oct, 2007 3 commits
  15. 18 Jul, 2007 1 commit
  16. 03 Oct, 2006 1 commit
  17. 26 Sep, 2006 2 commits
  18. 25 Jun, 2006 4 commits
  19. 02 Apr, 2006 1 commit
    • Andrew de Quincey's avatar
      V4L/DVB (3673): Fix budget-av CAM reset · 86f40cc3
      Andrew de Quincey authored
      Unfortunately on the budget-av board, the CAM reset line is tied to the
      frontend reset line, so resetting the CAM also zaps the frontend. This
      breaks the tda1004x at least, and causes it to fail to tune until the
      budget-av module is reloaded. This patch adds an exported function to dvb_frontend
      that allows a card to forcibly reinitialise a frontend. The budget-av now
      does this on CAM reset, which corrects this problem.
      since they do not tie the CAM reset line to the frontend reset line.
      Signed-off-by: default avatarAndrew de Quincey <adq_dvb@lidskialf.net>
      Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@infradead.org>
      86f40cc3