linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Yong Wu (吴勇)" <Yong.Wu@mediatek.com>
To: "dafna.hirschfeld@collabora.com" <dafna.hirschfeld@collabora.com>,
	"Irui Wang (王瑞)" <Irui.Wang@mediatek.com>
Cc: srv_heupstream <srv_heupstream@mediatek.com>,
	"krzysztof.kozlowski@canonical.com"
	<krzysztof.kozlowski@canonical.com>,
	"Youlin Pei (裴友林)" <youlin.pei@mediatek.com>,
	"Anan Sun (孙安安)" <Anan.Sun@mediatek.com>,
	"enric.balletbo@collabora.com" <enric.balletbo@collabora.com>,
	"kernel@collabora.com" <kernel@collabora.com>,
	"tfiga@chromium.org" <tfiga@chromium.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	"Xia Jiang (江霞)" <Xia.Jiang@mediatek.com>,
	"eizan@chromium.org" <eizan@chromium.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"Yi Kuo (郭懿)" <Yi.Kuo@mediatek.com>,
	"daniel@ffwll.ch" <daniel@ffwll.ch>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"evgreen@chromium.org" <evgreen@chromium.org>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"Anthony Huang (黃建嘉)" <Anthony.Huang@mediatek.com>,
	"Tiffany Lin (林慧珊)" <tiffany.lin@mediatek.com>,
	"acourbot@chromium.org" <acourbot@chromium.org>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"drinkcat@chromium.org" <drinkcat@chromium.org>,
	"hsinyi@chromium.org" <hsinyi@chromium.org>,
	"joro@8bytes.org" <joro@8bytes.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"frank-w@public-files.de" <frank-w@public-files.de>,
	"Ming-Fan Chen (陳明汎)" <Ming-Fan.Chen@mediatek.com>,
	"chunkuang.hu@kernel.org" <chunkuang.hu@kernel.org>,
	"mchehab@kernel.org" <mchehab@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"will.deacon@arm.com" <will.deacon@arm.com>,
	"robin.murphy@arm.com" <robin.murphy@arm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"mka@chromium.org" <mka@chromium.org>
Subject: Re: [PATCH v7 04/12] iommu/mediatek: Add device_link between the consumer and the larb devices
Date: Mon, 9 Aug 2021 08:00:34 +0000	[thread overview]
Message-ID: <1bea58ed853eab23d4af8829538ab9aa22cbd340.camel@mediatek.com> (raw)
In-Reply-To: <3f359c03-df44-2410-3172-2f17e620cada@collabora.com>

On Thu, 2021-08-05 at 15:22 +0200, Dafna Hirschfeld wrote:
> 
> On 30.07.21 04:52, Yong Wu wrote:
> > MediaTek IOMMU-SMI diagram is like below. all the consumer connect
> > with
> > smi-larb, then connect with smi-common.
> > 
> >          M4U
> >           |
> >      smi-common
> >           |
> >    -------------
> >    |         |    ...
> >    |         |
> > larb1     larb2
> >    |         |
> > vdec       venc
> > 
> > When the consumer works, it should enable the smi-larb's power
> > which
> > also need enable the smi-common's power firstly.
> > 
> > Thus, First of all, use the device link connect the consumer and
> > the
> > smi-larbs. then add device link between the smi-larb and smi-
> > common.
> > 
> > This patch adds device_link between the consumer and the larbs.
> > 
> > When device_link_add, I add the flag DL_FLAG_STATELESS to avoid
> > calling
> > pm_runtime_xx to keep the original status of clocks. It can avoid
> > two
> > issues:
> > 1) Display HW show fastlogo abnormally reported in [1]. At the
> > beggining,
> > all the clocks are enabled before entering kernel, but the clocks
> > for
> > display HW(always in larb0) will be gated after clk_enable and
> > clk_disable
> > called from device_link_add(->pm_runtime_resume) and rpm_idle. The
> > clock
> > operation happened before display driver probe. At that time, the
> > display
> > HW will be abnormal.
> > 
> > 2) A deadlock issue reported in [2]. Use DL_FLAG_STATELESS to skip
> > pm_runtime_xx to avoid the deadlock.
> > 
> > Corresponding, DL_FLAG_AUTOREMOVE_CONSUMER can't be added, then
> > device_link_removed should be added explicitly.
> > 
> > [1] 
> > https://lore.kernel.org/linux-mediatek/1564213888.22908.4.camel@mhfsdcap03/
> > [2] https://lore.kernel.org/patchwork/patch/1086569/
> > 
> > Suggested-by: Tomasz Figa <tfiga@chromium.org>
> > Signed-off-by: Yong Wu <yong.wu@mediatek.com>
> > Tested-by: Dafna Hirschfeld <dafna.hirschfeld@collabora.com> # on
> > mt8173
> 
> Hi, unfortunately, I have to take back the Tested-by tag.

sorry for inconvenience you.

(and sorry for reply late, there is something wrong about my local mail
server.)

> I am now testing the mtk-vcodec with latest kernel + patches sent
> from the mailing list:
> 
https://gitlab.collabora.com/eballetbo/linux/-/commits/topic/chromeos/chromeos-5.14
> which includes this patchset.
> 
> On chromeos I open a video conference with googl-meet which cause the
> mtk-vcodec vp8 encoder to run.
> If I kill it with `killall -9 chrome` I get some page fault messages
> from the iommu:

Does the "git bisect" point to this patch?

If you don't kill it, Does it also have these error below?

I don't know what happen about "killall -9 chrome', Does it cause
freeing some buffer?

> 
> [  837.255952] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read

This means "larb0 port0" translation fault. 

