linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@misterjones.org>
To: Eric Miao <eric.y.miao@gmail.com>
Cc: ARM Linux <linux-arm-kernel@lists.arm.linux.org.uk>,
	linux-fbdev-devel@lists.sourceforge.net,
	Jaya Kumar <jayakumar.lkml@gmail.com>,
	Mike Rapoport <mike@compulab.co.il>,
	Richard Purdie <rpurdie@rpsys.net>, Ian Molton <spyro@f2s.com>,
	pHilipp Zabel <philipp.zabel@gmail.com>,
	Stefan Schmidt <stefan@datenfreihafen.org>,
	Marek Vasut <marek.vasut@gmail.com>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	Juergen Schindele <linux@schindele.name>
Subject: Re: [PATCH 1/2] pxa: introduce GPIOxx_LCD_* macros for easier pin configuration
Date: Thu, 11 Dec 2008 19:43:58 +0100	[thread overview]
Message-ID: <20081211194358.44af1dc5@why> (raw)
In-Reply-To: <f17812d70812110104y4b3d9b40i2f1c5d22e97988db@mail.gmail.com>

On Thu, 11 Dec 2008 17:04:22 +0800
"Eric Miao" <eric.y.miao@gmail.com> wrote:

> From ed2c9a22a9653880fad7e22333c7d6155c45c399 Mon Sep 17 00:00:00 2001
> From: Eric Miao <eric.miao@marvell.com>
> Date: Thu, 11 Dec 2008 13:34:54 +0800
> Subject: [PATCH] [ARM] pxa: introduce GPIOxx_LCD_* macros for easier
> pin configuration
> 
> For those peripherals with only one possible pin configuration,
> introduce handy macros of GPIOxx_*, it also avoids potential
> copy-and-paste errors.
> 
> Let's start from LCD for PXA25x/PXA27x, depending on the different
> mode used: passive (STN), active (TFT) and LCD with internal
> framebuffer (i.e. smart panel), and the actual number of pins used to
> connect to the LCD panel, the configurations slightly differ.
> 
> Also, let's fix the issue of LCD pin configurations are missed from
> some platforms (e.g. am200epd, cm-x270, e400)
> 
> NOTE: the 18bpp and smart panel are only available on PXA27x.
> 
> Signed-off-by: Eric Miao <eric.miao@marvell.com>

For the Viper part:

Acked-by: Marc Zyngier <maz@misterjones.org>

	M;
-- 
And if you don't know where you're going, any road will take you there.

-------------------------------------------------------------------
List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm-kernel
FAQ:        http://www.arm.linux.org.uk/mailinglists/faq.php
Etiquette:  http://www.arm.linux.org.uk/mailinglists/etiquette.php

  parent reply	other threads:[~2008-12-11 18:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-11  9:04 [PATCH 1/2] pxa: introduce GPIOxx_LCD_* macros for easier pin configuration Eric Miao
2008-12-11 16:39 ` Stefan Schmidt
2008-12-12  2:41   ` Eric Miao
2008-12-11 18:43 ` Marc Zyngier [this message]
2008-12-14  6:54 ` Mike Rapoport
2008-12-14 16:22 ` Jaya Kumar

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=20081211194358.44af1dc5@why \
    --to=maz@misterjones.org \
    --cc=eric.y.miao@gmail.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=jayakumar.lkml@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux@schindele.name \
    --cc=marek.vasut@gmail.com \
    --cc=mike@compulab.co.il \
    --cc=philipp.zabel@gmail.com \
    --cc=rpurdie@rpsys.net \
    --cc=spyro@f2s.com \
    --cc=stefan@datenfreihafen.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).