From: Wentong Wu <wentong.wu@intel.com>
To: sakari.ailus@linux.intel.com, linux-media@vger.kernel.org
Cc: hao.yao@intel.com, Wentong Wu <wentong.wu@intel.com>
Subject: [PATCH 0/3] Fix privacy issue for MEI CSI
Date: Mon, 3 Jun 2024 16:26:11 +0800 [thread overview]
Message-ID: <20240603082614.1567712-1-wentong.wu@intel.com> (raw)
Currently if starting stream goes with privacy mode on, the whole
pipeline will fail because MEI CSI counts privacy mode on as error.
In face, the ongoing MEI command is well executed by firmware as
well even if privacy mode is turned on. The status (-1) of command
response is just to indicate current privacy on status instead of
failed to execute command by firmware. This patch set changes the
behavior to notify privacy mode on via v4l2 privacy control instead
of fail the ongoing MEI command.
This patch set adds one dedicated lock for v4l2 control handler to
avoid dead locking issue as well. And the useless privacy status in
struct mei_csi is removed to make code clean.
Wentong Wu (3):
media: ivsc: csi: don't count privacy on as error
media: ivsc: csi: add separate lock for v4l2 control handler
media: ivsc: csi: remove privacy status in struct mei_csi
drivers/media/pci/intel/ivsc/mei_csi.c | 23 ++++++++++++++---------
1 file changed, 14 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2024-06-03 8:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 8:26 Wentong Wu [this message]
2024-06-03 8:26 ` [PATCH 1/3] media: ivsc: csi: don't count privacy on as error Wentong Wu
2024-06-07 12:45 ` Sakari Ailus
2024-06-07 12:55 ` Wu, Wentong
2024-06-03 8:26 ` [PATCH 2/3] media: ivsc: csi: add separate lock for v4l2 control handler Wentong Wu
2024-06-07 12:41 ` Sakari Ailus
2024-06-07 12:53 ` Wu, Wentong
2024-06-03 8:26 ` [PATCH 3/3] media: ivsc: csi: remove privacy status in struct mei_csi Wentong Wu
2024-06-07 12:45 ` Sakari Ailus
2024-06-07 12:54 ` Wu, Wentong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240603082614.1567712-1-wentong.wu@intel.com \
--to=wentong.wu@intel.com \
--cc=hao.yao@intel.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.