From: Mike Rapoport <mike@compulab.co.il>
To: Cliff Brake <cliff.brake@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: several OMAP newbie questions
Date: Wed, 09 Sep 2009 17:51:01 +0300 [thread overview]
Message-ID: <4AA7C0D5.2070106@compulab.co.il> (raw)
In-Reply-To: <f96d234e0909041508m73e0f2a1r946f1c446d3880b6@mail.gmail.com>
Cliff Brake wrote:
> On Tue, Sep 1, 2009 at 6:34 AM, Mike Rapoport<mike@compulab.co.il> wrote:
>
>> 3) If I'm not much mistaken, board specific pin mux configuration has to deal
>> with arch/arm/plat-omap/include/mach/mux.h and arch/arm/mach-omap2/mux.c. For
>> instance, if my board uses ULPI pins that have not been defined already, I need
>> to patch those file with my pin mux definitions. Am I right here, or have I
>> missed something?
>
> It seems to me there should be a global mux configuration per CPU, but
> should be configurable per board, group of boards, etc. What I would
> like is a set of routines can be used to configure the mux that is
> then called by the board files (similar to PXA).
Yeah, I actually was missing pxa_mfp_config()...
The omap34xx_pins seems somewhat sparse...
>
> Cliff
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2009-09-09 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 10:34 several OMAP newbie questions Mike Rapoport
2009-09-04 22:08 ` Cliff Brake
2009-09-09 14:51 ` Mike Rapoport [this message]
2009-09-10 16:09 ` Kevin Hilman
2009-09-13 13:07 ` Mike Rapoport
2009-09-14 15:21 ` Kevin Hilman
2009-09-15 6:16 ` Mike Rapoport
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=4AA7C0D5.2070106@compulab.co.il \
--to=mike@compulab.co.il \
--cc=cliff.brake@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox