Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752866Ab3F0QJy (ORCPT ); Thu, 27 Jun 2013 12:09:54 -0400 Received: from bear.ext.ti.com ([192.94.94.41]:43252 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752018Ab3F0QJx (ORCPT ); Thu, 27 Jun 2013 12:09:53 -0400 Message-ID: <51CC6299.2070203@ti.com> Date: Thu, 27 Jun 2013 19:04:41 +0300 From: Grygorii Strashko User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Tony Lindgren CC: Linus Walleij , Kevin Hilman , Hebbar Gururaja , "linux-arm-kernel@lists.infradead.org" , Linux-OMAP , "linux-kernel@vger.kernel.org" , Stephen Warren Subject: Re: [RFC] ARM: OMAP2+: omap_device: add pinctrl handling References: <1371826990-25820-1-git-send-email-grygorii.strashko@ti.com> <20130625065811.GZ5523@atomide.com> <51CAEA90.90200@ti.com> <51CC45D3.2000305@ti.com> <20130627144535.GK5523@atomide.com> In-Reply-To: <20130627144535.GK5523@atomide.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1858 Lines: 55 On 06/27/2013 05:45 PM, Tony Lindgren wrote: > * Grygorii Strashko [130627 07:12]: >> >> As you can see, from 12 pins only 3 pins need to be reconfigured >> while switching from "active"->"idle" states and back (and as I >> mentioned above for OMAP "idle" == "sleep" now). >> >> Regarding "OFF" state: >> OMAP mux HW defines special state for unused pins which is selected >> by default after reset and need to be selected when device isn't >> used, for example: >> _MUXMODE - Functional multiplexing selection for pad >> 0x0: Select usbb1_hsic_data >> 0x3: Select gpio_96 >> 0x7: Select safe_mode <<--- pin unused > > The off mode bits can be enabled continuously, the mux hardware > automatically sets them. So sounds like you don't need any > separate "idle" "sleep" and "off" states, the following should > do: > > "default" (or "static") static pins that don't need to be touched > after consumer driver probe > > "active" dynamic pins that are not a subset of > "default" needed for runtime; these pins > are the same as "idle" below, but with > different muxing or pinconf device > runtime > > "idle" dynamic pins that are not a subset of > "default" needed for various idle modes; > these pins are the same as "active" above, > but with different muxing or pinconf for > various idle states > > Can you please confirm that these named modes are enough for > your needs? Confirm ) > > If your hardware does not have specific off mode bits, then > I can understand that you may need one mor state "off". > > Regards, > > Tony > Regards, -grygorii -- 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/