linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>,
	Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
Cc: Archit Taneja <archit@ti.com>,
	linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH 0/3] OMAPDSS: Panel NEC: backlight handling changes
Date: Wed, 16 Jan 2013 12:45:06 +0000	[thread overview]
Message-ID: <1358340309-8774-1-git-send-email-peter.ujfalusi@ti.com> (raw)

Hi Tomi,

While working with Zoom2 which is using the NEC panel I noticed few issues with
the panel driver.
The first patch fixes one irritating warning print every time I boot the board.
With the third patch we can cleanly move to bl-pwm driver to handle the
backlight on Zoom2. In this case we should not register another backlight device
in the NEC panel driver.

Regards,
Peter
---
Peter Ujfalusi (3):
  OMAPDSS: Panel NEC: Set backlight type to remove boot time warning
  OMAPDSS: Panel NEC: Get rid of nec_80848_data structure
  OMAPDSS: Panel NEC: Only register backlight when we have valid
    callback

 .../omap2/displays/panel-nec-nl8048hl11-01b.c      | 81 ++++++++++------------
 1 file changed, 35 insertions(+), 46 deletions(-)

-- 
1.8.1


             reply	other threads:[~2013-01-16 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 12:45 Peter Ujfalusi [this message]
2013-01-16 12:45 ` [PATCH 1/3] OMAPDSS: Panel NEC: Set backlight type to remove boot time warning Peter Ujfalusi
2013-01-16 12:45 ` [PATCH 2/3] OMAPDSS: Panel NEC: Get rid of nec_80848_data structure Peter Ujfalusi
2013-01-16 12:45 ` [PATCH 3/3] OMAPDSS: Panel NEC: Only register backlight when we have valid callback Peter Ujfalusi

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=1358340309-8774-1-git-send-email-peter.ujfalusi@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=akpm@linux-foundation.org \
    --cc=archit@ti.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tomi.valkeinen@ti.com \
    /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).