From: Philipp Zabel <p.zabel@pengutronix.de>
To: linux-media@vger.kernel.org
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Mats Randgaard <matrandg@cisco.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
kernel@pengutronix.de
Subject: [PATCH v4 0/3] Add g_csi_active_lanes for dynamic active lanes
Date: Tue, 24 Sep 2019 13:49:52 +0200 [thread overview]
Message-ID: <20190924114955.13132-1-p.zabel@pengutronix.de> (raw)
Some MIPI CSI-2 transmitters, such as TC358743 can dynamically change
the number of active data lanes depending on the bandwidth needs for the
selected video format. This patchset adds a subdevice video operation
g_csi_active_lanes() to let the MIPI CSI-2 receiver query the number of
active lanes and change its configuration accordingly.
Changes since v3 [1]:
- Add g_csi_active_lanes() subdevice video operation,
implement it in tc358743, and use it in imx6-mipi-csi2.
[1] https://patchwork.linuxtv.org/patch/53331/
regards
Philipp
Philipp Zabel (3):
media: v4l2-subdev: add g_csi_active_lanes() op
media: tc358743: fix connected/active CSI-2 lane reporting
media: imx: ask source subdevice for number of active data lanes
drivers/media/i2c/tc358743.c | 44 ++++++++++++++++------
drivers/staging/media/imx/imx6-mipi-csi2.c | 8 ++--
include/media/v4l2-subdev.h | 3 ++
3 files changed, 39 insertions(+), 16 deletions(-)
--
2.20.1
next reply other threads:[~2019-09-24 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 11:49 Philipp Zabel [this message]
2019-09-24 11:49 ` [PATCH v4 1/3] media: v4l2-subdev: add g_csi_active_lanes() op Philipp Zabel
2019-09-25 13:41 ` Laurent Pinchart
2019-09-25 14:51 ` Jacopo Mondi
2019-09-25 15:08 ` Philipp Zabel
2019-09-25 14:57 ` Philipp Zabel
2019-09-24 11:49 ` [PATCH v4 2/3] media: tc358743: fix connected/active CSI-2 lane reporting Philipp Zabel
2019-09-24 11:49 ` [PATCH v4 3/3] media: imx: ask source subdevice for number of active data lanes Philipp Zabel
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=20190924114955.13132-1-p.zabel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=hverkuil@xs4all.nl \
--cc=kernel@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=matrandg@cisco.com \
--cc=slongerbeam@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).