From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Subject: Re: TSC2101/2102 Date: Wed, 14 Mar 2007 08:21:24 -0500 Message-ID: <45F7F6D4.20203@gmail.com> References: <20070309140650.GC4399@bitbox.mine.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-omap-open-source-bounces+gplao-linux-omap-open-source=gmane.org@linux.omap.com Errors-To: linux-omap-open-source-bounces+gplao-linux-omap-open-source=gmane.org@linux.omap.com To: balrogg@gmail.com Cc: Linux OMAP ML List-Id: linux-omap@vger.kernel.org andrzej zaborowski stated on 3/9/2007 8:23 AM: > On 09/03/07, Imre Deak wrote: >> I'm wondering about the proper way to convert the existing omap-tsc2101 >> driver to the SPI framework. Would it make sense to handle it with the >> tsc2102 driver? omap-tsc2101 has only the register read / write >> interface >> which is the same as in tsc2102. > > How about maybe a header file shared between > tsc2101/2102 with the register access functions as "static inline" > functions? Some TODOs: 1. should interrupt muxing be done here? 2. There are some TSC2005 devices(TS only).. so it will be interesting to see xxxx.h scales to all.. 3. rename this to tsc2xxx_core.[ch] 4. use SPI framework (would not break uwire support I believe). Regards, Nishanth Menon