From: Govindraj <govindraj.ti@gmail.com>
To: "Gopinath, Thara" <thara@ti.com>
Cc: "Raja, Govindraj" <govindraj.raja@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>,
"Aguirre, Sergio" <saaguirre@ti.com>
Subject: Re: [pm-wip/uart][PATCH 2/4] OMAP3: serial: Fix uart4 handling for 3630
Date: Fri, 4 Jun 2010 19:38:56 +0530 [thread overview]
Message-ID: <AANLkTimRBs4cpfIyUMMMeU7xIFjhOK4I8W66RSk3oip4@mail.gmail.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB03232DA919@dbde02.ent.ti.com>
On Fri, Jun 4, 2010 at 7:33 PM, Gopinath, Thara <thara@ti.com> wrote:
>
>
>>>-----Original Message-----
>>>From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of
>>>Govindraj.R
>>>Sent: Friday, June 04, 2010 7:14 PM
>>>To: linux-omap@vger.kernel.org
>>>Cc: Kevin Hilman; Aguirre, Sergio
>>>Subject: [pm-wip/uart][PATCH 2/4] OMAP3: serial: Fix uart4 handling for 3630
>>>
>>>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 rx line.
>>>
>>>Cc: Kevin Hilman <khilman@deeprootsystems.com>
>>>Signed-off-by: Sergio Aguirre <saaguirre@ti.com>
>>>Signed-off-by: Govindraj.R <govindraj.raja@ti.com>
>>>---
>>> arch/arm/mach-omap2/serial.c | 30 +++++++++++++++++++++++++++++-
>>> 1 files changed, 29 insertions(+), 1 deletions(-)
>>>
>>>diff --git a/arch/arm/mach-omap2/serial.c b/arch/arm/mach-omap2/serial.c
>>>index da9fee6..70a9089 100644
>>>--- a/arch/arm/mach-omap2/serial.c
>>>+++ b/arch/arm/mach-omap2/serial.c
>>>@@ -42,6 +42,7 @@
>>> #include "prm.h"
>>> #include "pm.h"
>>> #include "cm.h"
>>>+#include "mux.h"
>>> #include "prm-regbits-34xx.h"
>>>
>>> #define UART_OMAP_NO_EMPTY_FIFO_READ_IP_REV 0x52
>>>@@ -68,6 +69,7 @@ struct omap_uart_state {
>>> u32 wk_mask;
>>> u32 padconf;
>>> u32 dma_enabled;
>>>+ u16 muxmode;
>>>
>>> struct clk *ick;
>>> struct clk *fck;
>>>@@ -229,8 +231,20 @@ static inline void omap_uart_disable_clocks(struct omap_uart_state *uart)
>>> omap_device_idle(uart->pdev);
>>> }
>>>
>>>+static inline void omap_uart_setmux_mode(struct omap_uart_state *uart)
>>>+{
>>>+ u16 w = omap_ctrl_readw(uart->padconf);
>>>+ w &= ~0x7;
>>>+ w |= OMAP_MUX_MODE2;
>
> Why it is hard coded to MUX_MODE2? Should it not be w |= uart->muxmode?
>
> Regards
> Thara
Yes correct it should been w |= uart->muxmode.
---
Regards,
Govindraj.R
--
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
next prev parent reply other threads:[~2010-06-04 14:16 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 [this message]
2010-06-04 15:35 ` Kevin Hilman
2010-06-07 8:47 ` Govindraj
2010-06-07 10:06 ` Tony Lindgren
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=AANLkTimRBs4cpfIyUMMMeU7xIFjhOK4I8W66RSk3oip4@mail.gmail.com \
--to=govindraj.ti@gmail.com \
--cc=govindraj.raja@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.com \
--cc=thara@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).