All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Alexandre Courbot <acourbot@nvidia.com>
Cc: dri-devel@lists.freedesktop.org, kernel@pengutronix.de,
	Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Subject: Re: [PATCH] drm/tilcdc: panel: make better use of gpiod API
Date: Wed, 10 Jun 2015 08:59:00 +0200	[thread overview]
Message-ID: <20150610065900.GL18985@pengutronix.de> (raw)
In-Reply-To: <5577A015.2000809@nvidia.com>

On Wed, Jun 10, 2015 at 11:25:25AM +0900, Alexandre Courbot wrote:
> On 06/09/2015 06:43 PM, Uwe Kleine-König wrote:
> >Since 39b2bbe3d715 (gpio: add flags argument to gpiod_get*() functions)
> >which appeared in v3.17-rc1, the gpiod_get* functions take an additional
> >parameter that allows to specify direction and initial value for output.
> >
> >Furthermore there is devm_gpiod_get_optional which is designed to get
> >optional gpios.
> >
> >Simplify driver accordingly.
> 
> Nice!
> 
> Acked-by: Alexandre Courbot <acourbot@nvidia.com>
By the way, my tree based on 4.1-rc7 has all instances fixed and I sent
out all required patches. So I'd say we can make the flags argument
mandatory for 4.3.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-06-10  6:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09  9:43 [PATCH] drm/tilcdc: panel: make better use of gpiod API Uwe Kleine-König
2015-06-10  2:25 ` Alexandre Courbot
2015-06-10  6:59   ` Uwe Kleine-König [this message]
2015-06-10  7:01     ` Alexandre Courbot
2015-06-10 13:04 ` Linus Walleij
2015-06-15 21:11 ` Uwe Kleine-König

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=20150610065900.GL18985@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=acourbot@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.