From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jammy Huang <jammy_huang@aspeedtech.com>
Cc: eajames@linux.ibm.com, mchehab@kernel.org, joel@jms.id.au,
andrew@aj.id.au, linux-media@vger.kernel.org,
openbmc@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: aspeed: Fix incorrect resolution detected
Date: Tue, 9 Nov 2021 12:22:37 +0100 [thread overview]
Message-ID: <ac30786b-dbeb-db77-4fd8-6fe1efbdb929@molgen.mpg.de> (raw)
In-Reply-To: <20211109095453.12363-1-jammy_huang@aspeedtech.com>
Dear Jammy,
Am 09.11.21 um 10:54 schrieb Jammy Huang:
> During the process of os-installation, detected resolution's height
> could be less than the correct one.
Can you please elaborate? What OS? What resolution was and what
resolution should have been detected?
> Increase min-required-count of stable signal to fix the problem.
So you do two changes in the patch? First use the bitfield access
macros, and then change VE_MODE_DT_HOR_STABLE and VE_MODE_DT_VER_STABLE
from 6 to 10? Is that the amount of iterations? Why 10 and not 20?
How much time do four iterations add?
Sorry for my ignorance, but if you could make it two patches, that’d be
great.
> Fixes: d2b4387f3bdf ("media: platform: Add Aspeed Video Engine driver")
> Signed-off-by: Jammy Huang <jammy_huang@aspeedtech.com>
> ---
> drivers/media/platform/aspeed-video.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/aspeed-video.c b/drivers/media/platform/aspeed-video.c
> index 5da52646b298..625a77ddb479 100644
> --- a/drivers/media/platform/aspeed-video.c
> +++ b/drivers/media/platform/aspeed-video.c
> @@ -196,6 +196,12 @@
> #define VE_INTERRUPT_VSYNC_DESC BIT(11)
>
> #define VE_MODE_DETECT 0x30c
> +#define VE_MODE_DT_HOR_TOLER GENMASK(31, 28)
> +#define VE_MODE_DT_VER_TOLER GENMASK(27, 24)
> +#define VE_MODE_DT_HOR_STABLE GENMASK(23, 20)
> +#define VE_MODE_DT_VER_STABLE GENMASK(19, 16)
> +#define VE_MODE_DT_EDG_THROD GENMASK(15, 8)
> +
> #define VE_MEM_RESTRICT_START 0x310
> #define VE_MEM_RESTRICT_END 0x314
>
> @@ -1199,7 +1205,12 @@ static void aspeed_video_init_regs(struct aspeed_video *video)
> aspeed_video_write(video, VE_SCALING_FILTER3, 0x00200000);
>
> /* Set mode detection defaults */
> - aspeed_video_write(video, VE_MODE_DETECT, 0x22666500);
> + aspeed_video_write(video, VE_MODE_DETECT,
> + FIELD_PREP(VE_MODE_DT_HOR_TOLER, 2) |
> + FIELD_PREP(VE_MODE_DT_VER_TOLER, 2) |
> + FIELD_PREP(VE_MODE_DT_HOR_STABLE, 10) |
> + FIELD_PREP(VE_MODE_DT_VER_STABLE, 10) |
> + FIELD_PREP(VE_MODE_DT_EDG_THROD, 0x65));
>
> aspeed_video_write(video, VE_BCD_CTRL, 0);
> }
>
Kind regards,
Paul
next prev parent reply other threads:[~2021-11-09 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 9:54 Jammy Huang
2021-11-09 11:22 ` Paul Menzel [this message]
2021-11-10 3:33 ` Jammy Huang
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=ac30786b-dbeb-db77-4fd8-6fe1efbdb929@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=andrew@aj.id.au \
--cc=eajames@linux.ibm.com \
--cc=jammy_huang@aspeedtech.com \
--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®