Merge branch 'v4l_for_linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-2.6
Merge commit. Changes below are compared with the first parent: 6c74700f.
Changes
109 files changed · +13593 −5190
Only the first 600 diff lines are shown. Download the complete patch.
Documentation/DocBook/v4l/lirc_device_interface.xml
View filediff --git a/Documentation/DocBook/v4l/lirc_device_interface.xml b/Documentation/DocBook/v4l/lirc_device_interface.xml
index 0413234..68134c0 100644
--- a/Documentation/DocBook/v4l/lirc_device_interface.xml
+++ b/Documentation/DocBook/v4l/lirc_device_interface.xml
@@ -229,6 +229,22 @@ on working with the default settings initially.</para>
and LIRC_SETUP_END. Drivers can also choose to ignore these ioctls.</para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term>LIRC_SET_WIDEBAND_RECEIVER</term>
+ <listitem>
+ <para>Some receivers are equipped with special wide band receiver which is intended
+ to be used to learn output of existing remote.
+ Calling that ioctl with (1) will enable it, and with (0) disable it.
+ This might be useful of receivers that have otherwise narrow band receiver
+ that prevents them to be used with some remotes.
+ Wide band receiver might also be more precise
+ On the other hand its disadvantage it usually reduced range of reception.
+ Note: wide band receiver might be implictly enabled if you enable
+ carrier reports. In that case it will be disabled as soon as you disable
+ carrier reports. Trying to disable wide band receiver while carrier
+ reports are active will do nothing.</para>
+ </listitem>
+ </varlistentry>
</variablelist>
</section>
Documentation/DocBook/v4l/pixfmt-packed-rgb.xml
View filediff --git a/Documentation/DocBook/v4l/pixfmt-packed-rgb.xml b/Documentation/DocBook/v4l/pixfmt-packed-rgb.xml
index d2dd697..26e8792 100644
--- a/Documentation/DocBook/v4l/pixfmt-packed-rgb.xml
+++ b/Documentation/DocBook/v4l/pixfmt-packed-rgb.xml
@@ -240,6 +240,45 @@ colorspace <constant>V4L2_COLORSPACE_SRGB</constant>.</para>
<entry>r<subscript>1</subscript></entry>
<entry>r<subscript>0</subscript></entry>
</row>
+ <row id="V4L2-PIX-FMT-BGR666">
+ <entry><constant>V4L2_PIX_FMT_BGR666</constant></entry>
+ <entry>'BGRH'</entry>
+ <entry></entry>
+ <entry>b<subscript>5</subscript></entry>
+ <entry>b<subscript>4</subscript></entry>
+ <entry>b<subscript>3</subscript></entry>
+ <entry>b<subscript>2</subscript></entry>
+ <entry>b<subscript>1</subscript></entry>
+ <entry>b<subscript>0</subscript></entry>
+ <entry>g<subscript>5</subscript></entry>
+ <entry>g<subscript>4</subscript></entry>
+ <entry></entry>
+ <entry>g<subscript>3</subscript></entry>
+ <entry>g<subscript>2</subscript></entry>
+ <entry>g<subscript>1</subscript></entry>
+ <entry>g<subscript>0</subscript></entry>
+ <entry>r<subscript>5</subscript></entry>
+ <entry>r<subscript>4</subscript></entry>
+ <entry>r<subscript>3</subscript></entry>
+ <entry>r<subscript>2</subscript></entry>
+ <entry></entry>
+ <entry>r<subscript>1</subscript></entry>
+ <entry>r<subscript>0</subscript></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ </row>
<row id="V4L2-PIX-FMT-BGR24">
<entry><constant>V4L2_PIX_FMT_BGR24</constant></entry>
<entry>'BGR3'</entry>
@@ -700,6 +739,45 @@ defined in error. Drivers may interpret them as in <xref
<entry>b<subscript>1</subscript></entry>
<entry>b<subscript>0</subscript></entry>
</row>
+ <row id="V4L2-PIX-FMT-BGR666">
+ <entry><constant>V4L2_PIX_FMT_BGR666</constant></entry>
+ <entry>'BGRH'</entry>
+ <entry></entry>
+ <entry>b<subscript>5</subscript></entry>
+ <entry>b<subscript>4</subscript></entry>
+ <entry>b<subscript>3</subscript></entry>
+ <entry>b<subscript>2</subscript></entry>
+ <entry>b<subscript>1</subscript></entry>
+ <entry>b<subscript>0</subscript></entry>
+ <entry>g<subscript>5</subscript></entry>
+ <entry>g<subscript>4</subscript></entry>
+ <entry></entry>
+ <entry>g<subscript>3</subscript></entry>
+ <entry>g<subscript>2</subscript></entry>
+ <entry>g<subscript>1</subscript></entry>
+ <entry>g<subscript>0</subscript></entry>
+ <entry>r<subscript>5</subscript></entry>
+ <entry>r<subscript>4</subscript></entry>
+ <entry>r<subscript>3</subscript></entry>
+ <entry>r<subscript>2</subscript></entry>
+ <entry></entry>
+ <entry>r<subscript>1</subscript></entry>
+ <entry>r<subscript>0</subscript></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ <entry></entry>
+ </row>
<row><!-- id="V4L2-PIX-FMT-BGR24" -->
<entry><constant>V4L2_PIX_FMT_BGR24</constant></entry>
<entry>'BGR3'</entry>
Documentation/video4linux/v4l2-controls.txt
View filediff --git a/Documentation/video4linux/v4l2-controls.txt b/Documentation/video4linux/v4l2-controls.txt
new file mode 100644
index 0000000..8773778
--- /dev/null
+++ b/Documentation/video4linux/v4l2-controls.txt
@@ -0,0 +1,648 @@
+Introduction
+============
+
+The V4L2 control API seems simple enough, but quickly becomes very hard to
+implement correctly in drivers. But much of the code needed to handle controls
+is actually not driver specific and can be moved to the V4L core framework.
+
+After all, the only part that a driver developer is interested in is:
+
+1) How do I add a control?
+2) How do I set the control's value? (i.e. s_ctrl)
+
+And occasionally:
+
+3) How do I get the control's value? (i.e. g_volatile_ctrl)
+4) How do I validate the user's proposed control value? (i.e. try_ctrl)
+
+All the rest is something that can be done centrally.
+
+The control framework was created in order to implement all the rules of the
+V4L2 specification with respect to controls in a central place. And to make
+life as easy as possible for the driver developer.
+
+Note that the control framework relies on the presence of a struct v4l2_device
+for V4L2 drivers and struct v4l2_subdev for sub-device drivers.
+
+
+Objects in the framework
+========================
+
+There are two main objects:
+
+The v4l2_ctrl object describes the control properties and keeps track of the
+control's value (both the current value and the proposed new value).
+
+v4l2_ctrl_handler is the object that keeps track of controls. It maintains a
+list of v4l2_ctrl objects that it owns and another list of references to
+controls, possibly to controls owned by other handlers.
+
+
+Basic usage for V4L2 and sub-device drivers
+===========================================
+
+1) Prepare the driver:
+
+1.1) Add the handler to your driver's top-level struct:
+
+ struct foo_dev {
+ ...
+ struct v4l2_ctrl_handler ctrl_handler;
+ ...
+ };
+
+ struct foo_dev *foo;
+
+1.2) Initialize the handler:
+
+ v4l2_ctrl_handler_init(&foo->ctrl_handler, nr_of_controls);
+
+ The second argument is a hint telling the function how many controls this
+ handler is expected to handle. It will allocate a hashtable based on this
+ information. It is a hint only.
+
+1.3) Hook the control handler into the driver:
+
+1.3.1) For V4L2 drivers do this:
+
+ struct foo_dev {
+ ...
+ struct v4l2_device v4l2_dev;
+ ...
+ struct v4l2_ctrl_handler ctrl_handler;
+ ...
+ };
+
+ foo->v4l2_dev.ctrl_handler = &foo->ctrl_handler;
+
+ Where foo->v4l2_dev is of type struct v4l2_device.
+
+ Finally, remove all control functions from your v4l2_ioctl_ops:
+ vidioc_queryctrl, vidioc_querymenu, vidioc_g_ctrl, vidioc_s_ctrl,
+ vidioc_g_ext_ctrls, vidioc_try_ext_ctrls and vidioc_s_ext_ctrls.
+ Those are now no longer needed.
+
+1.3.2) For sub-device drivers do this:
+
+ struct foo_dev {
+ ...
+ struct v4l2_subdev sd;
+ ...
+ struct v4l2_ctrl_handler ctrl_handler;
+ ...
+ };
+
+ foo->sd.ctrl_handler = &foo->ctrl_handler;
+
+ Where foo->sd is of type struct v4l2_subdev.
+
+ And set all core control ops in your struct v4l2_subdev_core_ops to these
+ helpers:
+
+ .queryctrl = v4l2_subdev_queryctrl,
+ .querymenu = v4l2_subdev_querymenu,
+ .g_ctrl = v4l2_subdev_g_ctrl,
+ .s_ctrl = v4l2_subdev_s_ctrl,
+ .g_ext_ctrls = v4l2_subdev_g_ext_ctrls,
+ .try_ext_ctrls = v4l2_subdev_try_ext_ctrls,
+ .s_ext_ctrls = v4l2_subdev_s_ext_ctrls,
+
+ Note: this is a temporary solution only. Once all V4L2 drivers that depend
+ on subdev drivers are converted to the control framework these helpers will
+ no longer be needed.
+
+1.4) Clean up the handler at the end:
+
+ v4l2_ctrl_handler_free(&foo->ctrl_handler);
+
+
+2) Add controls:
+
+You add non-menu controls by calling v4l2_ctrl_new_std:
+
+ struct v4l2_ctrl *v4l2_ctrl_new_std(struct v4l2_ctrl_handler *hdl,
+ const struct v4l2_ctrl_ops *ops,
+ u32 id, s32 min, s32 max, u32 step, s32 def);
+
+Menu controls are added by calling v4l2_ctrl_new_std_menu:
+
+ struct v4l2_ctrl *v4l2_ctrl_new_std_menu(struct v4l2_ctrl_handler *hdl,
+ const struct v4l2_ctrl_ops *ops,
+ u32 id, s32 max, s32 skip_mask, s32 def);
+
+These functions are typically called right after the v4l2_ctrl_handler_init:
+
+ v4l2_ctrl_handler_init(&foo->ctrl_handler, nr_of_controls);
+ v4l2_ctrl_new_std(&foo->ctrl_handler, &foo_ctrl_ops,
+ V4L2_CID_BRIGHTNESS, 0, 255, 1, 128);
+ v4l2_ctrl_new_std(&foo->ctrl_handler, &foo_ctrl_ops,
+ V4L2_CID_CONTRAST, 0, 255, 1, 128);
+ v4l2_ctrl_new_std_menu(&foo->ctrl_handler, &foo_ctrl_ops,
+ V4L2_CID_POWER_LINE_FREQUENCY,
+ V4L2_CID_POWER_LINE_FREQUENCY_60HZ, 0,
+ V4L2_CID_POWER_LINE_FREQUENCY_DISABLED);
+ ...
+ if (foo->ctrl_handler.error) {
+ int err = foo->ctrl_handler.error;
+
+ v4l2_ctrl_handler_free(&foo->ctrl_handler);
+ return err;
+ }
+
+The v4l2_ctrl_new_std function returns the v4l2_ctrl pointer to the new
+control, but if you do not need to access the pointer outside the control ops,
+then there is no need to store it.
+
+The v4l2_ctrl_new_std function will fill in most fields based on the control
+ID except for the min, max, step and default values. These are passed in the
+last four arguments. These values are driver specific while control attributes
+like type, name, flags are all global. The control's current value will be set
+to the default value.
+
+The v4l2_ctrl_new_std_menu function is very similar but it is used for menu
+controls. There is no min argument since that is always 0 for menu controls,
+and instead of a step there is a skip_mask argument: if bit X is 1, then menu
+item X is skipped.
+
+Note that if something fails, the function will return NULL or an error and
+set ctrl_handler->error to the error code. If ctrl_handler->error was already
+set, then it will just return and do nothing. This is also true for
+v4l2_ctrl_handler_init if it cannot allocate the internal data structure.
+
+This makes it easy to init the handler and just add all controls and only check
+the error code at the end. Saves a lot of repetitive error checking.
+
+It is recommended to add controls in ascending control ID order: it will be
+a bit faster that way.
+
+3) Optionally force initial control setup:
+
+ v4l2_ctrl_handler_setup(&foo->ctrl_handler);
+
+This will call s_ctrl for all controls unconditionally. Effectively this
+initializes the hardware to the default control values. It is recommended
+that you do this as this ensures that both the internal data structures and
+the hardware are in sync.
+
+4) Finally: implement the v4l2_ctrl_ops
+
+ static const struct v4l2_ctrl_ops foo_ctrl_ops = {
+ .s_ctrl = foo_s_ctrl,
+ };
+
+Usually all you need is s_ctrl:
+
+ static int foo_s_ctrl(struct v4l2_ctrl *ctrl)
+ {
+ struct foo *state = container_of(ctrl->handler, struct foo, ctrl_handler);
+
+ switch (ctrl->id) {
+ case V4L2_CID_BRIGHTNESS:
+ write_reg(0x123, ctrl->val);
+ break;
+ case V4L2_CID_CONTRAST:
+ write_reg(0x456, ctrl->val);
+ break;
+ }
+ return 0;
+ }
+
+The control ops are called with the v4l2_ctrl pointer as argument.
+The new control value has already been validated, so all you need to do is
+to actually update the hardware registers.
+
+You're done! And this is sufficient for most of the drivers we have. No need
+to do any validation of control values, or implement QUERYCTRL/QUERYMENU. And
+G/S_CTRL as well as G/TRY/S_EXT_CTRLS are automatically supported.
+
+
+==============================================================================
+
+The remainder of this document deals with more advanced topics and scenarios.
+In practice the basic usage as described above is sufficient for most drivers.
+
+===============================================================================
+
+
+Inheriting Controls
+===================
+
+When a sub-device is registered with a V4L2 driver by calling
+v4l2_device_register_subdev() and the ctrl_handler fields of both v4l2_subdev
+and v4l2_device are set, then the controls of the subdev will become
+automatically available in the V4L2 driver as well. If the subdev driver
+contains controls that already exist in the V4L2 driver, then those will be
+skipped (so a V4L2 driver can always override a subdev control).
+
+What happens here is that v4l2_device_register_subdev() calls
+v4l2_ctrl_add_handler() adding the controls of the subdev to the controls
+of v4l2_device.
+
+
+Accessing Control Values
+========================
+
+The v4l2_ctrl struct contains these two unions:
+
+ /* The current control value. */
+ union {
+ s32 val;
+ s64 val64;
+ char *string;
+ } cur;
+
+ /* The new control value. */
+ union {
+ s32 val;
+ s64 val64;
+ char *string;
+ };
+
+Within the control ops you can freely use these. The val and val64 speak for
+themselves. The string pointers point to character buffers of length
+ctrl->maximum + 1, and are always 0-terminated.
+
+In most cases 'cur' contains the current cached control value. When you create
+a new control this value is made identical to the default value. After calling
+v4l2_ctrl_handler_setup() this value is passed to the hardware. It is generally
+a good idea to call this function.
+
+Whenever a new value is set that new value is automatically cached. This means
+that most drivers do not need to implement the g_volatile_ctrl() op. The
+exception is for controls that return a volatile register such as a signal
+strength read-out that changes continuously. In that case you will need to
+implement g_volatile_ctrl like this:
+
+ static int foo_g_volatile_ctrl(struct v4l2_ctrl *ctrl)
+ {
+ switch (ctrl->id) {
+ case V4L2_CID_BRIGHTNESS:
+ ctrl->cur.val = read_reg(0x123);
+ break;
+ }
+ }
+
+The 'new value' union is not used in g_volatile_ctrl. In general controls
+that need to implement g_volatile_ctrl are read-only controls.
+
+To mark a control as volatile you have to set the is_volatile flag:
+
+ ctrl = v4l2_ctrl_new_std(&sd->ctrl_handler, ...);
+ if (ctrl)
+ ctrl->is_volatile = 1;
+
+For try/s_ctrl the new values (i.e. as passed by the user) are filled in and
+you can modify them in try_ctrl or set them in s_ctrl. The 'cur' union
+contains the current value, which you can use (but not change!) as well.
+
+If s_ctrl returns 0 (OK), then the control framework will copy the new final
+values to the 'cur' union.
+
+While in g_volatile/s/try_ctrl you can access the value of all controls owned
+by the same handler since the handler's lock is held. If you need to access
+the value of controls owned by other handlers, then you have to be very careful
+not to introduce deadlocks.
+
+Outside of the control ops you have to go through to helper functions to get
+or set a single control value safely in your driver:
+
+ s32 v4l2_ctrl_g_ctrl(struct v4l2_ctrl *ctrl);
+ int v4l2_ctrl_s_ctrl(struct v4l2_ctrl *ctrl, s32 val);
+
+These functions go through the control framework just as VIDIOC_G/S_CTRL ioctls
+do. Don't use these inside the control ops g_volatile/s/try_ctrl, though, that
+will result in a deadlock since these helpers lock the handler as well.
+
+You can also take the handler lock yourself:
+
+ mutex_lock(&state->ctrl_handler.lock);
+ printk(KERN_INFO "String value is '%s'\n", ctrl1->cur.string);
+ printk(KERN_INFO "Integer value is '%s'\n", ctrl2->cur.val);
+ mutex_unlock(&state->ctrl_handler.lock);
+
+
+Menu Controls
+=============
+
+The v4l2_ctrl struct contains this union:
+
+ union {
+ u32 step;
+ u32 menu_skip_mask;
+ };
+
+For menu controls menu_skip_mask is used. What it does is that it allows you
+to easily exclude certain menu items. This is used in the VIDIOC_QUERYMENU
+implementation where you can return -EINVAL if a certain menu item is not
+present. Note that VIDIOC_QUERYCTRL always returns a step value of 1 for
+menu controls.
+
+A good example is the MPEG Audio Layer II Bitrate menu control where the
+menu is a list of standardized possible bitrates. But in practice hardware
+implementations will only support a subset of those. By setting the skip
+mask you can tell the framework which menu items should be skipped. Setting
+it to 0 means that all menu items are supported.
+
+You set this mask either through the v4l2_ctrl_config struct for a custom
+control, or by calling v4l2_ctrl_new_std_menu().
+
+
+Custom Controls
+===============
+
+Driver specific controls can be created using v4l2_ctrl_new_custom():
+
+ static const struct v4l2_ctrl_config ctrl_filter = {
+ .ops = &ctrl_custom_ops,
+ .id = V4L2_CID_MPEG_CX2341X_VIDEO_SPATIAL_FILTER,
+ .name = "Spatial Filter",
+ .type = V4L2_CTRL_TYPE_INTEGER,
+ .flags = V4L2_CTRL_FLAG_SLIDER,
+ .max = 15,
+ .step = 1,
+ };
+
+ ctrl = v4l2_ctrl_new_custom(&foo->ctrl_handler, &ctrl_filter, NULL);
+
+The last argument is the priv pointer which can be set to driver-specific
+private data.
+
+The v4l2_ctrl_config struct also has fields to set the is_private and is_volatile
+flags.
+
+If the name field is not set, then the framework will assume this is a standard
+control and will fill in the name, type and flags fields accordingly.
+
+
+Active and Grabbed Controls
+===========================
+
+If you get more complex relationships between controls, then you may have to
+activate and deactivate controls. For example, if the Chroma AGC control is
+on, then the Chroma Gain control is inactive. That is, you may set it, but
+the value will not be used by the hardware as long as the automatic gain
+control is on. Typically user interfaces can disable such input fields.
+
+You can set the 'active' status using v4l2_ctrl_activate(). By default all
+controls are active. Note that the framework does not check for this flag.
+It is meant purely for GUIs. The function is typically called from within
+s_ctrl.
+
+The other flag is the 'grabbed' flag. A grabbed control means that you cannot
+change it because it is in use by some resource. Typical examples are MPEG
+bitrate controls that cannot be changed while capturing is in progress.
+
+If a control is set to 'grabbed' using v4l2_ctrl_grab(), then the framework
+will return -EBUSY if an attempt is made to set this control. The
+v4l2_ctrl_grab() function is typically called from the driver when it
+starts or stops streaming.
+
+
+Control Clusters
+================
+
+By default all controls are independent from the others. But in more
+complex scenarios you can get dependencies from one control to another.
+In that case you need to 'cluster' them:
+
+ struct foo {
+ struct v4l2_ctrl_handler ctrl_handler;
+#define AUDIO_CL_VOLUME (0)
+#define AUDIO_CL_MUTE (1)
+ struct v4l2_ctrl *audio_cluster[2];
+ ...
+ };
+
+ state->audio_cluster[AUDIO_CL_VOLUME] =
+ v4l2_ctrl_new_std(&state->ctrl_handler, ...);
+ state->audio_cluster[AUDIO_CL_MUTE] =
+ v4l2_ctrl_new_std(&state->ctrl_handler, ...);
+ v4l2_ctrl_cluster(ARRAY_SIZE(state->audio_cluster), state->audio_cluster);
+
+From now on whenever one or more of the controls belonging to the same
+cluster is set (or 'gotten', or 'tried'), only the control ops of the first
+control ('volume' in this example) is called. You effectively create a new
+composite control. Similar to how a 'struct' works in C.
+
+So when s_ctrl is called with V4L2_CID_AUDIO_VOLUME as argument, you should set
+all two controls belonging to the audio_cluster:
+
+ static int foo_s_ctrl(struct v4l2_ctrl *ctrl)
+ {
+ struct foo *state = container_of(ctrl->handler, struct foo, ctrl_handler);
+
+ switch (ctrl->id) {
+ case V4L2_CID_AUDIO_VOLUME: {
+ struct v4l2_ctrl *mute = ctrl->cluster[AUDIO_CL_MUTE];
+
+ write_reg(0x123, mute->val ? 0 : ctrl->val);
+ break;
+ }
+ case V4L2_CID_CONTRAST:
+ write_reg(0x456, ctrl->val);
+ break;
+ }
+ return 0;
+ }
+
+In the example above the following are equivalent for the VOLUME case:
+
+ ctrl == ctrl->cluster[AUDIO_CL_VOLUME] == state->audio_cluster[AUDIO_CL_VOLUME]
+ ctrl->cluster[AUDIO_CL_MUTE] == state->audio_cluster[AUDIO_CL_MUTE]
+
+Note that controls in a cluster may be NULL. For example, if for some
+reason mute was never added (because the hardware doesn't support that
+particular feature), then mute will be NULL. So in that case we have a
+cluster of 2 controls, of which only 1 is actually instantiated. The
+only restriction is that the first control of the cluster must always be
+present, since that is the 'master' control of the cluster. The master
+control is the one that identifies the cluster and that provides the
+pointer to the v4l2_ctrl_ops struct that is used for that cluster.
+
+Obviously, all controls in the cluster array must be initialized to either
+a valid control or to NULL.
+
+
+VIDIOC_LOG_STATUS Support
+=========================
+
+This ioctl allow you to dump the current status of a driver to the kernel log.
+The v4l2_ctrl_handler_log_status(ctrl_handler, prefix) can be used to dump the
+value of the controls owned by the given handler to the log. You can supply a
This diff is incomplete. Download the complete patch.
MAINTAINERS
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/Kconfig
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/Makefile
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ene_ir.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ene_ir.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/imon.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ir-core-priv.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ir-jvc-decoder.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ir-keytable.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ir-lirc-codec.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ir-nec-decoder.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ir-raw-event.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/ir-sysfs.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/keymaps/Makefile
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/keymaps/rc-empty.c
View before deletionThis diff is incomplete. Download the complete patch.
drivers/media/IR/keymaps/rc-rc5-streamzap.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/keymaps/rc-rc6-mce.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/mceusb.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/rc-map.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/IR/streamzap.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/common/tuners/Kconfig
View fileThis diff is incomplete. Download the complete patch.
drivers/media/dvb/bt8xx/dst.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/dvb/frontends/Kconfig
View fileThis diff is incomplete. Download the complete patch.
drivers/media/dvb/siano/smscoreapi.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/Kconfig
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/Makefile
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cs53l32a.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx2341x.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/Kconfig
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/Makefile
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-av.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-av.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-cards.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-core.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-i2c.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-input.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-ir.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-reg.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-vbi.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885-video.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23885.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx23885/cx23888-ir.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx25840/Makefile
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx25840/cx25840-audio.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx25840/cx25840-core.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx25840/cx25840-core.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/cx25840/cx25840-ir.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/gspca/gspca.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/gspca/sonixj.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/gspca/sq930x.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/gspca/t613.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/gspca/vc032x.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/gspca/zc3xx.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-controls.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-controls.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-driver.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-driver.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-fileops.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-firmware.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-gpio.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-i2c.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-ioctl.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/ivtv/ivtv-streams.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/msp3400-driver.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/msp3400-driver.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/msp3400-kthreads.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/mt9m111.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/mx2_camera.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/pvrusb2/pvrusb2-debugifc.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/s5p-fimc/Makefile
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/s5p-fimc/fimc-core.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/s5p-fimc/fimc-core.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/s5p-fimc/fimc-reg.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/s5p-fimc/regs-fimc.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/saa7115.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/saa717x.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/soc_camera.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/tvp7002.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/usbvideo/usbvideo.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/uvc/uvc_driver.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/uvc/uvc_queue.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/uvc/uvc_video.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/uvc/uvcvideo.h
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/v4l2-common.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/v4l2-ctrls.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/v4l2-dev.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/v4l2-device.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/v4l2-ioctl.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/wm8739.c
View fileThis diff is incomplete. Download the complete patch.
drivers/media/video/wm8775.c
View fileThis diff is incomplete. Download the complete patch.
drivers/staging/lirc/Kconfig
View fileThis diff is incomplete. Download the complete patch.
drivers/staging/lirc/Makefile
View fileThis diff is incomplete. Download the complete patch.
drivers/staging/lirc/lirc_ene0100.c
View before deletionThis diff is incomplete. Download the complete patch.
drivers/staging/lirc/lirc_it87.c
View fileThis diff is incomplete. Download the complete patch.
drivers/staging/lirc/lirc_parallel.c
View fileThis diff is incomplete. Download the complete patch.
drivers/staging/lirc/lirc_streamzap.c
View before deletionThis diff is incomplete. Download the complete patch.
include/linux/videodev2.h
View fileThis diff is incomplete. Download the complete patch.
include/media/cx2341x.h
View fileThis diff is incomplete. Download the complete patch.
include/media/cx25840.h
View fileThis diff is incomplete. Download the complete patch.
include/media/ir-core.h
View fileThis diff is incomplete. Download the complete patch.
include/media/lirc.h
View fileThis diff is incomplete. Download the complete patch.
include/media/rc-map.h
View fileThis diff is incomplete. Download the complete patch.
include/media/v4l2-ctrls.h
View fileThis diff is incomplete. Download the complete patch.
include/media/v4l2-dev.h
View fileThis diff is incomplete. Download the complete patch.
include/media/v4l2-device.h
View fileThis diff is incomplete. Download the complete patch.
include/media/v4l2-subdev.h
View fileThis diff is incomplete. Download the complete patch.