From: Jammy Huang <jammy_huang@aspeedtech.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
"eajames@linux.ibm.com" <eajames@linux.ibm.com>,
"mchehab@kernel.org" <mchehab@kernel.org>,
"joel@jms.id.au" <joel@jms.id.au>,
"andrew@aj.id.au" <andrew@aj.id.au>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-aspeed@lists.ozlabs.org" <linux-aspeed@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 0/2] Fix incorrect resolution detected
Date: Wed, 26 Jan 2022 09:41:27 +0800 [thread overview]
Message-ID: <8681fe29-69c2-f701-aff4-c27cef2d32d7@aspeedtech.com> (raw)
In-Reply-To: <c3202b1f-ff8f-8108-e8a3-8710c8c74d10@xs4all.nl>
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
prev parent reply other threads:[~2022-01-26 1:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 10:07 Jammy Huang
2022-01-18 10:07 ` [PATCH v4 1/2] media: aspeed: Add macro for the fields of the mode-detect registers Jammy Huang
2022-01-18 10:07 ` [PATCH v4 2/2] media: aspeed: Fix unstable timing detection Jammy Huang
2022-01-25 10:43 ` [PATCH v4 0/2] Fix incorrect resolution detected Hans Verkuil
2022-01-26 1:41 ` 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=8681fe29-69c2-f701-aff4-c27cef2d32d7@aspeedtech.com \
--to=jammy_huang@aspeedtech.com \
--cc=andrew@aj.id.au \
--cc=eajames@linux.ibm.com \
--cc=hverkuil@xs4all.nl \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=openbmc@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
all inboxes | Powered by JetHome®