Patch "[media] media: am437x-vpfe: Requested frame size and fmt overwritten by current sensor setting" has been added to the 4.2-stable tree
Subsystems (2)
This is a note to let you know that I've just added the patch titled
[media] media: am437x-vpfe: Requested frame size and fmt overwritten by current sensor setting
to the 4.2-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
media-am437x-vpfe-requested-frame-size-and-fmt-overwritten-by-current-sensor-setting.patch
and it can be found in the queue-4.2 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.
Quoted 1 line
From
f47c9045643f91e76d8a9030828b9fe1cf4a6bcfMon Sep 17 00:00:00 2001
From: Benoit Parrot <[email protected]>
Date: Mon, 29 Jun 2015 18:19:06 -0300
Subject: [media] media: am437x-vpfe: Requested frame size and fmt overwritten by current sensor setting
From: Benoit Parrot <[email protected]>
commit f47c9045643f91e76d8a9030828b9fe1cf4a6bcf upstream.
Upon a S_FMT the input/requested frame size and pixel format is overwritten by the current sub-device settings.
Fix this so application can actually set the frame size and format.
--- drivers/media/platform/am437x/am437x-vpfe.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/platform/am437x/am437x-vpfe.c +1 -1
@@ -1565,7 +1565,7 @@ static int vpfe_s_fmt(struct file *file,return -EBUSY ; } - ret =vpfe_try_fmt (file, priv, fmt); + ret =vpfe_try_fmt (file, priv, &format);if (ret)return ret;
Patches currently in stable-queue which might be from [email protected] are
queue-4.2/media-am437x-vpfe-fix-a-race-condition-during-release.patch queue-4.2/media-am437x-vpfe-requested-frame-size-and-fmt-overwritten-by-current-sensor-setting.patch