From: Tony Lindgren <tony@atomide.com>
To: Kim Kyuwon <chammoru@gmail.com>
Cc: OMAP <linux-omap@vger.kernel.org>, David Brownell <david-b@pacbell.net>
Subject: Re: Suggestion regarding the ordering of GPIO MUX configurations
Date: Mon, 2 Mar 2009 08:40:10 -0800 [thread overview]
Message-ID: <20090302164008.GA11864@atomide.com> (raw)
In-Reply-To: <4d34a0a70903011837k2a1467b5s9c3b56e065d4b5c8@mail.gmail.com>
* Kim Kyuwon <chammoru@gmail.com> [090301 18:37]:
> Hi All.
>
> The current order of GPIO mux configurations is not sorted. It seems
> that all new GPIO MUX configurations are being inserted to the end as
> shown in next code
>
> /* arch/arm/plat-omap/include/mach/mux.h */
> 791 AH8_34XX_GPIO29,
> 792 J25_34XX_GPIO170,
> 793 AF26_34XX_GPIO0,
> 794 AF22_34XX_GPIO9,
> 795 L8_34XX_GPIO63,
> 796 AF6_34XX_GPIO140_UP,
> 797 AE6_34XX_GPIO141,
> 798 AF5_34XX_GPIO142,
> 799 AE5_34XX_GPIO143,
> 800 AG4_34XX_GPIO134,
> 801 U8_34XX_GPIO54,
> 802 AE4_34XX_GPIO136,
>
>
> I wonder if we can sort the order of GPIO MUX configurations and then
> insert new MUXs at right position. Can I ask your opinions?
Yes, I was thinking about the same. I'll combine the pending mux patches
and merge them into a single patch for mainline tree. While doing that
I'll sort them by gpio number. Will post the patch here for testing
probably today.
Regards,
Tony
next prev parent reply other threads:[~2009-03-02 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-02 2:37 Suggestion regarding the ordering of GPIO MUX configurations Kim Kyuwon
2009-03-02 16:40 ` Tony Lindgren [this message]
2009-03-02 17:31 ` Peter Barada
2009-03-02 17:47 ` Tony Lindgren
2009-03-02 19:41 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090302164008.GA11864@atomide.com \
--to=tony@atomide.com \
--cc=chammoru@gmail.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.