[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d1f64020a9fa819a7928ea96a2608e4021b325a8.camel@mediatek.com>
Date: Tue, 11 Feb 2025 08:23:16 +0000
From: Paul-pl Chen (陳柏霖) <Paul-pl.Chen@...iatek.com>
To: "robh@...nel.org" <robh@...nel.org>, "krzk+dt@...nel.org"
<krzk+dt@...nel.org>, "conor+dt@...nel.org" <conor+dt@...nel.org>,
"chunkuang.hu@...nel.org" <chunkuang.hu@...nel.org>, "AngeloGioacchino Del
Regno" <angelogioacchino.delregno@...labora.com>, "krzk@...nel.org"
<krzk@...nel.org>
CC: Sunny Shen (沈姍姍) <Sunny.Shen@...iatek.com>,
Sirius Wang (王皓昱) <Sirius.Wang@...iatek.com>,
Nancy Lin (林欣螢) <Nancy.Lin@...iatek.com>,
Xiandong Wang (王先冬)
<Xiandong.Wang@...iatek.com>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, Project_Global_Chrome_Upstream_Group
<Project_Global_Chrome_Upstream_Group@...iatek.com>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>,
Jason-JH Lin (林睿祥) <Jason-JH.Lin@...iatek.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"fshao@...omium.org" <fshao@...omium.org>, "p.zabel@...gutronix.de"
<p.zabel@...gutronix.de>, Singo Chang (張興國)
<Singo.Chang@...iatek.com>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "matthias.bgg@...il.com"
<matthias.bgg@...il.com>, "treapking@...omium.org" <treapking@...omium.org>
Subject: Re: [PATCH 03/12] dt-bindings: display: mediatek: add EXDMA yaml for
MT8196
On Sat, 2025-01-18 at 09:37 +0100, Krzysztof Kozlowski wrote:
>
> >
> > (2)Primary Task of EXDMA:
> > The main function of EXDMA is to transfer buffers allocated by GEM
> > to
> > the subsequent display pipeline.
> > EXDMA serves as a bridge between memory allocated by GEM and the
> > display components, rather than acting as a general-purpose DMA
> > engine.
> > Based on the points above, we have decided to place the EXDMA
> > driver
> > under the DRM display subsystem rather than under the DMA
> > subsystem.
>
>
> I don't care if it uses GEM or kernel allocator or even 3rd party
> allocator. The question is: what is this device? If it is performing
> DMA, then it should be placed in "dma" directory. The rdma was placed
> differently but as you can easily check: it was never acked/reviewed,
> so
> don't use it as an example.
>
> Of course if it does not perform DMA, then it should not be in dma,
> but
> then I don't agree on using dma-cells here and anything like that in
> the
> driver.
>
> Best regards,
> Krzysztof
>
>
>
Hi KK,
Sorry, I just found this email was not send.
This email is discuss about the EXDMA under the display subsystem
The current placement of EXDMA under the display subsystem in
Mediatek's architecture is primarily due to its functional role as a
sub-device within the display pipeline.
In MT8196 hardware design, the sub-devices in display pipeline follow a
sequence of: EXDMA -> BLENDER -> OUTPROC -> PQ -> DVO.
In MT8195 hardware design, the sub-devices in display pipeline follow a
sequence of: OVL -> PQ ->DSI.
As we see, OVL has been divided into three new hardware IPs in MT8196.
OVL and EXDMA both have the ability to fetch data directly from DRAM
and can be regarded as DMA controller.
I also have confirmed with the hardware designer that EXDMA is a kind
of DMA, but it is specially designed to handle the graphical layer, and
has better performance than ordinary DMA.
Therefore, I think that moving EXDMA and OVL from the display folder to
the DMA folder, or only kepping them in the display folder is decided
by the two different views of DMA ability or display sub-device.
We will follow your instructions to put EXDMA on the place you decided.
Best, Paul
Powered by blists - more mailing lists