If I am not wrong, you work at mt8173, from [0], this is DISP_OVL0.

May be "killall -9 chrome" free the buffer(iova:0xfcff0000) that
DISP_OVL is accessing, then iommu complain it is not a valid iova.

[0] 
https://elixir.bootlin.com/linux/v5.14-rc1/source/include/dt-bindings/memory/mt8173-larb-port.h#L19

> [  837.265696] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.282367] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.299028] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.315683] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.332345] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.349004] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.365665] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.382329] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> [  837.400002] mtk-iommu 10205000.iommu: fault type=0x5
> iova=0xfcff0001 pa=0x0 larb=0 port=0 layer=1 read
> 
> In addition, running the encoder tests from the shell:
> 
> sudo --user=#1000 /usr/local/libexec/chrome-binary-
> tests/video_encode_accelerator_tests --
> gtest_filter=VideoEncoderTest.FlushAtEndOfStream_Multiple*  
> --codec=vp8
> /usr/local/share/tast/data/chromiumos/tast/local/bundles/cros/video/d
> ata/tulip2-320x180.yuv --disable_validator
> 
> At some point it fails with the error
> 
> [ 5472.161821] [MTK_V4L2][ERROR] mtk_vcodec_wait_for_done_ctx:32:
> [290] ctx->type=1, cmd=1, wait_event_interruptible_timeout
> time=1000ms out 0 0!
> [ 5472.174678] [MTK_VCODEC][ERROR][290]: vp8_enc_encode_frame()
> irq_status=0 failed
> [ 5472.182687] [MTK_V4L2][ERROR] mtk_venc_worker:1239: venc_if_encode
> failed=-5

+our venc guy Irui.

This looks VENC HW don't start to work. Does this caused by this
patchset?  this patchset only change the flow of power.

I guess we should check if the power/clock for venc here is enable or
not?

> 
> 
> If you have any idea of what might be the problem or how to debug?
> 
> Thanks,
> Dafna
> 
> > --

  reply	other threads:[~2021-08-09  8:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30  2:52 [PATCH v7 00/12] Clean up "mediatek,larb" Yong Wu
2021-07-30  2:52 ` [PATCH v7 01/12] dt-binding: mediatek: Get rid of mediatek,larb for multimedia HW Yong Wu
2021-07-30  2:52 ` [PATCH v7 02/12] iommu/mediatek-v1: Free the existed fwspec if the master dev already has Yong Wu
2021-07-30  2:52 ` [PATCH v7 03/12] iommu/mediatek: Add probe_defer for smi-larb Yong Wu
2021-07-30  2:52 ` [PATCH v7 04/12] iommu/mediatek: Add device_link between the consumer and the larb devices Yong Wu
2021-08-05 13:22   ` Dafna Hirschfeld
2021-08-09  8:00     ` Yong Wu (吴勇) [this message]
2021-07-30  2:52 ` [PATCH v7 05/12] media: mtk-jpeg: Get rid of mtk_smi_larb_get/put Yong Wu
2021-07-30  2:52 ` [PATCH v7 06/12] media: mtk-mdp: " Yong Wu
2021-07-30  2:52 ` [PATCH v7 07/12] drm/mediatek: Add pm runtime support for ovl and rdma Yong Wu
2021-07-30  2:52 ` [PATCH v7 08/12] drm/mediatek: Get rid of mtk_smi_larb_get/put Yong Wu
2021-07-30  2:52 ` [PATCH v7 09/12] media: mtk-vcodec: " Yong Wu
2021-07-30  2:52 ` [PATCH v7 10/12] memory: mtk-smi: " Yong Wu
2021-07-30  2:52 ` [PATCH v7 11/12] arm: dts: mediatek: Get rid of mediatek,larb for MM nodes Yong Wu
2021-07-30  2:52 ` [PATCH v7 12/12] arm64: " Yong Wu
2021-07-30 12:06 ` Aw: [PATCH v7 00/12] Clean up "mediatek,larb" Frank Wunderlich
2021-08-02  9:51 ` Joerg Roedel
2021-08-09  8:30   ` Yong Wu (吴勇)
2021-08-09  9:11     ` joro
2021-08-31 10:45 ` Yong Wu (吴勇)

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=1bea58ed853eab23d4af8829538ab9aa22cbd340.camel@mediatek.com \
    --to=yong.wu@mediatek.com \
    --cc=Anan.Sun@mediatek.com \
    --cc=Anthony.Huang@mediatek.com \
    --cc=Irui.Wang@mediatek.com \
    --cc=Ming-Fan.Chen@mediatek.com \
    --cc=Xia.Jiang@mediatek.com \
    --cc=Yi.Kuo@mediatek.com \
    --cc=acourbot@chromium.org \
    --cc=airlied@linux.ie \
    --cc=chunkuang.hu@kernel.org \
    --cc=dafna.hirschfeld@collabora.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=drinkcat@chromium.org \
    --cc=eizan@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=evgreen@chromium.org \
    --cc=frank-w@public-files.de \
    --cc=hsinyi@chromium.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joro@8bytes.org \
    --cc=kernel@collabora.com \
    --cc=krzysztof.kozlowski@canonical.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=mka@chromium.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=robin.murphy@arm.com \
    --cc=srv_heupstream@mediatek.com \
    --cc=tfiga@chromium.org \
    --cc=tiffany.lin@mediatek.com \
    --cc=will.deacon@arm.com \
    --cc=youlin.pei@mediatek.com \
    --subject='Re: [PATCH v7 04/12] iommu/mediatek: Add device_link between the consumer and the larb devices' \
    /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

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).