From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: xiuzhi <1450335857@qq.com>, openbmc <openbmc@lists.ozlabs.org>,
eajames <eajames@linux.ibm.com>, Joel Stanley <joel@jms.id.au>,
"Andrew.Jeffery" <andrew@aj.id.au>
Subject: Re: [PATCH dev-5.1 4/4] media: aspeed: add a workaround to fix asilicon bug (Jae Hyun Yoo)
Date: Mon, 3 Jun 2019 11:25:35 -0700 [thread overview]
Message-ID: <e9a3d82f-df30-6930-cb00-cdcf0bc7d4e7@linux.intel.com> (raw)
In-Reply-To: <tencent_10A7D5E3614D49E602F427F6@qq.com>
Hi Xiuzhi,
Thanks a lot for sharing the test result. Please let us update if you
find any issue in the further test.
Regards,
Jae
On 6/1/2019 7:46 PM, xiuzhi wrote:
> Hi Jae,
> This new patch works very well so far,
> I will test it more cases next week.
> Best,
> xiuzhi
>
>
> ------------------ Original ------------------
> *From: * "jae.hyun.yoo";<jae.hyun.yoo@linux.intel.com>;
> *Date: * Jun 1, 2019
> *To: * "xiuzhi"<1450335857@qq.com>; "openbmc"<openbmc@lists.ozlabs.org>;
> "eajames"<eajames@linux.ibm.com>; "joel"<joel@jms.id.au>;
> "andrew"<andrew@aj.id.au>;
> *Subject: * Re: [PATCH dev-5.1 4/4] media: aspeed: add a workaround to
> fix asilicon bug (Jae Hyun Yoo)
>
> On 5/31/2019 4:21 AM, xiuzhi wrote:
> > Hi Jae,
> > I tested this patch ,it works on 1680*1050,but I found an issue:
> >
> > The ikvm webpage will be black screen when you reboot the host after
> > switching solution between 1680*1050 and 800*600 on chrome browser (my
> > chrome version is 65).
> > you can reproduce it:
> > 1, Set host screen solution to 1680*1050 and save it . ikvm webpage works
> > 2,Set host screen solution to 800*600 and save it. ikvm webpage works
> > 3,Reset host screen solution to 1680*1050 and save it,
> > 4,reboot the host,
> > 5, the ikvm webpage is black screen when boot to Centos GUI
>
> Hi Xiuzhi,
>
> Checked that the issue isn't related this patch. Actually, that is
> caused by the first patch of this patch series. Since the patch removes
> source buffer allocation before mode detection, remaining allocation
> logic should be changed accordingly, otherwise it can't allocate buffers
> and eventually causes the issue. I'll fix the first patch in the next
> spin. In the meantime, you can apply below quick fix on top of what you
> tested the issue.
>
> Thanks,
> Jae
>
>
> diff --git a/drivers/media/platform/aspeed-video.c
> b/drivers/media/platform/aspeed-video.c
> index c2d4a2e6f20f..034f2f436d76 100644
> --- a/drivers/media/platform/aspeed-video.c
> +++ b/drivers/media/platform/aspeed-video.c
> @@ -865,20 +865,14 @@ static void aspeed_video_set_resolution(struct
> aspeed_video *video)
>
> size *= 4;
>
> - if (size == video->srcs[0].size / 2) {
> - aspeed_video_write(video, VE_SRC1_ADDR,
> - video->srcs[0].dma + size);
> - } else if (size == video->srcs[0].size) {
> - if (!aspeed_video_alloc_buf(video, &video->srcs[1], size))
> - goto err_mem;
> -
> - aspeed_video_write(video, VE_SRC1_ADDR, video->srcs[1].dma);
> - } else {
> - aspeed_video_free_buf(video, &video->srcs[0]);
> + if (size != video->srcs[0].size) {
> + if (video->srcs[0].size)
> + aspeed_video_free_buf(video, &video->srcs[0]);
> + if (video->srcs[1].size)
> + aspeed_video_free_buf(video, &video->srcs[1]);
>
> if (!aspeed_video_alloc_buf(video, &video->srcs[0], size))
> goto err_mem;
> -
> if (!aspeed_video_alloc_buf(video, &video->srcs[1], size))
> goto err_mem;
>
prev parent reply other threads:[~2019-06-03 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9.1558663202.24371.openbmc@lists.ozlabs.org>
2019-05-31 11:21 ` Re:[PATCH dev-5.1 4/4] media: aspeed: add a workaround to fix a silicon bug (Jae Hyun Yoo) xiuzhi
2019-05-31 20:37 ` [PATCH " Jae Hyun Yoo
2019-06-02 2:46 ` [PATCH dev-5.1 4/4] media: aspeed: add a workaround to fix asilicon " xiuzhi
2019-06-03 18:25 ` Jae Hyun Yoo [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=e9a3d82f-df30-6930-cb00-cdcf0bc7d4e7@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=1450335857@qq.com \
--cc=andrew@aj.id.au \
--cc=eajames@linux.ibm.com \
--cc=joel@jms.id.au \
--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 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.