From: Rob Herring <robh@kernel.org>
To: Liviu Dudau <Liviu.Dudau@arm.com>
Cc: Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Russell King <rmk+kernel@arm.linux.org.uk>,
Jean-Francois Moine <moinejf@free.fr>,
DT <devicetree@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: tda998x: Document the required 'port' node.
Date: Fri, 4 Dec 2015 12:54:31 -0600 [thread overview]
Message-ID: <20151204185431.GA9463@rob-hp-laptop> (raw)
In-Reply-To: <1449056139-31222-1-git-send-email-Liviu.Dudau@arm.com>
On Wed, Dec 02, 2015 at 11:35:39AM +0000, Liviu Dudau wrote:
> All the users of the tda998x driver are component based and bind the
> driver via the device graph method described in
> Documentation/devicetree/bindings/graph.txt. Add the fact that the
> 'port' node is required to the bindings.
>
> Signed-off-by: Liviu Dudau <Liviu.Dudau@arm.com>
Applied, thanks.
Rob
> ---
> Documentation/devicetree/bindings/display/bridge/tda998x.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/bridge/tda998x.txt b/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> index e9e4bce..e178e6b 100644
> --- a/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> +++ b/Documentation/devicetree/bindings/display/bridge/tda998x.txt
> @@ -5,6 +5,10 @@ Required properties;
>
> - reg: I2C address
>
> +Required node:
> + - port: Input port node with endpoint definition, as described
> + in Documentation/devicetree/bindings/graph.txt
> +
> Optional properties:
> - interrupts: interrupt number and trigger type
> default: polling
> --
> 2.6.2
>
prev parent reply other threads:[~2015-12-04 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 11:35 Liviu Dudau
2015-12-04 18:54 ` Rob Herring [this message]
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=20151204185431.GA9463@rob-hp-laptop \
--to=robh@kernel.org \
--cc=Liviu.Dudau@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=moinejf@free.fr \
--cc=pawel.moll@arm.com \
--cc=rmk+kernel@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®