linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Martin Kaiser <martin@kaiser.cx>
Cc: linux-fbdev@vger.kernel.org,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Mark Rutland <mark.rutland@arm.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] video: fbdev: imxfb: support AUS mode
Date: Fri, 3 Mar 2017 00:21:30 -0600	[thread overview]
Message-ID: <20170303062130.eu5i6kcusxuodoea@rob-hp-laptop> (raw)
In-Reply-To: <1488312337-32154-1-git-send-email-martin@kaiser.cx>

On Tue, Feb 28, 2017 at 09:04:16PM +0100, Martin Kaiser wrote:
> Some displays require setting AUS mode in the LDCD AUS Mode Control
> Register to work with the imxfb driver. Like the value of the Panel
> Configuration Register, the AUS Mode Control Register's value depends on
> the display mode.
> 
> Allow setting this register from the device tree. Make the device tree
> node optional to keep the DT ABI stable. This register is available only
> on imx21 and compatible chipsets. Update the device tree bindings with
> this info.
> 
> Signed-off-by: Martin Kaiser <martin@kaiser.cx>
> ---
> v2:
>   re-sending DT bindings and code changes as one patch

The opposite is what is prefered.

> 
>  .../devicetree/bindings/display/imx/fsl,imx-fb.txt    |  2 ++
>  drivers/video/fbdev/imxfb.c                           | 19 +++++++++++++++++++
>  include/linux/platform_data/video-imxfb.h             |  1 +
>  3 files changed, 22 insertions(+)

  reply	other threads:[~2017-03-03  6:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-27 10:56 [PATCH 1/2] video: fbdev: imxfb: support AUS mode Martin Kaiser
2017-02-27 10:56 ` [PATCH 2/2] dt-bindings: display: imx: entry for LAUSCR Martin Kaiser
2017-03-02 16:13   ` Rob Herring
2017-03-04  8:52     ` Martin Kaiser
2017-02-27 20:36 ` [PATCH 1/2] video: fbdev: imxfb: support AUS mode Uwe Kleine-König
2017-02-27 22:33   ` Martin Kaiser
2017-02-28 11:45     ` Bartlomiej Zolnierkiewicz
2017-02-28 20:04 ` [PATCH v2] " Martin Kaiser
2017-03-03  6:21   ` Rob Herring [this message]
2017-03-03  8:53     ` Bartlomiej Zolnierkiewicz
2017-03-04  8:38       ` Martin Kaiser
2017-03-08 18:22 ` [PATCH 1/2 v3] " Martin Kaiser
2017-03-08 18:22   ` [PATCH 2/2 v3] dt-bindings: display: imx: entry for " Martin Kaiser
2017-03-15 20:24     ` Rob Herring
2017-04-21  7:45 ` [PATCH 1/2 v3 resend] video: fbdev: imxfb: support " Martin Kaiser
2017-04-21  7:45   ` [PATCH 2/2 v3 resend] dt-bindings: display: imx: entry for " Martin Kaiser
2017-04-21  9:33   ` [PATCH 1/2 v3 resend] video: fbdev: imxfb: support " Bartlomiej Zolnierkiewicz
2017-04-21 10:31     ` Martin Kaiser
2017-04-21 10:29 ` [PATCH 1/2 v4] " Martin Kaiser
2017-04-21 10:29   ` [PATCH 2/2] dt-bindings: display: imx: entry for " Martin Kaiser
2017-04-21 12:29   ` [PATCH 2/2 v4] " Martin Kaiser
2017-04-21 14:50     ` Bartlomiej Zolnierkiewicz
2017-04-21 14:49   ` [PATCH 1/2 v4] video: fbdev: imxfb: support " Bartlomiej Zolnierkiewicz

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=20170303062130.eu5i6kcusxuodoea@rob-hp-laptop \
    --to=robh@kernel.org \
    --cc=b.zolnierkie@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=martin@kaiser.cx \
    --cc=p.zabel@pengutronix.de \
    /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).