From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: Trying to understand how to use new OMAP mux code Date: Thu, 3 Jun 2010 17:37:01 +0300 Message-ID: <20100603143701.GJ30622@atomide.com> References: <738b3f7e1003111424t34326158j570980c691a98853@mail.gmail.com> <20100311224812.GU2900@atomide.com> <4C062DD4.2050701@cioinfoindus.fr> <20100602112130.GG5980@atomide.com> <20100602144606.4287c438.jhnikula@gmail.com> <4C07B136.8010008@cioinfoindus.fr> <20100603140642.GI30622@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:53936 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754893Ab0FCOhF (ORCPT ); Thu, 3 Jun 2010 10:37:05 -0400 Content-Disposition: inline In-Reply-To: <20100603140642.GI30622@atomide.com> Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Laurent Epinat Cc: linux-omap@vger.kernel.org, Jarkko Nikula * Tony Lindgren [100603 17:03]: > * Laurent Epinat [100603 16:36]: > > > > I would like one basic configuration for the modules with (twl,net,flash,.. all on the COM's) > > and for the rest, external driver for extra functionalities on the support board. > > > > This is why I need to change the mux pins dynamically by the driver module. > > If you really want to do it after the system has booted instead of passing > the desired muxing in the kernel cmdline, you could just do some > shell scripts to echo 0xXXXX > /sys/kernel/debug/omap_mux/whateverpin.. Or you could have the remux function in your board-*.c file, then pass the pointer to it to your custom remux module in the platform data. Then your custom remux module could change the mode via sysfs or something. Regards, Tony