From: Matthias Brugger <matthias.bgg@gmail.com>
To: Allen-KH Cheng <allen-kh.cheng@mediatek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Project_Global_Chrome_Upstream_Group@mediatek.com,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org,
hsinyi@chromium.org
Subject: Re: [PATCH v2 4/5] arm64: dts: mt8186: Add dsi node
Date: Wed, 23 Nov 2022 16:30:00 +0100 [thread overview]
Message-ID: <2238a980-7e04-1615-d836-c385a41628a9@gmail.com> (raw)
In-Reply-To: <20221123135531.23221-5-allen-kh.cheng@mediatek.com>
On 23/11/2022 14:55, Allen-KH Cheng wrote:
> Add dsi node for mt8186 SoC.
>
> Signed-off-by: Allen-KH Cheng <allen-kh.cheng@mediatek.com>
Applied, thanks!
> ---
> arch/arm64/boot/dts/mediatek/mt8186.dtsi | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8186.dtsi b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> index c0481f0dc527..4a2f7ad3c6f0 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8186.dtsi
> @@ -979,6 +979,25 @@
> power-domains = <&spm MT8186_POWER_DOMAIN_DIS>;
> };
>
> + dsi0: dsi@14013000 {
> + compatible = "mediatek,mt8186-dsi";
> + reg = <0 0x14013000 0 0x1000>;
> + clocks = <&mmsys CLK_MM_DSI0>,
> + <&mmsys CLK_MM_DSI0_DSI_CK_DOMAIN>,
> + <&mipi_tx0>;
> + clock-names = "engine", "digital", "hs";
> + interrupts = <GIC_SPI 311 IRQ_TYPE_LEVEL_HIGH 0>;
> + power-domains = <&spm MT8186_POWER_DOMAIN_DIS>;
> + resets = <&mmsys MT8186_MMSYS_SW0_RST_B_DISP_DSI0>;
> + phys = <&mipi_tx0>;
> + phy-names = "dphy";
> + status = "disabled";
> +
> + port {
> + dsi_out: endpoint { };
> + };
> + };
> +
> iommu_mm: iommu@14016000 {
> compatible = "mediatek,mt8186-iommu-mm";
> reg = <0 0x14016000 0 0x1000>;
next prev parent reply other threads:[~2022-11-23 15:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 13:55 [PATCH v2 0/5] Add some driver nodes for MT8186 SoC Allen-KH Cheng
2022-11-23 13:55 ` [PATCH v2 1/5] dt-bindings: usb: mtu3: add compatible for mt8186 Allen-KH Cheng
2022-11-23 15:11 ` Matthias Brugger
2022-11-25 8:00 ` Krzysztof Kozlowski
2022-11-25 8:41 ` Allen-KH Cheng (程冠勳)
2022-11-25 8:59 ` Krzysztof Kozlowski
2022-11-25 9:02 ` Allen-KH Cheng (程冠勳)
2022-11-23 13:55 ` [PATCH v2 2/5] arm64: dts: mt8186: Add power domains controller Allen-KH Cheng
2022-11-23 15:23 ` Matthias Brugger
2022-11-23 13:55 ` [PATCH v2 3/5] arm64: dts: mt8186: Add IOMMU and SMI nodes Allen-KH Cheng
2022-11-23 15:28 ` Matthias Brugger
2022-11-23 13:55 ` [PATCH v2 4/5] arm64: dts: mt8186: Add dsi node Allen-KH Cheng
2022-11-23 15:30 ` Matthias Brugger [this message]
2022-11-23 13:55 ` [PATCH v2 5/5] arm64: dts: mt8186: Add mtu3 nodes Allen-KH Cheng
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=2238a980-7e04-1615-d836-c385a41628a9@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=allen-kh.cheng@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hsinyi@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).