From: Varka Bhadram <varkabhadram@gmail.com>
To: Zhangfei Gao <zhangfei.gao@linaro.org>,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
sean@mess.org, arnd@arndb.de, haifeng.yan@linaro.org,
jchxue@gmail.com
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-media@vger.kernel.org,
Guoxiong Yan <yanguoxiong@huawei.com>
Subject: Re: [PATCH v3 1/3] rc: Add DT bindings for hix5hd2
Date: Fri, 29 Aug 2014 09:00:37 +0530 [thread overview]
Message-ID: <53FFF3DD.7030702@gmail.com> (raw)
In-Reply-To: <1409238977-19444-2-git-send-email-zhangfei.gao@linaro.org>
On 08/28/2014 08:46 PM, Zhangfei Gao wrote:
> From: Guoxiong Yan <yanguoxiong@huawei.com>
>
> Signed-off-by: Guoxiong Yan <yanguoxiong@huawei.com>
> Signed-off-by: Zhangfei Gao <zhangfei.gao@linaro.org>
> ---
> .../devicetree/bindings/media/hix5hd2-ir.txt | 25 ++++++++++++++++++++
> 1 file changed, 25 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/hix5hd2-ir.txt
>
> diff --git a/Documentation/devicetree/bindings/media/hix5hd2-ir.txt b/Documentation/devicetree/bindings/media/hix5hd2-ir.txt
> new file mode 100644
> index 0000000..2bd88b9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/hix5hd2-ir.txt
> @@ -0,0 +1,25 @@
> +Device-Tree bindings for hix5hd2 ir IP
> +
> +Required properties:
> +- compatible: Should contain "hisilicon,hix5hd2-ir".
> +- reg: Base physical address of the controller and length of memory
> + mapped region.
> +- interrupts: interrupt-specifier for the sole interrupt generated by
> + the device. The interrupt specifier format depends on the interrupt
> + controller parent.
> +- clocks: clock phandle and specifier pair.
> +- hisilicon,power-syscon: phandle of syscon used to control power.
> +
It would be readable if
Required properties:
- compatible : Should contain "hisilicon,hix5hd2-ir".
- reg : Base physical address of the controller and length of memory mapped region.
- interrupts : interrupt-specifier for the sole interrupt generated by
the device. The interrupt specifier format depends on the interrupt
controller parent.
...
> +Optional properties:
> +- linux,rc-map-name : Remote control map name.
> +
> +Example node:
> +
> + ir: ir@f8001000 {
> + compatible = "hisilicon,hix5hd2-ir";
> + reg = <0xf8001000 0x1000>;
> + interrupts = <0 47 4>;
> + clocks = <&clock HIX5HD2_FIXED_24M>;
> + hisilicon,power-syscon = <&sysctrl>;
> + linux,rc-map-name = "rc-tivo";
> + };
--
Regards,
Varka Bhadram.
next prev parent reply other threads:[~2014-08-29 3:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 15:16 [PATCH v3 0/3] Introduce hix5hd2 IR transmitter driver Zhangfei Gao
2014-08-28 15:16 ` [PATCH v3 1/3] rc: Add DT bindings for hix5hd2 Zhangfei Gao
2014-08-29 3:30 ` Varka Bhadram [this message]
2014-08-28 15:16 ` [PATCH v3 2/3] rc: Introduce hix5hd2 IR transmitter driver Zhangfei Gao
2014-08-28 16:22 ` Sean Young
2014-08-30 13:24 ` zhangfei
2014-08-29 3:41 ` Varka Bhadram
2014-08-30 13:58 ` zhangfei
2014-08-28 15:16 ` [PATCH v3 3/3] ARM: dts: hix5hd2: add ir node Zhangfei Gao
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=53FFF3DD.7030702@gmail.com \
--to=varkabhadram@gmail.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=haifeng.yan@linaro.org \
--cc=jchxue@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@samsung.com \
--cc=sean@mess.org \
--cc=yanguoxiong@huawei.com \
--cc=zhangfei.gao@linaro.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).