Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753026Ab3FQQFY (ORCPT ); Mon, 17 Jun 2013 12:05:24 -0400 Received: from mail-oa0-f48.google.com ([209.85.219.48]:62824 "EHLO mail-oa0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752354Ab3FQQFT (ORCPT ); Mon, 17 Jun 2013 12:05:19 -0400 MIME-Version: 1.0 In-Reply-To: <20130617072021.GB4465@atomide.com> References: <1370980749-15383-1-git-send-email-linus.walleij@stericsson.com> <51BA1FE7.4000900@wwwdotorg.org> <51BB3A2C.608@wwwdotorg.org> <20130617072021.GB4465@atomide.com> Date: Mon, 17 Jun 2013 18:05:18 +0200 Message-ID: Subject: Re: [PATCH] pinctrl: document the pinctrl PM states From: Linus Walleij To: Tony Lindgren Cc: Stephen Warren , Linus Walleij , Stephen Warren , Kevin Hilman , "linux-kernel@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , Ulf Hansson Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1202 Lines: 30 On Mon, Jun 17, 2013 at 9:20 AM, Tony Lindgren wrote: > First, I think the concept of remuxing (or even checking) _all_ the pins > for a consumer device is wrong on most if not all hardware. For past 10 > years I have not seen a case where _all_ the pins for a device would need > to be remuxed for any reason. We may be talking past each other here. On the ux500 we use a lot of runtime pincontrol, but none of this is *remuxing*. We are only *reconfiguring*. Now I know that Haojian only recently added pin config to the pinctrl-single.c driver so maybe you have mostly seen muxing in your driver so far, so you view of the world is a bit different. On the Nomadik pin controller we do mostly hogged muxing at boot time, but a lot of runtime reconfiguration. So our needs are very different. Bear in mind that struct pinctl * forks effects in two paths, one is muxing the other is config, like pull-ups etc. 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/