lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbaej0s0GNYUwbsmwR-fSRMuJR5H+GHrat1sevUBiCgmw@mail.gmail.com>
Date:	Tue, 17 Nov 2015 14:56:16 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Robert Jarzmik <robert.jarzmik@...e.fr>
Cc:	Alexandre Courbot <gnurou@...il.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] gpio: pxa: change initcall level second attempt

On Fri, Nov 13, 2015 at 9:22 PM, Robert Jarzmik <robert.jarzmik@...e.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@...e.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