From: Sakari Ailus <sakari.ailus@iki.fi>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org,
Michael Tretter <m.tretter@pengutronix.de>,
Marek Vasut <marex@denx.de>,
Steve Longerbeam <slongerbeam@gmail.com>,
laurent.pinchart@ideasonboard.com
Subject: Re: [PATCH 0/3] Explicit CSI-2 LP-11 / LP-111 support
Date: Wed, 23 Jun 2021 21:18:53 +0300 [thread overview]
Message-ID: <20210623181853.GD3@valkosipuli.retiisi.eu> (raw)
In-Reply-To: <20210623181302.14660-1-sakari.ailus@linux.intel.com>
On Wed, Jun 23, 2021 at 09:12:59PM +0300, Sakari Ailus wrote:
> Hi all,
>
> Some receiver devices requires explicit support for transitioning
> transmitters to LP-11 or LP-111 state before starting streaming. As
> there's currently a single operation (s_stream()) callback to do that,
> there's no way for the receiver driver to differentiate between the two
> things.
>
> This set adds two more callbacks, pre_streamon and post_streamon, to do
> exactly that. The usage on CSI-2 is to set the transmitter state to LP-11
> or LP-111 (depending on the PHY) and thus allow reliable receiver
> initialisation.
>
> The set also adds support for this in the CCS driver.
I forgot to mention the set goes on top of my earlier patches I sent
recently. This is all here:
https://git.linuxtv.org/sailus/media_tree.git/ camera-stuff
--
Sakari Ailus
prev parent reply other threads:[~2021-06-23 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 18:12 [PATCH 0/3] Explicit CSI-2 LP-11 / LP-111 support Sakari Ailus
2021-06-23 18:13 ` [PATCH 1/3] Documentation: v4l: Rework LP-11 documentation, add callbacks Sakari Ailus
2021-06-23 18:13 ` [PATCH 2/3] v4l: subdev: Add pre_streamon and post_streamoff callbacks Sakari Ailus
2021-06-23 18:13 ` [PATCH 3/3] ccs: Implement support for manual LP control Sakari Ailus
2021-07-08 13:44 ` [PATCH v2 " Sakari Ailus
2021-06-23 18:18 ` Sakari Ailus [this message]
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=20210623181853.GD3@valkosipuli.retiisi.eu \
--to=sakari.ailus@iki.fi \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=m.tretter@pengutronix.de \
--cc=marex@denx.de \
--cc=sakari.ailus@linux.intel.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 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.