1. 22 9月, 2014 5 次提交
  2. 05 3月, 2014 1 次提交
  3. 08 11月, 2013 1 次提交
    • M
      [media] tuners: Don't use dynamic static allocation · f1baab87
      Mauro Carvalho Chehab 提交于
      Dynamic static allocation is evil, as Kernel stack is too low, and
      compilation complains about it on some archs:
      	drivers/media/tuners/e4000.c:50:1: warning: 'e4000_wr_regs' uses dynamic stack allocation [enabled by default]
      	drivers/media/tuners/e4000.c:83:1: warning: 'e4000_rd_regs' uses dynamic stack allocation [enabled by default]
      	drivers/media/tuners/fc2580.c:66:1: warning: 'fc2580_wr_regs.constprop.1' uses dynamic stack allocation [enabled by default]
      	drivers/media/tuners/fc2580.c:98:1: warning: 'fc2580_rd_regs.constprop.0' uses dynamic stack allocation [enabled by default]
      	drivers/media/tuners/tda18212.c:57:1: warning: 'tda18212_wr_regs' uses dynamic stack allocation [enabled by default]
      	drivers/media/tuners/tda18212.c:90:1: warning: 'tda18212_rd_regs.constprop.0' uses dynamic stack allocation [enabled by default]
      	drivers/media/tuners/tda18218.c:60:1: warning: 'tda18218_wr_regs' uses dynamic stack allocation [enabled by default]
      	drivers/media/tuners/tda18218.c:92:1: warning: 'tda18218_rd_regs.constprop.0' uses dynamic stack allocation [enabled by default]
      Instead, let's enforce a limit for the buffer. Considering that I2C
      transfers are generally limited, and that devices used on USB has a
      max data length of 64 bytes for	the control URBs.
      So, it seem safe to use 64 bytes as the hard limit for all those devices.
       On most cases, the limit is a way lower than that, but	this limit
      is small enough to not affect the Kernel stack, and it is a no brain
      limit, as using smaller ones would require to either carefully each
      driver or to take a look on each datasheet.
      Signed-off-by: NMauro Carvalho Chehab <m.chehab@samsung.com>
      Reviewed-by: NHans Verkuil <hans.verkuil@cisco.com>
      Reviewed-by: NAntti Palosaari <crope@iki.fi>
      Signed-off-by: NMauro Carvalho Chehab <m.chehab@samsung.com>
      f1baab87
  4. 22 12月, 2012 1 次提交
    • P
      [media] tda18212: tda18218: use 'val' if initialized · ed2e3301
      Paul Bolle 提交于
      Commits e666a44f ("[media] tda18212:
      silence compiler warning") and e0e52d4e
      ("[media] tda18218: silence compiler warning") silenced warnings
      equivalent to these:
          drivers/media/tuners/tda18212.c: In function ‘tda18212_attach’:
          drivers/media/tuners/tda18212.c:299:2: warning: ‘val’ may be used uninitialized in this function [-Wmaybe-uninitialized]
          drivers/media/tuners/tda18218.c: In function ‘tda18218_attach’:
          drivers/media/tuners/tda18218.c:305:2: warning: ‘val’ may be used uninitialized in this function [-Wmaybe-uninitialized]
      But in both cases 'val' will still be used uninitialized if the calls
      of tda18212_rd_reg() or tda18218_rd_reg() fail. Fix this by only
      printing the "chip id" if the calls of those functions were successful.
      This allows to drop the uninitialized_var() stopgap measure.
      Also stop printing the return values of tda18212_rd_reg() or
      tda18218_rd_reg(), as these are not interesting.
      Signed-off-by: NPaul Bolle <pebolle@tiscali.nl>
      Acked-by: NAntti Palosaari <crope@iki.fi>
      Reviewed-by: NAntti Palosaari <crope@iki.fi>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      ed2e3301
  5. 14 8月, 2012 1 次提交
  6. 13 8月, 2012 1 次提交
  7. 12 8月, 2012 1 次提交
  8. 31 12月, 2011 2 次提交
  9. 25 11月, 2011 2 次提交
  10. 07 11月, 2011 1 次提交
  11. 27 8月, 2011 1 次提交
  12. 20 5月, 2011 1 次提交