From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: moudy ho <moudy.ho@mediatek.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Jernej Skrabec <jernej.skrabec@siol.net>
Cc: Chun-Kuang Hu <chunkuang.hu@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Rob Landley <rob@landley.net>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
Alexandre Courbot <acourbot@chromium.org>,
tfiga@chromium.org, drinkcat@chromium.org, pihsun@chromium.org,
hsinyi@google.com, Maoguang Meng <maoguang.meng@mediatek.com>,
daoyuan huang <daoyuan.huang@mediatek.com>,
Ping-Hsun Wu <ping-hsun.wu@mediatek.com>,
menghui.lin@mediatek.com, sj.huang@mediatek.com,
allen-kh.cheng@mediatek.com, randy.wu@mediatek.com,
jason-jh.lin@mediatek.com, roy-cw.yeh@mediatek.com,
river.cheng@mediatek.com, srv_heupstream@mediatek.com
Subject: Re: [PATCH v11 2/3] dts: arm64: mt8183: add Mediatek MDP3 nodes
Date: Thu, 27 Jan 2022 11:57:23 +0100 [thread overview]
Message-ID: <08fc74c5-4f2f-8712-454d-8cf3aed4eb10@collabora.com> (raw)
In-Reply-To: <356f512b549f90b329775e249fd48eb2954ade02.camel@mediatek.com>
Il 25/01/22 09:20, moudy ho ha scritto:
> On Fri, 2022-01-21 at 12:58 +0100, AngeloGioacchino Del Regno wrote:
>> Il 05/01/22 10:37, Moudy Ho ha scritto:
>>> Add device nodes for Media Data Path 3 (MDP3) modules.
>>>
>>> Signed-off-by: Moudy Ho <moudy.ho@mediatek.com>
>>> ---
>>> arch/arm64/boot/dts/mediatek/mt8183.dtsi | 108
>>> ++++++++++++++++++++++-
>>> 1 file changed, 107 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
>>> b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
>>> index ba4584faca5a..b872ef1ff6b3 100644
>>> --- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
>>> +++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
>>> @@ -1325,6 +1325,79 @@
>>> mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX
>>> 0 0x1000>;
>>> };
>>>
>>> + mdp3_rdma0: mdp3_rdma0@14001000 {
>>> + compatible = "mediatek,mt8183-mdp3",
>>> + "mediatek,mt8183-mdp3-rdma0";
>>> + mediatek,scp = <&scp>;
>>> + mediatek,mdp3-comps = "mediatek,mt8183-mdp3-
>>> dl1",
>>> + "mediatek,mt8183-mdp3-
>>> dl2",
>>> + "mediatek,mt8183-mdp3-
>>> path1",
>>> + "mediatek,mt8183-mdp3-
>>> path2",
>>> + "mediatek,mt8183-mdp3-
>>> imgi",
>>> + "mediatek,mt8183-mdp3-
>>> exto";
>>> + reg = <0 0x14001000 0 0x1000>,
>>> + <0 0x14000000 0 0x1000>,
>>> + <0 0x14005000 0 0x1000>,
>>> + <0 0x14006000 0 0x1000>,
>>> + <0 0x15020000 0 0x1000>;
>>> + mediatek,gce-client-reg = <&gce SUBSYS_1400XXXX
>>> 0x1000 0x1000>,
>>> + <&gce SUBSYS_1400XXXX
>>> 0 0x1000>,
>>> + <&gce SUBSYS_1400XXXX
>>> 0x5000 0x1000>,
>>> + <&gce SUBSYS_1400XXXX
>>> 0x6000 0x1000>,
>>> + <&gce SUBSYS_1502XXXX
>>> 0 0x1000>;
>>> + power-domains = <&spm
>>> MT8183_POWER_DOMAIN_DISP>;
>>> + clocks = <&mmsys CLK_MM_MDP_RDMA0>,
>>> + <&mmsys CLK_MM_MDP_RSZ1>,
>>> + <&mmsys CLK_MM_MDP_DL_TXCK>,
>>> + <&mmsys CLK_MM_MDP_DL_RX>,
>>> + <&mmsys CLK_MM_IPU_DL_TXCK>,
>>> + <&mmsys CLK_MM_IPU_DL_RX>;
>>> + iommus = <&iommu M4U_PORT_MDP_RDMA0>;
>>> + mediatek,mmsys = <&mmsys>;
>>> + mediatek,mm-mutex = <&mutex>;
>>> + mediatek,mailbox-gce = <&gce>;
>>> + mboxes = <&gce 20 CMDQ_THR_PRIO_LOWEST 0>,
>>> + <&gce 21 CMDQ_THR_PRIO_LOWEST>,
>>> + <&gce 22 CMDQ_THR_PRIO_LOWEST>,
>>> + <&gce 23 CMDQ_THR_PRIO_LOWEST>;
>>
>> Hello Moudy,
>> the mboxes for gce 21, 22, 23 are missing the third cell. Please fix.
>>
>> Regards,
>> Angelo
>
> Hi Angelo,
> Thanks for the reminder, but I'm a bit confused, the previous
> version(v10) mentioned that the current upstream mbox has only 2
> cells.
> So I should follow this rule to remove the extra 0 in the first item as
> follows:
> + mboxes = <&gce 20 CMDQ_THR_PRIO_LOWEST>,
> + <&gce 21 CMDQ_THR_PRIO_LOWEST>,
> + <&gce 22 CMDQ_THR_PRIO_LOWEST>,
> + <&gce 23 CMDQ_THR_PRIO_LOWEST>;
>
> Thanks,
> Moudy Ho
Hello Moudy,
I'm sorry for this confusion and you are totally right in the proposed solution,
which is the exact opposite of what I said.
Thanks for understanding,
Angelo
>>
>>> + gce-subsys = <&gce 0x14000000 SUBSYS_1400XXXX>,
>>> + <&gce 0x14010000 SUBSYS_1401XXXX>,
>>> + <&gce 0x14020000 SUBSYS_1402XXXX>,
>>> + <&gce 0x15020000 SUBSYS_1502XXXX>;
>>> + };
>>> +
>>
>>
>
next prev parent reply other threads:[~2022-01-27 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 9:37 [PATCH v11 0/3] media: mediatek: support mdp3 on mt8183 platform Moudy Ho
2022-01-05 9:37 ` [PATCH v11 1/3] dt-binding: mt8183: add Mediatek MDP3 dt-bindings Moudy Ho
2022-01-21 21:16 ` Rob Herring
2022-01-24 11:40 ` AngeloGioacchino Del Regno
2022-01-05 9:37 ` [PATCH v11 2/3] dts: arm64: mt8183: add Mediatek MDP3 nodes Moudy Ho
2022-01-21 11:58 ` AngeloGioacchino Del Regno
2022-01-25 8:20 ` moudy ho
2022-01-27 10:57 ` AngeloGioacchino Del Regno [this message]
2022-01-05 9:37 ` [PATCH v11 3/3] media: platform: mtk-mdp3: add Mediatek MDP3 driver Moudy Ho
2022-02-02 17:08 ` Benjamin Gaignard
2022-03-16 8:35 ` [PATCH v11 0/3] media: mediatek: support mdp3 on mt8183 platform AngeloGioacchino Del Regno
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=08fc74c5-4f2f-8712-454d-8cf3aed4eb10@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=acourbot@chromium.org \
--cc=allen-kh.cheng@mediatek.com \
--cc=chunkuang.hu@kernel.org \
--cc=daoyuan.huang@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=geert+renesas@glider.be \
--cc=hsinyi@google.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jason-jh.lin@mediatek.com \
--cc=jernej.skrabec@siol.net \
--cc=laurent.pinchart@ideasonboard.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=maoguang.meng@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=menghui.lin@mediatek.com \
--cc=moudy.ho@mediatek.com \
--cc=pihsun@chromium.org \
--cc=ping-hsun.wu@mediatek.com \
--cc=randy.wu@mediatek.com \
--cc=river.cheng@mediatek.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.org \
--cc=roy-cw.yeh@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.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®