public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Govindraj.R" <govindraj.raja@ti.com>
Cc: linux-omap@vger.kernel.org, Sergio Aguirre <saaguirre@ti.com>
Subject: Re: [pm-wip/uart][PATCH 3/5 v2] OMAP3: serial: Fix uart4 handling for  3630
Date: Thu, 17 Jun 2010 14:45:55 -0700	[thread overview]
Message-ID: <87typ1jpt8.fsf@deeprootsystems.com> (raw)
In-Reply-To: <2232.10.24.255.18.1276697648.squirrel@dbdmail.itg.ti.com> (Govindraj R.'s message of "Wed\, 16 Jun 2010 19\:44\:08 +0530 \(IST\)")

"Govindraj.R" <govindraj.raja@ti.com> writes:

> This patch makes the following:
>  - Adds missing wakeup padding register handling.
>  - Fixes a hardcode to use PER module ONLY on UART3.
>  - Muxmode usage needed for uart4 for 3630, for padconf
>    wakeup on uart4_rx line. uart4_rx signal is available
>    under mode-2 in gpmc_wait3. Thus have to ensure we are
>    in right mux mode before accesing any padconf register.
>    So ensure right mux mode for uarti padconf access.

I think this mux-mode handling should be done as a separate patch with
more description as exactly what problem this is solving.

Presumably, whatever problem you're solving not unique to 3630 UART4
as the UARTs on the other platforms can be muxed with other
peripherals as well.

Based on the way it's being mux'd (and continually re-mux'd) in this
patch, it looks like the mux settings for that pin are being
dynamically changed elsewhere in the code.  If that's the case, then
that should be better understood, and this code should likely re-mux
to the original settings when its done.

Kevin

  reply	other threads:[~2010-06-17 21:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-16 14:14 [pm-wip/uart][PATCH 3/5 v2] OMAP3: serial: Fix uart4 handling for 3630 Govindraj.R
2010-06-17 21:45 ` Kevin Hilman [this message]
2010-06-22 14:55   ` Govindraj
2010-06-22 15:22     ` Kevin Hilman

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=87typ1jpt8.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=govindraj.raja@ti.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