From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Vikas Sajjan <vikas.sajjan@linaro.org>
Cc: Thomas Abraham <thomas.abraham@linaro.org>,
linux-samsung-soc@vger.kernel.org, kgene.kim@samsung.com,
devicetree-discuss@lists.ozlabs.org, inki.dae@samsung.com,
linaro-kernel@lists.linaro.org
Subject: Re: [PATCH v9 4/4] ARM: dts: Add FIMD DT binding Documentation
Date: Mon, 25 Mar 2013 12:56:32 +0100 [thread overview]
Message-ID: <51503B70.8040506@samsung.com> (raw)
In-Reply-To: <CAJuYYwQZKXXVNNbDS20d8i6mybzyRc_Y8BQs73NSw6mUVwsGwQ@mail.gmail.com>
On 03/25/2013 12:10 PM, Thomas Abraham wrote:
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/video/samsung-fimd.txt
>> @@ -0,0 +1,68 @@
>> +Device-Tree bindings for Samsung SoC display controller (FIMD)
[...]
>> +- interrupts : should contain a list of all FIMD IP block interrupts:
>> + FIFO Level, VSYNC, LCD_SYSTEM. The interrupt specifier format depends
>> + on the interrupt controller used.
Since the interrupt order is supposed to be defined by the binding, perhaps
it could be rephrased to something like:
- interrupts : should contain a list of all FIMD IP block interrupts in
order: FIFO Level, VSYNC, LCD_SYSTEM. The interrupt specifier format
depends on the interrupt controller used.
>> +- interrupt-names : should contain the interrupt names: "fifo", "vsync",
>> + "lcd_sys", in the same order as they were listed in the interrupts
>> + property.
>> +
>> +- pinctrl : property defining the pinctrl configurations with a phandle
>> +
>> +- pinctrl-names : "default" state needs to be specified in the fimd node
>> + The pinctrl bindings defined in
>> + ../../../pinctrl/pinctrl-bindings.txt must be used to define a
>> + pinctrl state named "default".
The path should be ../pinctrl/pinctrl-bindings.txt. It probably makes to sense
to either have this one sentence or pinctrl/pinctrl-names properties listed
with their description. So for example
- pinctrl : pin control group to be used for this controller;
- pinctrl-names : should contain "default" entry;
or
The pinctrl bindings defined in ../pinctrl/pinctrl-bindings.txt must be used
to define a pinctrl state named "default".
next prev parent reply other threads:[~2013-03-25 11:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 13:56 [PATCH v9 0/4] Add DRM FIMD DT support for Exynos4 DT Machines Vikas Sajjan
[not found] ` <1363960608-23825-1-git-send-email-vikas.sajjan-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-03-22 13:56 ` [PATCH v9 1/4] ARM: dts: Add FIMD node to exynos4 Vikas Sajjan
2013-03-22 13:56 ` [PATCH v9 2/4] ARM: dts: Add lcd pinctrl node entries for EXYNOS4412 SoC Vikas Sajjan
2013-03-25 11:00 ` Thomas Abraham
2013-03-22 13:56 ` [PATCH v9 3/4] ARM: dts: Add FIMD node and display timing node to exynos4412-origen.dts Vikas Sajjan
2013-03-25 11:02 ` Thomas Abraham
2013-03-22 13:56 ` [PATCH v9 4/4] ARM: dts: Add FIMD DT binding Documentation Vikas Sajjan
2013-03-25 11:10 ` Thomas Abraham
2013-03-25 11:56 ` Sylwester Nawrocki [this message]
2013-03-25 10:49 ` [PATCH v9 0/4] Add DRM FIMD DT support for Exynos4 DT Machines Vikas Sajjan
2013-03-25 11:04 ` Kukjin Kim
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=51503B70.8040506@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=inki.dae@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=thomas.abraham@linaro.org \
--cc=vikas.sajjan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.