> -----Original Message----- > From: Hilman, Kevin > Sent: Thursday, June 16, 2011 9:46 PM > To: DebBarma, Tarun Kanti > Cc: [email protected]; Shilimkar, Santosh; [email protected]; > [email protected] > Subject: Re: [PATCH v2 00/18] GPIO: OMAP: Driver Cleanup and Fixes > > Tarun Kanti DebBarma <[email protected]> writes: > > > This series is continuation of cleanup of OMAP GPIO driver and fixes. > > The cleanup include getting rid of cpu_is_* checks wherever possible, > > use of gpio_bank list instead of static array, use of unique platform > > specific value associated data member to OMAP platforms to avoid > > cpu_is_* checks. The series also include PM runtime support. > > A quick test of this series on 3430/n900 shows that it prevents PER > retention. I see CM_FCLKEN_PER=0000c000 (debounce clock for GPIO banks > 3 & 4 are still enabled.) > > Can you retest with debounce enabled on one of the GPIOs for one of your > platforms? Sure, I will. -- Tarun > > Kevin > >
-- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
