Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S933388AbbESO6V (ORCPT <rfc822;w@1wt.eu>);
	Tue, 19 May 2015 10:58:21 -0400
Received: from mail-oi0-f44.google.com ([209.85.218.44]:35347 "EHLO
	mail-oi0-f44.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753895AbbESO6U (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 19 May 2015 10:58:20 -0400
MIME-Version: 1.0
In-Reply-To: <20150519075537.GU4004@lukather>
References: <1431707940-19372-1-git-send-email-jenskuske@gmail.com>
	<1431707940-19372-5-git-send-email-jenskuske@gmail.com>
	<20150517141922.GE4004@lukather>
	<5559B1AF.2010200@gmail.com>
	<20150519075537.GU4004@lukather>
Date: Tue, 19 May 2015 16:58:19 +0200
Message-ID: <CACRpkdaUHiqKaVr71p9sVaXHAdVYC2v6u-OT8pdnVC5rN_t+0Q@mail.gmail.com>
Subject: Re: [PATCH v2 04/10] pinctrl: sunxi: Prepare for building SoC
 specific drivers as modules
From: Linus Walleij <linus.walleij@linaro.org>
To: Maxime Ripard <maxime.ripard@free-electrons.com>,
        Johan Hovold <johan@kernel.org>
Cc: Jens Kuske <jenskuske@gmail.com>,
        =?UTF-8?Q?Emilio_L=C3=B3pez?= <emilio@elopez.com.ar>,
        Mike Turquette <mturquette@linaro.org>,
        Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
        Vishnu Patekar <vishnupatekar0510@gmail.com>,
        Hans de Goede <hdegoede@redhat.com>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        linux-sunxi <linux-sunxi@googlegroups.com>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Length: 842
Lines: 23

On Tue, May 19, 2015 at 9:55 AM, Maxime Ripard
<maxime.ripard@free-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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/