From: Tony Lindgren <tony@atomide.com>
To: Girish <girishsg@ti.com>
Cc: linux-omap@vger.kernel.org, linux-omap-open-source@linux.omap.com
Subject: Re: [Resending PATCH 2/2] ARM: OMAP2: rtc board specific code
Date: Wed, 5 Mar 2008 11:44:33 +0200 [thread overview]
Message-ID: <20080305094432.GB8106@atomide.com> (raw)
In-Reply-To: <028b01c85f0e$c9353f30$988818ac@ent.ti.com>
Hi Girish,
* Girish <girishsg@ti.com> [080125 06:57]:
>
>
> >-----Original Message-----
> >From: Tony Lindgren [mailto:tony@atomide.com]
>
> msecure/gpio-22 line
> >connected to T2 */
> >> + if (is_device_type_gp() &&
> >is_sil_rev_less_than(OMAP3430_REV_ES2_0)) {
> >> + u32 msecure_pad_config_reg = omap2_ctrl_base + 0xA3C;
> >> + int mux_mask = 0x04;
> >> + u16 tmp;
> >
> >Let's wait a bit on this one until we have the
> >omap_ctrl_read/write stuff merged, then update this patch for it.
>
> Yes, we can do that.
Could you please refresh your RTC patch now?
Tony
next parent reply other threads:[~2008-03-05 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080124223246.GH13765@atomide.com>
[not found] ` <028b01c85f0e$c9353f30$988818ac@ent.ti.com>
2008-03-05 9:44 ` Tony Lindgren [this message]
2008-03-12 6:12 ` [Resending PATCH 2/2] ARM: OMAP2: rtc board specific code Girish
2007-12-18 7:29 Girish
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=20080305094432.GB8106@atomide.com \
--to=tony@atomide.com \
--cc=girishsg@ti.com \
--cc=linux-omap-open-source@linux.omap.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