Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1271218 > unrolled thread

Re: [PATCH] gpio: pxa: change initcall level second attempt

Started byLinus Walleij <linus.walleij@linaro.org>
First post2015-11-17 15:00 +0100
Last post2015-11-17 21:40 +0100
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH] gpio: pxa: change initcall level second attempt Linus Walleij <linus.walleij@linaro.org> - 2015-11-17 15:00 +0100
    Re: [PATCH] gpio: pxa: change initcall level second attempt Robert Jarzmik <robert.jarzmik@free.fr> - 2015-11-17 21:40 +0100

#1271218 — Re: [PATCH] gpio: pxa: change initcall level second attempt

FromLinus Walleij <linus.walleij@linaro.org>
Date2015-11-17 15:00 +0100
SubjectRe: [PATCH] gpio: pxa: change initcall level second attempt
Message-ID<qvOXE-5L7-1@gated-at.bofh.it>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [next] | [standalone]


#1271644

FromRobert Jarzmik <robert.jarzmik@free.fr>
Date2015-11-17 21:40 +0100
Message-ID<qvVcL-1sl-41@gated-at.bofh.it>
In reply to#1271218
Linus Walleij <linus.walleij@linaro.org> writes:

> Kludgy, but what can we do.
Indeed.

> Patch applied.
Thanks. I'll follow up with the current pinmux + partly pinconf implementation
to gather comments to amend/change/rework my current pxa2xx implementation.

I just need to split the patch into smaller chunks for easier review.

Cheers.

-- 
Robert
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web