From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dirk Behme <dirk.behme@googlemail.com>
Date: Sun, 12 Jul 2009 16:31:34 +0200
Subject: [U-Boot] [PATCH] Add support for the KwikByte KBOC
	OMAP35xx	board
In-Reply-To: <4A59F251.1050801@gmail.com>
References: <20090709170309.dzm4q9q74kk0sc04@host302.hostmonster.com>	<782515bb0907091806h40164862td187a1973200e559@mail.gmail.com>	<20090712131357.GE7218@game.jcrosoft.org>
	<4A59F251.1050801@gmail.com>
Message-ID: <4A59F3C6.2060607@googlemail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Nishanth Menon wrote:
> Jean-Christophe PLAGNIOL-VILLARD said the following on 07/12/2009 08:13 AM:
>>>> _sread*/\
>>>> + MUX_VAL(CP(D2D_MBUSFLAG),     (IEN  | PTD | DIS | M0)) /*d2d_mbusflag*/\
>>>> + MUX_VAL(CP(D2D_SBUSFLAG),     (IEN  | PTD | DIS | M0)) /*d2d_sbusflag*/\
>>>> + MUX_VAL(CP(SDRC_CKE0),                (IDIS | PTU | EN  | M0)) /*sdrc_cke0*/\
>>>> + MUX_VAL(CP(SDRC_CKE1),                (IDIS | PTU | EN  | M0)) /*sdrc_cke1*/
>>>>       
>>> one more reason why the mux needs a big change in mux handling :( I
>>> think we will end up with 1/2 a dozen crazy and code repetition for
>>> each board... Arrggghhh...
>>>     
>> NM: yes, it's really not easy to follow here
>> do you plan to do it soon?
>>   
> Been a little tied up recent days with "work load" hoping things to ease
> down.. will try to send out a mux cleanup rev next weekend..

Btw, I like the way we do pin mux in U-Boot at the moment (*). Or 
better: I can't imagine a way how to do it even better without 
introducing other disadvantages. But I will enjoy to have a look to 
your changes ;) Maybe you can give us already an idea of how you like 
to change it?

(*) What I like:

Having everything in one file for each board. With this, you can get a 
complete overview of board's pin mux with looking only in one file. 
And you can see immediately for each pin what is configured and how.

Best regards

Dirk