[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8681fe29-69c2-f701-aff4-c27cef2d32d7@aspeedtech.com>
Date: Wed, 26 Jan 2022 09:41:27 +0800
From: Jammy Huang <jammy_huang@...eedtech.com>
To: Hans Verkuil <hverkuil@...all.nl>,
"eajames@...ux.ibm.com" <eajames@...ux.ibm.com>,
"mchehab@...nel.org" <mchehab@...nel.org>,
"joel@....id.au" <joel@....id.au>,
"andrew@...id.au" <andrew@...id.au>,
"linux-media@...r.kernel.org" <linux-media@...r.kernel.org>,
"openbmc@...ts.ozlabs.org" <openbmc@...ts.ozlabs.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-aspeed@...ts.ozlabs.org" <linux-aspeed@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 0/2] Fix incorrect resolution detected
On 2022/1/25 下午 06:43, Hans Verkuil wrote:
> Hi Jammy,
>
> On 18/01/2022 11:07, Jammy Huang wrote:
>> This series fixes incorrect resolution detected.
>> We found this problem happened occasionally in the switch between bios
>> and bootloader.
> Can you rebase this on top of:
>
> https://git.linuxtv.org/hverkuil/media_tree.git/log/?h=for-v5.18f
>
> This series doesn't apply cleanly.
OK, I will update patch based on this code base.
Regards,
Jammy
>
> Regards,
>
> Hans
>
>> Changes in v4:
>> - Correct the subject of patch
>>
>> Changes in v3:
>> - In v2, we tried to increase the min-required-count of stable signal
>> to avoid incorrect transient state in timing detection. But it is
>> not working for all conditions.
>> Thus, we go another way in v3. Use regs, which can represent the
>> signal status, to decide if we needs to do detection again.
>>
>> Changes in v2:
>> - Separate the patch into two patches
>>
>> Jammy Huang (2):
>> media: aspeed: Add macro for the fields of the mode-detect registers
>> media: aspeed: Fix unstable timing detection
>>
>> drivers/media/platform/aspeed-video.c | 25 ++++++++++++++++++++++++-
>> 1 file changed, 24 insertions(+), 1 deletion(-)
>>
--
Best Regards
Jammy
Powered by blists - more mailing lists