1. 18 8月, 2013 5 次提交
  2. 01 8月, 2013 2 次提交
    • S
      [media] media: lirc: Allow lirc dev to talk to rc device · ca7a722d
      Srinivas Kandagatla 提交于
      The use case is simple, if any rc device has allowed protocols =
      RC_TYPE_LIRC and map_name = RC_MAP_LIRC set, the driver open will be never
      called. The reason for this is, all of the key maps except lirc have some
      KEYS in there map, so during rc_register_device process these keys are
      matched against the input drivers and open is performed, so for the case
      of RC_MAP_EMPTY, a vt/keyboard is matched and the driver open is
      performed.
      In case of lirc, there is no match and result is that there is no open
      performed, however the lirc-dev will go ahead and create a /dev/lirc0
      node. Now when lircd/mode2 opens this device, no data is available
      because the driver was never opened.
      Other case pointed by Sean Young, As rc device gets opened via the
      input interface. If the input device is never opened (e.g. embedded with
      no console) then the rc open is never called and lirc will not work
      either. So that's another case.
      lirc_dev seems to have no link with actual rc device w.r.t open/close.
      This patch adds rc_dev pointer to lirc_driver structure for cases like
      this, so that it can do the open/close of the real driver in accordance
      to lircd/mode2 open/close.
      Without this patch its impossible to open a rc device which has
      RC_TYPE_LIRC ad RC_MAP_LIRC set.
      Signed-off-by: NSrinivas Kandagatla <srinivas.kandagatla@st.com>
      Signed-off-by: NMauro Carvalho Chehab <m.chehab@samsung.com>
      ca7a722d
    • S
      [media] media: rc: Add rc_open/close and use count to rc_dev · 8b2ff320
      Srinivas Kandagatla 提交于
      This patch adds user count to rc_dev structure, the reason to add this
      new member is to allow other code like lirc to open rc device directly.
      In the existing code, rc device is only opened by input subsystem which
      works ok if we have any input drivers to match. But in case like lirc
      where there will be no input driver, rc device will be never opened.
      Having this user count variable will be usefull to allow rc device to be
      opened from code other than rc-main.
      This patch also adds rc_open and rc_close functions for other drivers
      like lirc to open and close rc devices. This functions safely increment
      and decrement the user count. Other driver wanting to open rc device
      should call rc_open and rc_close, rather than directly modifying the
      rc_dev structure.
      Signed-off-by: NSrinivas Kandagatla <srinivas.kandagatla@st.com>
      Signed-off-by: NMauro Carvalho Chehab <m.chehab@samsung.com>
      8b2ff320
  3. 31 7月, 2013 4 次提交
  4. 27 7月, 2013 3 次提交
  5. 26 7月, 2013 1 次提交
    • P
      [media] mem2mem: add support for hardware buffered queue · 33bdd5a8
      Philipp Zabel 提交于
      On mem2mem decoders with a hardware bitstream ringbuffer, to drain the
      buffer at the end of the stream, remaining frames might need to be decoded
      from the bitstream buffer without additional input buffers being provided.
      To achieve this, allow a queue to be marked as buffered by the driver, and
      allow scheduling of device_runs when buffered ready queues are empty.
      This also allows a driver to copy input buffers into their bitstream
      ringbuffer and immediately mark them as done to be dequeued.
      The motivation for this patch is hardware assisted h.264 reordering support
      in the coda driver. For high profile streams, the coda can hold back
      out-of-order frames, causing a few mem2mem device runs in the beginning, that
      don't produce any decompressed buffer at the v4l2 capture side. At the same
      time, the last few frames can be decoded from the bitstream with mem2mem device
      runs that don't need a new input buffer at the v4l2 output side. The decoder
      command ioctl can be used to put the decoder into the ringbuffer draining
      end-of-stream mode.
      Signed-off-by: NPhilipp Zabel <p.zabel@pengutronix.de>
      Acked-by: NSylwester Nawrocki <s.nawrocki@samsung.com>
      Signed-off-by: NKamil Debski <k.debski@samsung.com>
      Signed-off-by: NMauro Carvalho Chehab <m.chehab@samsung.com>
      33bdd5a8
  6. 29 6月, 2013 2 次提交
  7. 22 6月, 2013 8 次提交
  8. 21 6月, 2013 6 次提交
  9. 19 6月, 2013 1 次提交
  10. 17 6月, 2013 2 次提交
    • H
      [media] v4l2: remove deprecated current_norm support completely · ca371575
      Hans Verkuil 提交于
      The use of current_norm to keep track of the current standard has been
      deprecated for quite some time. Now that all drivers that were using it
      have been converted to use g_std we can drop it from the core.
      It was a bad idea to introduce this at the time: since it is a per-device
      node field it didn't work for drivers that create multiple nodes, all sharing
      the same tuner (e.g. video and vbi nodes, or a raw video node and a compressed
      video node). In addition it was very surprising behavior that g_std was
      implemented in the core. Often drivers implemented both g_std and current_norm,
      because they didn't understand how it should be used.
      Since the benefits were very limited (if they were there at all), it is better
      to just drop it and require that drivers just implement g_std.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      ca371575
    • H
      [media] tveeprom: remove v4l2-chip-ident.h include · 33001010
      Hans Verkuil 提交于
      Replace the V4L2_IDENT_* usage with tveeprom-specific defines. This header
      is deprecated, so those defines shouldn't be used anymore.
      The em28xx driver is the only one that uses the tveeprom audio_processor
      field, so that has been updated to use the new tveeprom AUDPROC define.
      Signed-off-by: NHans Verkuil <hans.verkuil@cisco.com>
      Signed-off-by: NMauro Carvalho Chehab <mchehab@redhat.com>
      33001010
  11. 13 6月, 2013 4 次提交
  12. 09 6月, 2013 1 次提交
  13. 04 6月, 2013 1 次提交