[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaUHiqKaVr71p9sVaXHAdVYC2v6u-OT8pdnVC5rN_t+0Q@mail.gmail.com>
Date: Tue, 19 May 2015 16:58:19 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Maxime Ripard <maxime.ripard@...e-electrons.com>,
Johan Hovold <johan@...nel.org>
Cc: Jens Kuske <jenskuske@...il.com>,
Emilio López <emilio@...pez.com.ar>,
Mike Turquette <mturquette@...aro.org>,
Rob Herring <robh+dt@...nel.org>, Chen-Yu Tsai <wens@...e.org>,
Vishnu Patekar <vishnupatekar0510@...il.com>,
Hans de Goede <hdegoede@...hat.com>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-sunxi <linux-sunxi@...glegroups.com>
Subject: Re: [PATCH v2 04/10] pinctrl: sunxi: Prepare for building SoC
specific drivers as modules
On Tue, May 19, 2015 at 9:55 AM, Maxime Ripard
<maxime.ripard@...e-electrons.com> wrote:
>> Apart from that, currently the kernel panics some seconds after removing
>> the pinctrl module because mmc wants to access a gpio. Can this be
>> prevented somehow? I think pinctrl must not be removed once other
>> devices use any pin-related things.
>
> pinctrl_unregister doesn't look like it cares about whether or not
> there's users left in the system.
Both GPIO and pinctrl has this problem, Johan Hovold has been
looking at fixing the GPIO side of things.
Patches welcome.
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