linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] gpio: pxa: change initcall level second attempt
Date: Tue, 17 Nov 2015 14:56:16 +0100	[thread overview]
Message-ID: <CACRpkdbaej0s0GNYUwbsmwR-fSRMuJR5H+GHrat1sevUBiCgmw@mail.gmail.com> (raw)
In-Reply-To: <1447446158-20213-1-git-send-email-robert.jarzmik@free.fr>

On Fri, Nov 13, 2015 at 9:22 PM, Robert Jarzmik <robert.jarzmik@free.fr> wrote:

> This patch is a second attempt at what was previously in commit
> 6c7e660a27da ("gpio: pxa: set initcall level to module init").
>
> The goal is the same : enable gpio & pinctrl driver to work
> together. As pinctrl driver will be initialized at device level, the
> gpio should be as well, so that the deferring mechanism is honored.
>
> Yet this patch should also respect the legacy platforms, so the set of
> constraints is :
>  - in legacy platforms (ie. non dt), gpio_[gs]et_*() should be available
>    for machine code => core initcall
>  - in new platforms (ie. dt based), pinctrl will be available and no
>    machine code => device initcall
>
> In order to fullfill all these constraints, the initcall level is either
> postcore for non devicetree platforms, and device for devicetree platforms.
>
> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>

Kludgy, but what can we do.
Patch applied.

Yours,
Linus Walleij

  reply	other threads:[~2015-11-17 13:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-13 20:22 [PATCH] gpio: pxa: change initcall level second attempt Robert Jarzmik
2015-11-17 13:56 ` Linus Walleij [this message]
2015-11-17 20:37   ` Robert Jarzmik

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=CACRpkdbaej0s0GNYUwbsmwR-fSRMuJR5H+GHrat1sevUBiCgmw@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=gnurou@gmail.com \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.jarzmik@free.fr \
    /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).