From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [RFC 1/2] ARM: OMAP2+: AM33XX: I2C Sleep/wake sequence support Date: Wed, 1 May 2013 16:54:08 -0700 Message-ID: <20130501235407.GO28721@atomide.com> References: <1367434947-6442-1-git-send-email-Russ.Dill@ti.com> <1367434947-6442-2-git-send-email-Russ.Dill@ti.com> <20130501232649.GN28721@atomide.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mho-02-ewr.mailhop.org ([204.13.248.72]:61195 "EHLO mho-02-ewr.mailhop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755527Ab3EAXyM (ORCPT ); Wed, 1 May 2013 19:54:12 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: Russ Dill Cc: Kevin Hilman , "linux-omap@vger.kernel.org" , Santosh Shilimkar , Vaibhav Bedia , Linux ARM Kernel List * Russ Dill [130501 16:43]: > On Wed, May 1, 2013 at 4:26 PM, Tony Lindgren wrote: > > > > Looks like you should make that into just a regular device driver that lives > > under drivers/ somewhere? > > This code has to be copied to, and run from SRAM. What would that even > look like? Additionally, there is also code under drivers/ that > manages this piece of hardware, i2c-omap.c. The code in this patch > differs in that it accesses no system memory, no stack, only knows how > to write, and it runs without interrupts. Well we should move to using the generic drivers/misc/sram.c, so you should be able to load the code to SRAM using that. Then you can probably register some callback function based on the compatible flag with i2c-omap.c? Regards, Tony