RE: [PATCH]OMAP3:PM :T2 keypad wakeup for OMAP3

From: "Premi, Sanjeev" <premi@ti.com>
To: "Premi, Sanjeev" <premi@ti.com>,
	Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Reddy, Teerth" <teerth@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [PATCH]OMAP3:PM :T2 keypad wakeup for OMAP3
Date: Fri, 6 Nov 2009 19:42:10 +0530	[thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB59301DE31FB3B@dbde02.ent.ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301DE280371@dbde02.ent.ti.com>

> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org 
> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Premi, Sanjeev
> Sent: Wednesday, November 04, 2009 7:32 PM
> To: Kevin Hilman
> Cc: Reddy, Teerth; linux-omap@vger.kernel.org
> Subject: RE: [PATCH]OMAP3:PM :T2 keypad wakeup for OMAP3

[snip] --- [snip]

> > > Teerth, Kevin,
> > >
> > > Did you test it with OFF mode enabled?
> > 
> > I tested on SDP, but not on omap3evm since that was the only board
> > file touched by this patch.
> > 
> > > When I do "echo 1 > /sys/power/enable_off_mode" I don't see 
> > resume on the omap3evm.
> > >
> > > Schematics for the keypad are/seem to be same for EVM and SDP.
> > 
> > I'm guessing that it's because the patch from Teerth only muxes this
> > pin for the SDP.  I'm guessing that doing the same 
> omap_cfg_reg in the
> > OMAP3EVM board file will get this working.
> > 
> > Kevin
> > 
> 
> Kevin,
> 
> I have done the corresponding changes. See:
>  1) http://marc.info/?l=linux-omap&m=125725494430834&w=2
>  2) http://marc.info/?l=linux-omap&m=125725495630852&w=2
>  3) http://marc.info/?l=linux-omap&m=125725498430876&w=2
> 
> If I do suspend with OFF mode enabled (enable_off_mode=1), and
> all power domains transition to target state, the key press
> doesn't resume the system.
> 
> But, with this flag off OR any power domain didn't transition to
> the target state. The key press brings system out of 'suspend'.
> 

Can someone with a 3430SDP or ZOOM board try this scenario?

I am trying to understand if it is a generic problem OR specific
to the omap3evm.

Best regards,
Sanjeev