From: Jammy Huang <jammy_huang@aspeedtech.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] media: aspeed: fix mode-detect always timeout at 2nd run
Date: Tue, 2 Nov 2021 16:40:43 +0800 [thread overview]
Message-ID: <106a61c6-ac89-b2a4-acb0-1baa315f5829@aspeedtech.com> (raw)
In-Reply-To: <15c44f9a-20af-8059-1694-601821e17413@molgen.mpg.de>
Dear Paul,
I will modify my commit message. Thanks for your review and suggestion.
On 2021/11/2 ?? 04:07, Paul Menzel wrote:
> Dear Jammy,
>
>
> On 02.11.21 08:13, Jammy Huang wrote:
>> aspeed_video_get_resolution() will try to do res-detect again if the
>> timing got in last try is invalid. But it will always timeout because
> The verb *time out* is spelled with a space.
>
>> VE_SEQ_CTRL_TRIG_MODE_DET only cleared after 1st mode-detect.
> is only cleared?
>
>> To fix the problem, just clear VE_SEQ_CTRL_TRIG_MODE_DET before set in
> before setting it?
>
>> aspeed_video_enable_mode_detect().
>>
>> Signed-off-by: Jammy Huang<jammy_huang@aspeedtech.com>
>> ---
>> drivers/media/platform/aspeed-video.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/media/platform/aspeed-video.c b/drivers/media/platform/aspeed-video.c
>> index cd2b71c81e31..b470f4b68aa0 100644
>> --- a/drivers/media/platform/aspeed-video.c
>> +++ b/drivers/media/platform/aspeed-video.c
>> @@ -611,6 +611,10 @@ static void aspeed_video_enable_mode_detect(struct aspeed_video *video)
>> aspeed_video_update(video, VE_INTERRUPT_CTRL, 0,
>> VE_INTERRUPT_MODE_DETECT);
>>
>> + /* Disable mode detect in order to re-trigger */
>> + aspeed_video_update(video, VE_SEQ_CTRL,
>> + VE_SEQ_CTRL_TRIG_MODE_DET, 0);
>> +
>> /* Trigger mode detect */
>> aspeed_video_update(video, VE_SEQ_CTRL, 0, VE_SEQ_CTRL_TRIG_MODE_DET);
>> }
>> @@ -930,10 +934,6 @@ static void aspeed_video_get_resolution(struct aspeed_video *video)
>> return;
>> }
>>
>> - /* Disable mode detect in order to re-trigger */
>> - aspeed_video_update(video, VE_SEQ_CTRL,
>> - VE_SEQ_CTRL_TRIG_MODE_DET, 0);
>> -
>> aspeed_video_check_and_set_polarity(video);
>>
>> aspeed_video_enable_mode_detect(video);
>>
> Acked-by: Paul Menzel<pmenzel@molgen.mpg.de>
>
>
> Kind regards,
>
> Paul
--
Best Regards
Jammy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linux-aspeed/attachments/20211102/06a4e5c4/attachment-0001.htm>
prev parent reply other threads:[~2021-11-02 8:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 7:13 [PATCH] media: aspeed: fix mode-detect always timeout at 2nd run Jammy Huang
2021-11-02 8:07 ` Paul Menzel
2021-11-02 8:40 ` Jammy Huang [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=106a61c6-ac89-b2a4-acb0-1baa315f5829@aspeedtech.com \
--to=jammy_huang@aspeedtech.com \
--cc=linux-aspeed@lists.ozlabs.org \
/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