Hello Ben, Samu, On Fri, 3 Dec 2010, [email protected] wrote:
> >-----Original Message----- > >From: ext Ben Dooks [mailto:[email protected]] > >Sent: 03 December, 2010 04:38 > >To: Onkalo Samu.P (Nokia-MS/Tampere) > >Cc: [email protected]; [email protected]; > >[email protected]; [email protected]; [email protected] > >Subject: Re: [PATCH] i2c-omap: Set latency requirements only once for > >several messages > > > >On Thu, Nov 18, 2010 at 12:04:20PM +0200, Samu Onkalo wrote: > >> Ordinary I2C read consist of two messages. First a write operation > >> to tell register address and then read operation to get data. > >> CPU wake up latency is set and removed twice in read case. > >> Set latency requirement before the message processing loop > >> and remove the requirement after the loop to remove latency > >> adjustment operations between the messages. > >> > >> Signed-off-by: Samu Onkalo <[email protected]> > >> Acked-by: Kevin Hilman <[email protected]> > >> Acked-by: Paul Walmsley <[email protected]> > > > >I'll queue this for -rc unless it is going in via the omap list > >or it should wait for merge window? > > > > I first sent this to omap-list and I got instructions to send this to you. > So I assume that you should queue this. Kevin, Paul, is -rc ok for you? I'd suggest that this go in through Ben, and go in as part of the 2.6.38 merge window, rather than the .37-rc. The patch doesn't fix any regressions introduced in the 2.6.37 merge window, and there's no impact on system stability, as far as I know. - Paul -- 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
