All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Sascha Hauer <kernel@pengutronix.de>
Subject: Re: [PATCH] ARM: dts: imx28: add gpio-ranges for internal gpio controller
Date: Mon, 22 May 2017 17:54:58 +0200	[thread overview]
Message-ID: <CACRpkdYvQdDXfK5QkWM6x6F4+UEQ=4oX_1gqdbjkk9n7tM5FSQ@mail.gmail.com> (raw)
In-Reply-To: <20170515071608.auju66dhylzaexkw@pengutronix.de>

On Mon, May 15, 2017 at 9:16 AM, Uwe Kleine-König
<u.kleine-koenig@pengutronix.de> wrote:
> On Mon, May 15, 2017 at 10:21:30AM +0800, Shawn Guo wrote:

>> You will need to free the GPIO before muxing it to a different function,
>> I think.
>
> IMHO this is a bad concept. This makes GPIOs more special than for
> example PWMs or LEDs. And it breaks some configurations (for example the
> make-pins-highz-on-idle setup in my previous mails).

So this is the reason why pin controllers can choose to be strict
or not: people disagree on the semantics.

But it's good if the driver maintainers agree for a certain driver :D

Yours,
Linus Walleij

WARNING: multiple messages have this Message-ID (diff)
From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: imx28: add gpio-ranges for internal gpio controller
Date: Mon, 22 May 2017 17:54:58 +0200	[thread overview]
Message-ID: <CACRpkdYvQdDXfK5QkWM6x6F4+UEQ=4oX_1gqdbjkk9n7tM5FSQ@mail.gmail.com> (raw)
In-Reply-To: <20170515071608.auju66dhylzaexkw@pengutronix.de>

On Mon, May 15, 2017 at 9:16 AM, Uwe Kleine-K?nig
<u.kleine-koenig@pengutronix.de> wrote:
> On Mon, May 15, 2017 at 10:21:30AM +0800, Shawn Guo wrote:

>> You will need to free the GPIO before muxing it to a different function,
>> I think.
>
> IMHO this is a bad concept. This makes GPIOs more special than for
> example PWMs or LEDs. And it breaks some configurations (for example the
> make-pins-highz-on-idle setup in my previous mails).

So this is the reason why pin controllers can choose to be strict
or not: people disagree on the semantics.

But it's good if the driver maintainers agree for a certain driver :D

Yours,
Linus Walleij

  reply	other threads:[~2017-05-22 15:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-08  8:59 [PATCH] ARM: dts: imx28: add gpio-ranges for internal gpio controller Uwe Kleine-König
2017-05-08  8:59 ` Uwe Kleine-König
2017-05-11  7:51 ` Shawn Guo
2017-05-11  7:51   ` Shawn Guo
2017-05-11  8:09   ` Uwe Kleine-König
2017-05-11  8:09     ` Uwe Kleine-König
2017-05-12  3:05     ` Shawn Guo
2017-05-12  3:05       ` Shawn Guo
2017-05-12  8:01       ` Uwe Kleine-König
2017-05-12  8:01         ` Uwe Kleine-König
2017-05-15  2:21         ` Shawn Guo
2017-05-15  2:21           ` Shawn Guo
2017-05-15  7:16           ` Uwe Kleine-König
2017-05-15  7:16             ` Uwe Kleine-König
2017-05-22 15:54             ` Linus Walleij [this message]
2017-05-22 15:54               ` 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='CACRpkdYvQdDXfK5QkWM6x6F4+UEQ=4oX_1gqdbjkk9n7tM5FSQ@mail.gmail.com' \
    --to=linus.walleij@linaro.org \
    --cc=fabio.estevam@nxp.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=u.kleine-koenig@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.