Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755798Ab2JWWKY (ORCPT ); Tue, 23 Oct 2012 18:10:24 -0400 Received: from us-mx3.synaptics.com ([12.239.217.85]:24350 "EHLO us-mx3.synaptics.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754530Ab2JWWKW (ORCPT ); Tue, 23 Oct 2012 18:10:22 -0400 Message-ID: <508715CC.1000600@synaptics.com> Date: Tue, 23 Oct 2012 15:10:20 -0700 From: Christopher Heiny Organization: Synaptics, Inc User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120827 Thunderbird/15.0 MIME-Version: 1.0 To: Mark Brown CC: Linus Walleij , Anton Vorontsov , Dmitry Torokhov , Jean Delvare , Linux Kernel , Linux Input , Allie Xiong , Vivian Ly , Daniel Rosenberg , Joerie de Gram , Wolfram Sang , Mathieu Poirier , Linus Walleij , Naveen Kumar Gaddipati , Alexandra Chin Subject: Re: [RFC PATCH 01/06] input/rmi4: Public header and documentation References: <1349496603-20775-1-git-send-email-cheiny@synaptics.com> <1349496603-20775-2-git-send-email-cheiny@synaptics.com> <20121009082719.GC8237@opensource.wolfsonmicro.com> <20121012051558.GK11726@opensource.wolfsonmicro.com> In-Reply-To: <20121012051558.GK11726@opensource.wolfsonmicro.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Brightmail-Tracker: AAAAAA== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1312 Lines: 35 On 10/11/2012 10:16 PM, Mark Brown wrote: > On Thu, Oct 11, 2012 at 03:56:22AM +0000, Christopher Heiny wrote: > > Fix your mailer to word wrap within paragraphs. Sorry - I was on the road and had to use a web interface. It looked OK during composition. Is this better? >> >If this feature is a deal-breaker, we can take it out. In the absence >> >of a generic GPIO implementation for CS, though, I'd much rather leave >> >it in. Once generic GPIO CS arrives, we'll remove it pretty quickly. > > Why not just implement this at an appropriate level in the SPI > subsystem? One of the great things about Linux is that you can change > the core code... At the moment, we're trying to keep our work focused on just the core RMI4 driver. It's evident that we've still got a bit to learn, and I'd be more comfortable keeping our learning experiences confined as they are now. However, a general capability in SPI core is a fine idea for future work, once we get the RMI4 driver ironed out. Can we agree to defer that for now? Thanks, Chris -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/