From: <sean.wang@mediatek.com>
To: mchehab@osg.samsung.com, hdegoede@redhat.com,
hkallweit1@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
matthias.bgg@gmail.com
Cc: devicetree@vger.kernel.org, ivo.g.dimitrov.75@gmail.com,
keyhaede@gmail.com, sean@mess.org,
Sean Wang <sean.wang@mediatek.com>,
linux-kernel@vger.kernel.org, andi.shyti@samsung.com,
hverkuil@xs4all.nl, linux-mediatek@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [PATCH v2 1/2] Documentation: devicetree: Add document bindings for mtk-cir
Date: Tue, 10 Jan 2017 17:13:50 +0800 [thread overview]
Message-ID: <1484039631-25120-2-git-send-email-sean.wang@mediatek.com> (raw)
In-Reply-To: <1484039631-25120-1-git-send-email-sean.wang@mediatek.com>
From: Sean Wang <sean.wang@mediatek.com>
This patch adds documentation for devicetree bindings for
Mediatek consumer IR controller.
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
---
.../devicetree/bindings/media/mtk-cir.txt | 24 ++++++++++++++++++++++
1 file changed, 24 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/mtk-cir.txt
diff --git a/Documentation/devicetree/bindings/media/mtk-cir.txt b/Documentation/devicetree/bindings/media/mtk-cir.txt
new file mode 100644
index 0000000..3850cbd
--- /dev/null
+++ b/Documentation/devicetree/bindings/media/mtk-cir.txt
@@ -0,0 +1,24 @@
+Device-Tree bindings for Mediatek consumer IR controller found in
+Mediatek SoC family
+
+Required properties:
+- compatible : "mediatek,mt7623-cir"
+- clocks : list of clock specifiers, corresponding to
+ entries in clock-names property;
+- clock-names : should contain "clk" entries;
+- interrupts : should contain IR IRQ number;
+- reg : should contain IO map address for IR.
+
+Optional properties:
+- linux,rc-map-name : Remote control map name.
+
+Example:
+
+cir: cir@10013000 {
+ compatible = "mediatek,mt7623-cir";
+ reg = <0 0x10013000 0 0x1000>;
+ interrupts = <GIC_SPI 87 IRQ_TYPE_LEVEL_LOW>;
+ clocks = <&infracfg CLK_INFRA_IRRX>;
+ clock-names = "clk";
+ linux,rc-map-name = "rc-rc6-mce";
+};
--
2.7.4
next prev parent reply other threads:[~2017-01-10 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 9:13 [PATCH v2 0/2] media: rc: add support for IR receiver on MT7623 SoC sean.wang
2017-01-10 9:13 ` sean.wang [this message]
2017-01-10 9:13 ` [PATCH v2 2/2] media: rc: add driver for IR remote " sean.wang
[not found] ` <1484039631-25120-3-git-send-email-sean.wang-NuS5LvNUpcJWk0Htik3J/w@public.gmane.org>
2017-01-10 11:09 ` Sean Young
2017-01-10 13:59 ` Sean Wang
2017-01-10 17:23 ` Sean Young
[not found] ` <20170110172355.GA27008-3XSxi2G4b3iXFJAUJl40Xg@public.gmane.org>
2017-01-11 9:19 ` Sean Wang
2017-01-10 12:07 ` kbuild test robot
[not found] ` <201701102015.fSM15CvI%fengguang.wu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-01-10 22:45 ` Andi Shyti
2017-01-11 9:27 ` Sean Wang
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=1484039631-25120-2-git-send-email-sean.wang@mediatek.com \
--to=sean.wang@mediatek.com \
--cc=andi.shyti@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=hkallweit1@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=keyhaede@gmail.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=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@osg.samsung.com \
--cc=robh+dt@kernel.org \
--cc=sean@mess.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).