public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steve Longerbeam <slongerbeam@gmail.com>
To: Ian Arkver <ian.arkver.dev@gmail.com>, linux-media@vger.kernel.org
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: docs-rst: Clarify duration of LP-11 mode
Date: Mon, 12 Aug 2019 14:39:45 -0700	[thread overview]
Message-ID: <2a84063e-b66f-bef2-1277-3514566aa236@gmail.com> (raw)
In-Reply-To: <3f31cde6-8faf-f9a0-626e-dc995260a640@gmail.com>

Hi Ian,

On 8/12/19 1:53 AM, Ian Arkver wrote:
> Hi Steve,
>
> On 11/08/2019 18:36, Steve Longerbeam wrote:
>> Add a sentence that makes it more clear when the CSI-2 transmitter
>> must, if possible, exit LP-11 mode. That is, maintain LP-11 mode
>> until stream on, at which point the transmitter activates the clock
>> lane and transition to HS mode.
>>
>> Signed-off-by: Steve Longerbeam <slongerbeam@gmail.com>
>> ---
>>   Documentation/media/kapi/csi2.rst | 10 +++++++---
>>   1 file changed, 7 insertions(+), 3 deletions(-)
>>
>> diff --git a/Documentation/media/kapi/csi2.rst 
>> b/Documentation/media/kapi/csi2.rst
>> index a7e75e2eba85..6cd1d4b0df17 100644
>> --- a/Documentation/media/kapi/csi2.rst
>> +++ b/Documentation/media/kapi/csi2.rst
>> @@ -49,9 +49,13 @@ where
>>     The transmitter drivers must, if possible, configure the CSI-2
>>   transmitter to *LP-11 mode* whenever the transmitter is powered on but
>> -not active. Some transmitters do this automatically but some have to
>> -be explicitly programmed to do so, and some are unable to do so
>> -altogether due to hardware constraints.
>> +not active, and maintain *LP-11 mode* until stream on. Only until
>
> s/until/at/ perhaps?

Sure, that's a bit better language.

Steve

>
> Regards,
> Ian
>> +stream on should the transmitter activate the clock on the clock lane
>> +and transition to *HS mode*.
>> +
>> +Some transmitters do this automatically but some have to be explicitly
>> +programmed to do so, and some are unable to do so altogether due to
>> +hardware constraints.
>>     Stopping the transmitter
>>   ^^^^^^^^^^^^^^^^^^^^^^^^
>>


      reply	other threads:[~2019-08-12 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-11 17:36 [PATCH] media: docs-rst: Clarify duration of LP-11 mode Steve Longerbeam
2019-08-12  8:53 ` Ian Arkver
2019-08-12 21:39   ` Steve Longerbeam [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=2a84063e-b66f-bef2-1277-3514566aa236@gmail.com \
    --to=slongerbeam@gmail.com \
    --cc=ian.arkver.dev@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox