From: Louis Kuo <louis.kuo@mediatek.com>
To: <hans.verkuil@cisco.com>,
<laurent.pinchart+renesas@ideasonboard.com>, <tfiga@chromium.org>,
<keiichiw@chromium.org>, <matthias.bgg@gmail.com>,
<mchehab@kernel.org>
Cc: <yuzhao@chromium.org>, <zwisler@chromium.org>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>, <Sean.Cheng@mediatek.com>,
<sj.huang@mediatek.com>, <christie.yu@mediatek.com>,
<louis.kuo@mediatek.com>, <frederic.chen@mediatek.com>,
<Jerry-ch.Chen@mediatek.com>, <jungo.lin@mediatek.com>,
<Rynn.Wu@mediatek.com>, <linux-media@vger.kernel.org>,
<srv_heupstream@mediatek.com>, <devicetree@vger.kernel.org>
Subject: [RFC PATCH V4 4/4] dts: arm64: mt8183: Add sensor interface nodes
Date: Sun, 15 Sep 2019 14:50:04 +0800 [thread overview]
Message-ID: <20190915065004.20257-5-louis.kuo@mediatek.com> (raw)
In-Reply-To: <20190915065004.20257-1-louis.kuo@mediatek.com>
Add nodes for Mediatek's sensor interface device. Sensor interface module
embedded in Mediatek SOCs, works as a HW camera interface controller
intended for image and data transmission between cameras and host devices.
Signed-off-by: Louis Kuo <louis.kuo@mediatek.com>
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index 66aaa07f6cec..f1d081b99867 100644
--- a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
@@ -506,4 +506,18 @@
#clock-cells = <1>;
};
};
+
+ seninf: seninf@1a040000 {
+ compatible = "mediatek,mt8183-seninf";
+ reg = <0 0x1a040000 0 0x8000>,
+ <0 0x11C80000 0 0x6000>;
+ reg-names = "base_reg", "rx_reg";
+ interrupts = <GIC_SPI 251 IRQ_TYPE_LEVEL_LOW>;
+ power-domains = <&scpsys MT8183_POWER_DOMAIN_CAM>;
+ clocks = <&camsys CLK_CAM_SENINF>,
+ <&topckgen CLK_TOP_MUX_SENINF>;
+ clock-names = "CLK_CAM_SENINF", "CLK_TOP_MUX_SENINF";
+ status = "disabled";
+ };
+ };
};
--
2.18.0
next prev parent reply other threads:[~2019-09-15 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-15 6:50 [RFC PATCH V4 0/4] media: support Mediatek sensor interface driver Louis Kuo
2019-09-15 6:50 ` [RFC PATCH V4 1/4] media: platform: mtk-isp: Add " Louis Kuo
2019-09-16 1:28 ` Yingjoe Chen
2019-09-18 8:11 ` Sakari Ailus
2019-09-15 6:50 ` [RFC PATCH V4 2/4] media: platform: Add Mediatek sensor interface driver KConfig Louis Kuo
2019-09-16 1:18 ` Yingjoe Chen
2019-09-18 8:16 ` Sakari Ailus
2019-09-15 6:50 ` [RFC PATCH V4 3/4] dt-bindings: mt8183: Add sensor interface dt-bindings Louis Kuo
2019-09-16 5:33 ` Yingjoe Chen
2019-09-18 8:29 ` Sakari Ailus
2019-09-15 6:50 ` Louis Kuo [this message]
2019-09-16 5:36 ` [RFC PATCH V4 4/4] dts: arm64: mt8183: Add sensor interface nodes Yingjoe Chen
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=20190915065004.20257-5-louis.kuo@mediatek.com \
--to=louis.kuo@mediatek.com \
--cc=Jerry-ch.Chen@mediatek.com \
--cc=Rynn.Wu@mediatek.com \
--cc=Sean.Cheng@mediatek.com \
--cc=christie.yu@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=frederic.chen@mediatek.com \
--cc=hans.verkuil@cisco.com \
--cc=jungo.lin@mediatek.com \
--cc=keiichiw@chromium.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.org \
--cc=yuzhao@chromium.org \
--cc=zwisler@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;
as well as URLs for NNTP newsgroup(s).