From: Mans Rullgard <mans@mansr.com>
To: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: marex@denx.de
Subject: [PATCH 1/2] devicetree: mxsfb: add reset-active property
Date: Tue, 15 Dec 2015 17:24:56 +0000 [thread overview]
Message-ID: <1450200297-19243-1-git-send-email-mans@mansr.com> (raw)
Some boards connect the LCD_RESET pin to a reset input on the
display panel. On these boards, this pin must be set to the
proper level for the display to function.
This adds an optional "reset-active" property to the "display"
subnode such that devicetrees can specify the desired polarity
of the LCD_RESET pin.
Signed-off-by: Mans Rullgard <mans@mansr.com>
---
Documentation/devicetree/bindings/display/mxsfb.txt | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/mxsfb.txt b/Documentation/devicetree/bindings/display/mxsfb.txt
index 96ec517..cb7212a 100644
--- a/Documentation/devicetree/bindings/display/mxsfb.txt
+++ b/Documentation/devicetree/bindings/display/mxsfb.txt
@@ -13,6 +13,11 @@ Required properties:
- bits-per-pixel : <16> for RGB565, <32> for RGB888/666.
- bus-width : number of data lines. Could be <8>, <16>, <18> or <24>.
+Optional properties:
+- reset-active : <0>: reset pin is active low
+ <1>: reset pin is active high
+ omitted: reset pin not used
+
Required sub-node:
- display-timings : Refer to binding doc display-timing.txt for details.
--
2.6.3
next reply other threads:[~2015-12-15 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 17:24 Mans Rullgard [this message]
2015-12-20 3:38 ` [PATCH 1/2] devicetree: mxsfb: add reset-active property Rob Herring
2016-01-11 14:38 ` Måns Rullgård
2016-01-12 0:01 ` Rob Herring
[not found] ` <CAL_Jsq++UkEVJDcWVrDZ9pdkz++uU8uD_skYCAmGWv412RbnVA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-12 0:05 ` Måns Rullgård
2016-01-12 0:28 ` Rob Herring
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=1450200297-19243-1-git-send-email-mans@mansr.com \
--to=mans@mansr.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).