diff options
author | Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se> | 2017-11-15 10:43:58 -0500 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@s-opensource.com> | 2017-11-30 04:44:07 -0500 |
commit | 487cc857851f6ca7850636bd111e7a4bfadab4da (patch) | |
tree | 9b036848e1ec3fc90dda8e945bfc8566d4049acb /MAINTAINERS | |
parent | 3bf393860f6efc41ce268f5c21a457df1e8e6e00 (diff) | |
download | lwn-487cc857851f6ca7850636bd111e7a4bfadab4da.tar.gz lwn-487cc857851f6ca7850636bd111e7a4bfadab4da.zip |
media: v4l: async: use the v4l2_dev from the root notifier when matching sub-devices
When matching and registering a sub-device from a sub-notifier use the
v4l2_device from the root parent notifier. Using the v4l2_dev stored in
the sub-notifier itself is incorrect as it might not be set.
This can be demonstrated by unbinding and rebinding the adv748x driver
and observing that it fails to probe due to the check !v4l2_dev in
v4l2_device_register_subdev().
# echo 4-0070 > /sys/bus/i2c/drivers/adv748x/unbind
# echo 4-0070 > /sys/bus/i2c/drivers/adv748x/bind
adv748x 4-0070: chip found @ 0xe0 revision 2143
adv748x 4-0070: Failed to probe TXA
adv748x: probe of 4-0070 failed with error -22
Looking at the commit which adds sub-notifiers to V4L2 it looks like
this is the intended behavior of the original commit. With this fix the
adv748x can be re-bound and still function properly.
Fixes: 2cab00bb076b9f0e ("media: v4l: async: Allow binding notifiers to sub-devices")
Signed-off-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions