linux-kernel - Re: [PATCH 03/12] dt-bindings: display: mediatek: add EXDMA yaml for MT8196

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAGXv+5G8C8F5ua595Z3zs-D4vUP6YSUaxaUTGPQY-kfZ6am61g@mail.gmail.com>
Date: Fri, 24 Jan 2025 00:20:45 +0800
From: Chen-Yu Tsai <wenst@...omium.org>
To: Paul-pl Chen (陳柏霖) <Paul-pl.Chen@...iatek.com>
Cc: "robh@...nel.org" <robh@...nel.org>, "krzk@...nel.org" <krzk@...nel.org>, 
	Sunny Shen (沈姍姍) <Sunny.Shen@...iatek.com>, 
	Sirius Wang (王皓昱) <Sirius.Wang@...iatek.com>, 
	Nancy Lin (林欣螢) <Nancy.Lin@...iatek.com>, 
	AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>, 
	Xiandong Wang (王先冬) <Xiandong.Wang@...iatek.com>, 
	"linux-mediatek@...ts.infradead.org" <linux-mediatek@...ts.infradead.org>, 
	Project_Global_Chrome_Upstream_Group <Project_Global_Chrome_Upstream_Group@...iatek.com>, 
	"conor+dt@...nel.org" <conor+dt@...nel.org>, 
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, 
	"chunkuang.hu@...nel.org" <chunkuang.hu@...nel.org>, 
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "fshao@...omium.org" <fshao@...omium.org>, 
	"krzk+dt@...nel.org" <krzk+dt@...nel.org>, "p.zabel@...gutronix.de" <p.zabel@...gutronix.de>, 
	Singo Chang (張興國) <Singo.Chang@...iatek.com>, 
	Jason-JH Lin (林睿祥) <Jason-JH.Lin@...iatek.com>, 
	"linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, 
	"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.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 Fri, Jan 24, 2025 at 12:14 AM Paul-pl Chen (陳柏霖)
<Paul-pl.Chen@...iatek.com> wrote:
>
> On Thu, 2025-01-23 at 08:21 +0100, Krzysztof Kozlowski wrote:
> >
> > External email : Please do not click links or open attachments until
> > you have verified the sender or the content.
> >
> >
> > On 23/01/2025 07:11, Paul-pl Chen (陳柏霖) wrote:
> > >
> > > Hi Krzysztof
> > >
> > > I hope this email finds you well. I have a couple of questions
> > > regarding the EXDMA commit patch and decoupling:
> > >
> > > 1. Would removing the example from the EXDMA commit patch be
> > > sufficient
> > > to achieve decoupling for EXDMA YAML and MTK clock/power header?
> >
> > No
> >
> > >
> > > 2. If removing the example from the EXDMA YAML is not allowed, what
> > > alternative changes could we implement to achieve decoupling?
> >
> > Don't use the header constants but just some fake phandle.
> >
> >
> >
> > Best regards,
> > Krzysztof
>
> Hi Krzysztof,
>
> Once again, thanks for the review and reply.
>
> SO If we apply Chenyu's suggestion:
>
> + example:
> +-|
>
> +soc {
> +
> + disp_ovl0_exdma2: dma-controller@...50000 {
> +compatible = "mediatek,mt8196-exdma";
> +reg = <0 0x32850000 0 0x1000>;
> +clocks = <13>;
> +power-domains = <12>;
> +mediatek,larb = <88>;
> +iommus = <&mm_smmu 144>;
> +#dma-cells = <1>;
> +        };
> +    };
>
> Does this work for decoupling?
>

AFAIK it will since now it isn't including any headers.

ChenYu

> Best Regards,
>
> Paul
>
>
>
>
> ************* MEDIATEK Confidentiality Notice ********************
> The information contained in this e-mail message (including any
> attachments) may be confidential, proprietary, privileged, or otherwise
> exempt from disclosure under applicable laws. It is intended to be
> conveyed only to the designated recipient(s). Any use, dissemination,
> distribution, printing, retaining or copying of this e-mail (including its
> attachments) by unintended recipient(s) is strictly prohibited and may
> be unlawful. If you are not an intended recipient of this e-mail, or believe
> that you have received this e-mail in error, please notify the sender
> immediately (by replying to this e-mail), delete any and all copies of
> this e-mail (including any attachments) from your system, and do not
> disclose the content of this e-mail to any other person. Thank you!