linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Courbot <acourbot@chromium.org>
To: Irui Wang <irui.wang@mediatek.com>
Cc: Andrew-CT.Chen@mediatek.com, Maoguang.Meng@mediatek.com,
	srv_heupstream@mediatek.com, Yunfei.Dong@mediatek.com,
	erin.lo@mediatek.com, Longfei.Wang@mediatek.com,
	linux-kernel@vger.kernel.org, houlong.wei@mediatek.com,
	hverkuil@xs4all.nl, linux-mediatek@lists.infradead.org,
	PoChun.Lin@mediatek.com, matthias.bgg@gmail.com,
	hsinyi@google.com, mchehab@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-media@vger.kernel.org
Subject: Re: [PATCH 1/2] media: mtk-vpu: VPU should be in idle state before system is suspended
Date: Wed, 25 Nov 2020 11:46:39 +0900	[thread overview]
Message-ID: <CAPBb6MXQadf+0xP3VXAWwaew-OFrFGu-yPZfjXNtMqcfpjzQGg@mail.gmail.com> (raw)
In-Reply-To: <20201029011721.6705-1-irui.wang@mediatek.com>

On Thu, Oct 29, 2020 at 10:17 AM Irui Wang <irui.wang@mediatek.com> wrote:
>
> VPU should be in idle state before system is suspended
> or it will work abnormally like VPU program counter not
> in a correct address or VPU reset
>
> Signed-off-by: Irui Wang <irui.wang@mediatek.com>

FWIW,

Reviewed-by: Alexandre Courbot <acourbot@chromium.org>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2020-11-25  2:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  1:17 [PATCH 1/2] media: mtk-vpu: VPU should be in idle state before system is suspended Irui Wang
2020-10-29  1:17 ` [PATCH 2/2] media: mtk-vpu: dump VPU status when IPI times out Irui Wang
2020-11-25  2:46   ` Alexandre Courbot
2020-11-25  2:46 ` Alexandre Courbot [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=CAPBb6MXQadf+0xP3VXAWwaew-OFrFGu-yPZfjXNtMqcfpjzQGg@mail.gmail.com \
    --to=acourbot@chromium.org \
    --cc=Andrew-CT.Chen@mediatek.com \
    --cc=Longfei.Wang@mediatek.com \
    --cc=Maoguang.Meng@mediatek.com \
    --cc=PoChun.Lin@mediatek.com \
    --cc=Yunfei.Dong@mediatek.com \
    --cc=erin.lo@mediatek.com \
    --cc=houlong.wei@mediatek.com \
    --cc=hsinyi@google.com \
    --cc=hverkuil@xs4all.nl \
    --cc=irui.wang@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=mchehab@kernel.org \
    --cc=srv_heupstream@mediatek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).