All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: linus.walleij@linaro.org, Stefan Agner <stefan@agner.ch>
Cc: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>,
	shawnguo@kernel.org, aalonso@freescale.com, b38343@freescale.com,
	ldewangan@nvidia.com, van.freenix@gmail.com,
	p.zabel@pengutronix.de, linux-gpio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pinctrl: freescale: avoid overwriting pin config when freeing GPIO
Date: Fri, 30 Sep 2016 07:42:08 +0530	[thread overview]
Message-ID: <20160930021208.GC14138@vireshk-i7> (raw)
In-Reply-To: <1478f2c1989ab735b0f86d2fe579f94f@agner.ch>

On 29-09-16, 09:33, Stefan Agner wrote:
> You need to differentiate between Vybrid and i.MX:
> 
> Vybrid muxes a pin to GPIO on gpio_request_one (via .gpio_request_enable
> callback)
> i.MX does not mux a pin as GPIO on its own, but needs to be muxed
> explicitly. That has been always the case...
> 
> I don't know what behavior is right, it is just "different"...

Hmm, I think What Vybrid and Tegra have done is better, but it would be better
to get inputs from Linus, which you already asked for :)

-- 
viresh

  reply	other threads:[~2016-09-30  2:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27  0:26 [PATCH] pinctrl: freescale: avoid overwriting pin config when freeing GPIO Stefan Agner
2016-09-27 12:12 ` Vladimir Zapolskiy
2016-09-27 12:12   ` Vladimir Zapolskiy
2016-09-27 16:37   ` Stefan Agner
2016-09-27 18:17     ` Vladimir Zapolskiy
2016-09-27 18:17       ` Vladimir Zapolskiy
2016-09-27 19:34       ` Stefan Agner
2016-09-27 20:28         ` Vladimir Zapolskiy
2016-09-27 20:28           ` Vladimir Zapolskiy
2016-09-28  2:00         ` Viresh Kumar
2016-09-28  3:38           ` Stefan Agner
2016-09-28  4:14             ` Viresh Kumar
2016-09-29 16:33               ` Stefan Agner
2016-09-30  2:12                 ` Viresh Kumar [this message]
2016-10-10  8:32                 ` Linus Walleij
2016-09-28 12:07             ` Vladimir Zapolskiy
2016-09-28 12:07               ` Vladimir Zapolskiy
2016-09-29  6:46               ` Viresh Kumar
2016-09-29 12:16                 ` Vladimir Zapolskiy
2016-09-29 12:16                   ` Vladimir Zapolskiy
2016-09-30  2:22                   ` Viresh Kumar
2016-10-10  8:33 ` Linus Walleij

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=20160930021208.GC14138@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=aalonso@freescale.com \
    --cc=b38343@freescale.com \
    --cc=ldewangan@nvidia.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=van.freenix@gmail.com \
    --cc=vladimir_zapolskiy@mentor.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 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.