linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: "Tony Lindgren" <tony@atomide.com>,
	"Mika Penttilä" <mika.penttila@nextfour.com>
Cc: Gary Bisson <gary.bisson@boundarydevices.com>,
	Stefan Agner <stefan@agner.ch>, Shawn Guo <shawnguo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH] fix pinctrl setup for i.IMX6
Date: Thu, 16 Mar 2017 12:28:11 +0100	[thread overview]
Message-ID: <CACRpkdZNe3s4ipc_Dbbm0Pr-Bz0-a_oOkGCgECsbp75dFSZOgw@mail.gmail.com> (raw)
In-Reply-To: <20170315162639.GK20572@atomide.com>

On Wed, Mar 15, 2017 at 5:26 PM, Tony Lindgren <tony@atomide.com> wrote:

> I think as a regression fix for the -rc series, we should use Mika's
> patch with the following tweaks:
>
> 1. Instead of adding yet another devm_pinctrl_register_and_init(),
>    let's just make devm_pinctrl_register_and_init() not call start
>    automatically. If people prefer to use Mika's naming for it
>    with nostart, I have no problem with that. But let's then rename
>    the current devm_pinctrl_register_and_init() so we are not stuck
>    with another interface with issues.
>
> 2. Update the four drivers using devm_pinctrl_register_and_init()
>    to also call start separately.
>
> Mika, care to update your patch for that?

OK sounds reasonable waiting for a revised patch from Mika.

Yours,
Linus Walleij

  reply	other threads:[~2017-03-16 11:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-28  6:00 [PATCH] fix pinctrl setup for i.IMX6 Mika Penttilä
2017-03-14 14:47 ` Linus Walleij
2017-03-14 14:55   ` Gary Bisson
2017-03-15 16:26     ` Tony Lindgren
2017-03-16 11:28       ` Linus Walleij [this message]
2017-03-14 14:57   ` Tony Lindgren

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=CACRpkdZNe3s4ipc_Dbbm0Pr-Bz0-a_oOkGCgECsbp75dFSZOgw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=gary.bisson@boundarydevices.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.penttila@nextfour.com \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    --cc=tony@atomide.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).