All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Eddie James <eajames@linux.vnet.ibm.com>,
	Eddie James <eajames@linux.ibm.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Joel Stanley <joel@jms.id.au>, Andrew Jeffery <andrew@aj.id.au>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Ryan Chen <ryan_chen@aspeedtech.com>
Cc: linux-aspeed@lists.ozlabs.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v2 11/11] media: aspeed: add a workaround to fix a silicon bug
Date: Wed, 29 May 2019 10:29:19 -0700	[thread overview]
Message-ID: <cd1814db-4892-bba0-027a-9f51cd49b9b5@linux.intel.com> (raw)
In-Reply-To: <03a3cf74-3fd3-982e-ec37-014ed4a13b47@linux.vnet.ibm.com>

On 5/29/2019 7:07 AM, Eddie James wrote:
> 
> On 5/24/19 6:17 PM, Jae Hyun Yoo wrote:
>> AST2500 silicon revision A1 and A2 have a silicon bug which causes
>> extremly long capturing time on specific resolutions (1680 width).
>> To fix the bug, this commit adjusts the capturing window register
>> setting to 1728 if detected width is 1680. The compression window
>> register setting will be kept as the original width so output
>> result will be the same.
> 
> 
> This is a bit curious, why 1728 in particular? And what is the behavior 
> of the VE when the capture window is larger than the actual source 
> resolution?

For an example, if resolution is 1680x1050, capturing operation takes
very long time because VE has the silicon bug. So this patch adjusts
the 'Capture Window' register slightly larger than 1680 to avoid the
issue. As a result, source buffer will copy 1728x1050 frames from the
original screen buffer but the image is still has valid information.
As the next step in compression phase, it will set the 'Compression
Window' register as '1680x1050' so it will compress using the original
image resolution which is a cropped image from the '1728x1050' source
buffer.

You can compare results using these shell commands in Ubuntu GUI
desktop.

$ xrandr --newmode "1680x1050_60.00"  146.25  1680 1784 1960 1240  1050 
1053 1059 1089 -hsync +vsync
$ xrandr --addmode VGA-1 1680x1050_60.00
$ xrandr --output VGA-1 --mode 1680x1050_60.00

I'm also curious about why that is 1728. Actually, this workaround was
provided from the chip vendor, Aspeed, and they use this in their SDK
code too. Let's check it to Ryan.


Hi Ryan,

Can you please explain why that is 1728 in particular.

Thanks,
Jae

> 
> Thanks,
> 
> Eddie
> 
> 
>>
>> Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
>> ---
>> v1 -> v2:
>>   New.
>>
>>   drivers/media/platform/aspeed-video.c | 26 +++++++++++++++++++-------
>>   1 file changed, 19 insertions(+), 7 deletions(-)
>>
>> diff --git a/drivers/media/platform/aspeed-video.c 
>> b/drivers/media/platform/aspeed-video.c
>> index b05b073b63bc..f93989f532d6 100644
>> --- a/drivers/media/platform/aspeed-video.c
>> +++ b/drivers/media/platform/aspeed-video.c
>> @@ -824,8 +824,27 @@ static void aspeed_video_set_resolution(struct 
>> aspeed_video *video)
>>       struct v4l2_bt_timings *act = &video->active_timings;
>>       unsigned int size = act->width * act->height;
>> +    /* Set capture/compression frame sizes */
>>       aspeed_video_calc_compressed_size(video, size);
>> +    if (video->active_timings.width == 1680) {
>> +        /*
>> +         * This is a workaround to fix a silicon bug on A1 and A2
>> +         * revisions. Since it doesn't break capturing operation on A0
>> +         * revision, use it for all revisions without checking the
>> +         * revision ID.
>> +         */
>> +        aspeed_video_write(video, VE_CAP_WINDOW,
>> +                   1728 << 16 | act->height);
>> +        size += (1728 - 1680) * video->active_timings.height;
>> +    } else {
>> +        aspeed_video_write(video, VE_CAP_WINDOW,
>> +                   act->width << 16 | act->height);
>> +    }
>> +    aspeed_video_write(video, VE_COMP_WINDOW,
>> +               act->width << 16 | act->height);
>> +    aspeed_video_write(video, VE_SRC_SCANLINE_OFFSET, act->width * 4);
>> +
>>       /* Don't use direct mode below 1024 x 768 (irqs don't fire) */
>>       if (size < DIRECT_FETCH_THRESHOLD) {
>>           aspeed_video_write(video, VE_TGS_0,
>> @@ -842,13 +861,6 @@ static void aspeed_video_set_resolution(struct 
>> aspeed_video *video)
>>           aspeed_video_update(video, VE_CTRL, 0, VE_CTRL_DIRECT_FETCH);
>>       }
>> -    /* Set capture/compression frame sizes */
>> -    aspeed_video_write(video, VE_CAP_WINDOW,
>> -               act->width << 16 | act->height);
>> -    aspeed_video_write(video, VE_COMP_WINDOW,
>> -               act->width << 16 | act->height);
>> -    aspeed_video_write(video, VE_SRC_SCANLINE_OFFSET, act->width * 4);
>> -
>>       size *= 4;
>>       if (size == video->srcs[0].size / 2) {
> 
> 

  reply	other threads:[~2019-05-29 17:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 23:17 [PATCH v2 00/11] Improve stability and add bug fixes of Aspeed video engine driver Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 01/11] media: aspeed: fix a kernel warning on clk control Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 02/11] media: aspeed: refine clock control logic Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 03/11] media: aspeed: change irq to threaded irq Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 04/11] media: aspeed: remove IRQF_SHARED flag Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 05/11] media: aspeed: reduce noisy log printing outs Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 06/11] media: aspeed: remove checking of VE_INTERRUPT_CAPTURE_COMPLETE Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 07/11] media: aspeed: refine interrupt handling logic Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 08/11] media: aspeed: remove source buffer allocation before mode detection Jae Hyun Yoo
2019-05-29 16:07   ` Eddie James
2019-05-24 23:17 ` [PATCH v2 09/11] media: aspeed: use different delays for triggering VE H/W reset Jae Hyun Yoo
2019-05-29 16:07   ` Eddie James
2019-05-24 23:17 ` [PATCH v2 10/11] media: aspeed: fix an incorrect timeout checking in mode detection Jae Hyun Yoo
2019-05-29 14:03   ` Eddie James
2019-05-29 17:04     ` Jae Hyun Yoo
2019-05-24 23:17 ` [PATCH v2 11/11] media: aspeed: add a workaround to fix a silicon bug Jae Hyun Yoo
2019-05-29 14:07   ` Eddie James
2019-05-29 17:29     ` Jae Hyun Yoo [this message]
2019-05-31 16:32       ` Ryan Chen
2019-05-31 20:38         ` Jae Hyun Yoo
2019-05-29  9:55 ` [PATCH v2 00/11] Improve stability and add bug fixes of Aspeed video engine driver Hans Verkuil

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=cd1814db-4892-bba0-027a-9f51cd49b9b5@linux.intel.com \
    --to=jae.hyun.yoo@linux.intel.com \
    --cc=andrew@aj.id.au \
    --cc=benh@kernel.crashing.org \
    --cc=eajames@linux.ibm.com \
    --cc=eajames@linux.vnet.ibm.com \
    --cc=joel@jms.id.au \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=ryan_chen@aspeedtech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.