From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Govindraj.R" <govindraj.raja@ti.com>,
linux-omap@vger.kernel.org, Sergio Aguirre <saaguirre@ti.com>
Subject: Re: [pm-wip/uart][PATCH 2/4] OMAP3: serial: Fix uart4 handling for 3630
Date: Mon, 7 Jun 2010 13:06:57 +0300 [thread overview]
Message-ID: <20100607100656.GE15515@atomide.com> (raw)
In-Reply-To: <871vcmq08s.fsf@deeprootsystems.com>
* Kevin Hilman <khilman@deeprootsystems.com> [100604 18:30]:
>
> > + w &= ~0x7;
> > + w |= OMAP_MUX_MODE2;
> > + omap_ctrl_writew(w, uart->padconf);
Generic NAK for tinkering with the mux registers directly.
Instead, Govindraj, please add omap_mux_request_signal() into mux.c:
void __iomem * __init omap_mux_request_signal(char *muxname);
Which returns the address of the mux register in question based
on the signal name. Then in the platform init code you can request
the pins for all the UARTs in use, and provide functions to remux
them as needed for the idle modes.
This will work for omap2 also at some point once it's converted to
use the common mux framework. And it will work in a generic way
for all omaps under mach-omap2 eventually.
You can take a look at the omap_mux_get_gpio() in mux.c for a
similar example.
Regards,
Tony
next prev parent reply other threads:[~2010-06-07 10:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 13:43 [pm-wip/uart][PATCH 2/4] OMAP3: serial: Fix uart4 handling for 3630 Govindraj.R
2010-06-04 14:03 ` Gopinath, Thara
2010-06-04 14:08 ` Govindraj
2010-06-04 15:35 ` Kevin Hilman
2010-06-07 8:47 ` Govindraj
2010-06-07 10:06 ` Tony Lindgren [this message]
2010-06-07 11:32 ` Govindraj
2010-06-07 14:56 ` Govindraj
2010-06-09 14:28 ` Tony Lindgren
2010-06-10 8:54 ` Govindraj
2010-06-10 11:12 ` Tony Lindgren
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=20100607100656.GE15515@atomide.com \
--to=tony@atomide.com \
--cc=govindraj.raja@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.com \
/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;
as well as URLs for NNTP newsgroup(s).