1. 04 11月, 2014 1 次提交
  2. 31 10月, 2014 7 次提交
  3. 28 7月, 2014 2 次提交
  4. 23 8月, 2013 1 次提交
  5. 17 6月, 2013 1 次提交
  6. 24 3月, 2013 3 次提交
  7. 19 3月, 2013 1 次提交
  8. 06 3月, 2013 7 次提交
  9. 28 12月, 2012 1 次提交
  10. 16 8月, 2012 1 次提交
  11. 31 7月, 2012 1 次提交
  12. 11 1月, 2012 2 次提交
    • M
      [media] cx231xx: fix device disconnect checks · 990862a2
      Mauro Carvalho Chehab 提交于
      The driver were using DEV_MISCONFIGURED on some places, and
      DEV_DISCONNECTED on others. In a matter of fact, DEV_MISCONFIGURED
      were set only during the usb disconnect callback, with
      was confusing.
      
      Also, the alsa driver never checks if the device is present,
      before doing some dangerous things.
      
      Remove DEV_MISCONFIGURED, replacing it by DEV_DISCONNECTED.
      
      Also, fixes the other usecases for DEV_DISCONNECTED.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      990862a2
    • M
      [media] cx231xx: Fix unregister logic · 7528cd27
      Mauro Carvalho Chehab 提交于
      There are several weirdness at the unregister logic.
      
      First of all, IR has a poll thread. This thread needs to be
      removed, as it uses some resources associated to the main driver.
      So, the driver needs to explicitly unregister the I2C client for
      ir-kbd-i2c.
      
      If, for some reason, the driver needs to wait for a close()
      to happen, not all memories will be freed, because the free
      logic were in the wrong place.
      
      Also, v4l2_device_unregister() seems to be called too early,
      as devices are still using it.
      
      Finally, even with the device disconnected, there is one
      USB function call that will still try to talk with it.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      7528cd27
  13. 28 7月, 2011 3 次提交
    • D
      [media] cx231xx: Fix power ramping issue · 44ecf1df
      Devin Heitmueller 提交于
      On platforms that have CONFIG_HZ set to 100, the power ramp time effectively
      ends up being 10ms.  However, on those that have a higher CONFIG_HZ, the time
      ends up *actually* being 5ms, which doesn't allow enough time for the hardware
      to be fully powered up before attempting to address it via i2c.
      
      Change the constant to 10ms, which is long enough for the hardware to power
      up, and won't really be anymore time than it was previously on platforms
      with CONFIG_HZ being 100.
      
      Credit goes to Mauro Carvalho Chehab and Gerd Hoffmann who previously
      investigated this issue.
      
      Tested with the Hauppauge USBLive 2, with which the problem was readily
      reproducible after setting CONFIG_HZ to 1000.
      Signed-off-by: NDevin Heitmueller <dheitmueller@kernellabs.com>
      Cc: Mauro Carvalho Chehab <mchehab@redhat.com>
      Cc: Gerd Hoffmann <kraxel@redhat.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      44ecf1df
    • M
      [media] Stop using linux/version.h on most video drivers · 1990d50b
      Mauro Carvalho Chehab 提交于
      All the modified drivers didn't have any version increment since
      Jan, 1 2011. Several of them didn't have any version increment
      for a long time, even having new features and important bug fixes
      happening.
      
      As we're now filling the QUERYCAP version with the current Kernel
      Release, we don't need to maintain a per-driver version control
      anymore. So, let's just use the default.
      
      In order to preserve the Kernel module version history, a
      KERNEL_VERSION() macro were added to all modified drivers, and
      the extraver number were incremented.
      
      I opted to preserve the per-driver version control to a few
      pwc, pvrusb2, s2255, s5p-fimc and sh_vou.
      
      A few drivers are still using the legacy way to handle ioctl's.
      So, we can't do such change on them, otherwise, they'll break.
      Those are: uvc, et61x251 and sn9c102.
      
      The rationale is that the per-driver version control seems to be
      actively maintained on those.
      
      Yet, I think that the better for them would be to just use the
      default version numbering, instead of doing that by themselves.
      
      While here, removed a few uneeded include linux/version.h
      Acked-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      1990d50b
    • P
      [media] cx231xx: Add support for Hauppauge WinTV USB2-FM · de8ae0d5
      Peter Moon 提交于
      This patch adds support for the "Hauppauge WinTV USB2-FM" Analog TV Stick.
      It includes support for both the PAL and NTSC variants of the device.
      Signed-off-by: NPeter Moon <pomoon@gmail.com>
      Reviewed-by: NDevin Heitmueller <dheitmueller@hauppauge.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      de8ae0d5
  14. 21 5月, 2011 1 次提交
  15. 20 5月, 2011 1 次提交
  16. 22 3月, 2011 4 次提交
  17. 29 12月, 2010 3 次提交
    • M
      [media] rc: Properly name the rc_map struct · b088ba65
      Mauro Carvalho Chehab 提交于
      The struct that describes a rc mapping had an weird and long name.
      We should properly name it, to make easier for developers to work
      with it, and to avoid confusion.
      
      Basically, generated by this script:
      
      for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,ir_scancode_table,rc_map,g <$i >a && mv a $i; done
      for i in `find drivers/staging -type f -name *.[ch]` `find include/media -type f -name *.[ch]` `find drivers/media -type f -name *.[ch]`; do sed s,rc_tab,rc_map,g <$i >a && mv a $i; done
      
      (and manually fixed where needed)
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      b088ba65
    • M
      [media] cx231xx: Properly name rc_map name · 29e3ec19
      Mauro Carvalho Chehab 提交于
      rc_map is confusing, as it may be understood as another thing. Properly
      rename the field to indicate its usage.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      29e3ec19
    • M
      [media] rc: rename the remaining things to rc_core · 6bda9644
      Mauro Carvalho Chehab 提交于
      The Remote Controller subsystem is meant to be used not only by Infra Red
      but also for similar types of Remote Controllers. The core is not specific
      to Infra Red. As such, rename:
      	- ir-core.h to rc-core.h
      	- IR_CORE to RC_CORE
      	- namespace inside rc-core.c/rc-core.h
      
      To be consistent with the other changes.
      
      No functional change on this patch.
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      6bda9644