1. 04 Jul, 2014 17 commits
  2. 26 Jun, 2014 1 commit
  3. 19 Jun, 2014 9 commits
  4. 17 Jun, 2014 13 commits
    • James Hogan's avatar
      [media] rc: img-ir: Expand copyright headers with GPL notices · 2ac6f630
      James Hogan authored
      Add the basic GPLv2+ license notice to the copyright headers at the top
      of all the source files in the img-ir driver.
      Reported-by: default avatarDavid Härdeman <david@hardeman.nu>
      Signed-off-by: default avatarJames Hogan <james.hogan@imgtec.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      2ac6f630
    • Jean Delvare's avatar
      [media] V4L2: soc_camera: Add run-time dependencies to sh_mobile drivers · 163438b8
      Jean Delvare authored
      The sh_mobile_ceu_camera and sh_mobile_csi2 drivers are only useful on
      SuperH and shmobile unless build testing.
      Signed-off-by: default avatarJean Delvare <jdelvare@suse.de>
      Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      163438b8
    • Alexander Shiyan's avatar
      [media] media: mx2_camera: Change Kconfig dependency · 50f06b88
      Alexander Shiyan authored
      This patch change MACH_MX27 dependency to SOC_IMX27 for MX2 camera
      driver, since MACH_MX27 symbol is scheduled for removal.
      Signed-off-by: default avatarAlexander Shiyan <shc_work@mail.ru>
      Signed-off-by: default avatarGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      50f06b88
    • Alexander Shiyan's avatar
      [media] media: mx1_camera: Remove driver · 90b05589
      Alexander Shiyan authored
      That driver hasn't been really maintained for a long time. It doesn't
      compile in any way, it includes non-existent headers, has no users,
      and marked as "BROKEN" more than year. Due to these factors, mx1_camera
      is now removed from the tree.
      Signed-off-by: default avatarAlexander Shiyan <shc_work@mail.ru>
      Signed-off-by: default avatarGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      90b05589
    • Jean Delvare's avatar
      [media] V4L2: soc_camera: add run-time dependencies to R-Car VIN driver · 0b911999
      Jean Delvare authored
      The R-Car Video Input driver is only useful on shmobile unless build
      testing.
      Signed-off-by: default avatarJean Delvare <jdelvare@suse.de>
      Cc: Vladimir Barinov <vladimir.barinov@cogentembedded.com>
      Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
      Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      0b911999
    • Ben Dooks's avatar
      [media] rcar_vin: copy flags from pdata · 25dfa02c
      Ben Dooks authored
      The platform data is a single word, so simply copy
      it into the device's private data structure than
      keeping a copy of the pointer.
      
      This will make changing to device-tree binding
      easier as it is one allocation instead of two.
      Signed-off-by: default avatarBen Dooks <ben.dooks@codethink.co.uk>
      Signed-off-by: default avatarGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      25dfa02c
    • Guennadi Liakhovetski's avatar
      [media] V4L: soc-camera: explicitly free allocated managed memory on error · 057c2a2e
      Guennadi Liakhovetski authored
      devm_kzalloc() allocations are freed when the device is unbound. But if a
      certain path fails and the allocated memory cannot be used anyway it is
      better to free it explicitly immediately. This patch does exactly this if
      asynchronous group probing in scan_async_group() fails after memory has
      been allocated.
      Signed-off-by: default avatarGuennadi Liakhovetski <g.liakhovetski@gmx.de>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      057c2a2e
    • Mauro Carvalho Chehab's avatar
      [media] dib7000p: Callibrate signal strength · 3926d91a
      Mauro Carvalho Chehab authored
      Calibrate the signal strength to dB.
      
      For this callibration, I used adapter 0 (antenna 1), connected
      via a normal cable to a DTF-2111 generator.
      
      The same cabling and RF generator connected to adapter 1
      (antenna 2) has a difference of +3dBm (signal was stronger
      there).
      
      Yet, changing the RF for a difference of, let's say, 6dB
      reflected on a 6dB difference at the measured signal, with
      is good.
      
      So, the signal strengh can indeed be used to measure the
      antenna gain, if the antenna is repositioned. It is
      not precise to measure the absolute dBm value, however.
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      3926d91a
    • Mauro Carvalho Chehab's avatar
      [media] dib7000p: Add DVBv5 stats support · 041ad449
      Mauro Carvalho Chehab authored
      Adds DVBv5 stats support. For now, just mimic whatever dib8000
      does, as they're very similar, with regards to statistics.
      
      However, dib7000p_get_time_us() likely require some
      adjustments, as I didn't actually reviewed the formula
      for it to work with DVB-T. Still, better than nothing,
      as latter patches can improve it.
      
      This patch also doesn't show the signal strength in dB
      yet. The code is already there, but it requires to be
      callibrated.
      
      A latter patch will do the calibration.
      
      It seems that this patch is also a bug fix: Before this
      patch, the frontend were not tuning with some userspace
      tools. I suspect that dib7000p firmware or hardware
      internally expects that the statistics to be collected,
      in order for it to work. With this patch, the DVB core
      will always retrive statistics, even if userspace doesn't
      request. So, it makes the device work on all tested apps.
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      041ad449
    • Mauro Carvalho Chehab's avatar
      [media] dib8000: export just one symbol · d44913c1
      Mauro Carvalho Chehab authored
      Exporting multiple symbols don't work as it causes compilation
      breakages, due to the way dvb_attach() works.
      
      The bug happens when:
              CONFIG_DVB_DIB8000=m
      	CONFIG_DVB_USB_DIB0700=y
      
      As a bonus, dib8000 won't be loaded anymore if the device uses
      a different frontend, reducing the memory footprint.
      
      Tested with both Pixelview PV-D231 and MyGica S870.
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      d44913c1
    • Mauro Carvalho Chehab's avatar
      [media] dib8000: rename dib8000_attach to dib8000_init · b9bc7d59
      Mauro Carvalho Chehab authored
      Well, what we call as "foo_attach" is the method that should
      be called by the dvb_attach() macro.
      
      It should be noticed that the name "dvb_attach" is really a
      bad name and don't express what it does.
      
      dvb_attach() basically does three things, if the frontend is
      compiled as a module:
      - It lookups for the module that it is known to have the
        given symbol name and requests such module;
      - It increments the module usage (anonymously - so lsmod
        doesn't print who loaded the module);
      - after loading the module, it runs the function associated
        with the dynamic symbol.
      
      When compiled as builtin, it just calls the function given to it.
      
      As dvb_attach() increments refcount, it can't be (easily)
      called more than once for the same module, or the kernel
      will deny to remove the module, because refcount will never
      be zeroed.
      
      In other words, the function name given to dvb_attach()
      should be one single symbol that will always be called
      before any other function on that module to be used.
      
      For almost all DVB frontends, there's just one function,
      but, on dib8000, there are several exported symbols.
      
      We need to get rid of all those direct calls, because they
      cause compilation breakages when bridge is builtin and
      frontend is module, we'll need to add a new function that
      will be the first one to be called, whatever initialization
      is needed.
      
      So, let's rename this function, in order to prepare for
      a next patch that will add a new attach() function that
      will be the only one exported by this module.
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      b9bc7d59
    • Mauro Carvalho Chehab's avatar
      [media] dib7000: export just one symbol · 8abe4a0a
      Mauro Carvalho Chehab authored
      Exporting multiple symbols don't work as it causes compilation
      breakages, due to the way dvb_attach() works.
      
      This were reported several times, like:
      
         drivers/built-in.o: In function `cxusb_dualdig4_rev2_tuner_attach':
      >> cxusb.c:(.text+0x27d4b5): undefined reference to `dib7000p_get_i2c_master'
         drivers/built-in.o: In function `dib7070_set_param_override':
         cxusb.c:(.text+0x27d5a5): undefined reference to `dib0070_wbd_offset'
      >> cxusb.c:(.text+0x27d5be): undefined reference to `dib7000p_set_wbd_ref'
         drivers/built-in.o: In function `dib7070_tuner_reset':
      >> cxusb.c:(.text+0x27d5f9): undefined reference to `dib7000p_set_gpio'
         drivers/built-in.o: In function `cxusb_dualdig4_rev2_frontend_attach':
      >> cxusb.c:(.text+0x27df5c): undefined reference to `dib7000p_i2c_enumeration'
      
      In this specific report:
      	CONFIG_DVB_USB_CXUSB=y
      	CONFIG_DVB_DIB7000P=m
      
      But the same type of bug can happen if:
      	CONFIG_DVB_DIB7000P=m
      and one of the bridge drivers is compiled builtin (cxusb, cx23885-dvb
      and/or dib0700).
      
      As a bonus, dib7000p won't be loaded anymore if the device uses
      a different frontend, reducing the memory footprint.
      
      Tested with Hauppauge Nova-TD (2 frontends).
      Reported-by: default avatarFengguang Wu <fengguang.wu@intel.com>
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      8abe4a0a
    • Mauro Carvalho Chehab's avatar
      [media] dib7000p: rename dib7000p_attach to dib7000p_init · 7f67d96a
      Mauro Carvalho Chehab authored
      Well, what we call as "foo_attach" is the method that should
      be called by the dvb_attach() macro.
      
      It should be noticed that the name "dvb_attach" is really a
      bad name and don't express what it does.
      
      dvb_attach() basically does three things, if the frontend is
      compiled as a module:
      - It lookups for the module that it is known to have the
        given symbol name and requests such module;
      - It increments the module usage (anonymously - so lsmod
        doesn't print who loaded the module);
      - after loading the module, it runs the function associated
        with the dynamic symbol.
      
      When compiled as builtin, it just calls the function given to it.
      
      As dvb_attach() increments refcount, it can't be (easily)
      called more than once for the same module, or the kernel
      will deny to remove the module, because refcount will never
      be zeroed.
      
      In other words, the function name given to dvb_attach()
      should be one single symbol that will always be called
      before any other function on that module to be used.
      
      For almost all DVB frontends, there's just one function.
      
      However, the dib7000p initialization can require up to 3
      functions to be called:
      	- dib7000p_get_i2c_master;
      	- dib7000p_i2c_enumeration;
      	- dib7000p_init (before this patch dib7000_attach).
      
      (plus a bunch of other functions that the bridge driver will
      need to call).
      
      As we need to get rid of all those direct calls, because they
      cause compilation breakages when bridge is builtin and
      frontend is module, we'll need to add a new function that
      will be the first one to be called, whatever initialization
      is needed.
      
      So, let's rename the function that probes and init the hardware
      to dib7000p_init.
      
      A latter patch will add a new dib7000p_attach that will be
      used as originally conceived by dvb_attach() way.
      Signed-off-by: default avatarMauro Carvalho Chehab <m.chehab@samsung.com>
      7f67d96a