Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1768024Ab2KOO1H (ORCPT ); Thu, 15 Nov 2012 09:27:07 -0500 Received: from mail.free-electrons.com ([88.190.12.23]:57521 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1767933Ab2KOO1F (ORCPT ); Thu, 15 Nov 2012 09:27:05 -0500 Date: Thu, 15 Nov 2012 15:26:52 +0100 From: Thomas Petazzoni To: Linus Walleij Cc: Mark Brown , Stephen Warren , Linus Walleij , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Stephen Warren , Anmar Oueja , Felipe Balbi , Benoit Cousson , Dmitry Torokhov , Mitch Bradley , Ulf Hansson , "Rafael J. Wysocki" , Kevin Hilman , Jean-Christophe PLAGNIOL-VILLARD , Rickard Andersson , Greg Kroah-Hartman , Russell King Subject: Re: [PATCH] RFC: pinctrl: grab default handler with bus notifiers Message-ID: <20121115152652.44c567d5@skate> In-Reply-To: References: <1352636539-6318-1-git-send-email-linus.walleij@stericsson.com> <50A15A54.3090803@wwwdotorg.org> <20121113063546.GD18224@opensource.wolfsonmicro.com> Organization: Free Electrons X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1721 Lines: 44 Linus, On Thu, 15 Nov 2012 15:03:40 +0100, Linus Walleij wrote: > > I have to say that I agree with this, notifiers seem to make life more > > complicated for limited gain. Otherwise I guess we could enhance > > notifiers so that they're able to trigger deferrals? > > OK I'll have to come up with a patch to the device core > instead... it'll be much simpler anyway and if both of you guys > can back it I guess Greg might be OK with it too. At ELCE, I've discussed with one person having an interesting use case: they are using the same pin for two different purposes during the system operation. At boot time, this pin is muxed as a SPI pin and is used to program the bitstream of a FPGA. This is done in Linux, through a userspace application. Then, once it is done, this pin is remuxed as a UART pin, and used to communicate with another device on the board. If the pinctrl configuration is done at probe() time inside the driver core, then how can this kind of use case be supported? If each driver does its own muxing, we could think of letting the SPI and UART driver only do their muxing when the device is opened, and remove their muxing when the device is closed, so that such sharing of pins for two separate functions could be supported. Is this something we want to support? Best regards, Thomas -- Thomas Petazzoni, Free Electrons Kernel, drivers, real-time and embedded Linux development, consulting, training and support. http://free-electrons.com -- 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/