From mboxrd@z Thu Jan 1 00:00:00 1970 From: Courtney Cavin Subject: Re: [PATCH 01/05] input synaptics-rmi4: Split F01 definitions out into header file for use by reflash. Date: Mon, 10 Mar 2014 15:57:50 -0700 Message-ID: <20140310225750.GG18578@sonymobile.com> References: <1394245795-17347-1-git-send-email-cheiny@synaptics.com> <20140310144658.GB18578@sonymobile.com> <531E3DA2.5090705@synaptics.com> <20140310224550.GF18578@sonymobile.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Return-path: Received: from seldrel01.sonyericsson.com ([212.209.106.2]:7427 "EHLO seldrel01.sonyericsson.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752435AbaCJWz5 (ORCPT ); Mon, 10 Mar 2014 18:55:57 -0400 Content-Disposition: inline In-Reply-To: <20140310224550.GF18578@sonymobile.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Christopher Heiny Cc: Dmitry Torokhov , Linux Input , Andrew Duggan , Vincent Huang , Vivian Ly , Daniel Rosenberg , Linus Walleij , Benjamin Tissoires , David Herrmann , Jiri Kosina On Mon, Mar 10, 2014 at 11:45:50PM +0100, Courtney Cavin wrote: > On Mon, Mar 10, 2014 at 11:33:06PM +0100, Christopher Heiny wrote: > > On 03/10/2014 07:46 AM, Courtney Cavin wrote: > > > On Sat, Mar 08, 2014 at 03:29:51AM +0100, Christopher Heiny wrote: > > >> Signed-off-by: Christopher Heiny > > >> Cc: Dmitry Torokhov > > >> Cc: Benjamin Tissoires > > >> Cc: Linux Walleij > > >> Cc: David Herrmann > > >> Cc: Jiri Kosina > > >> > > >> --- > > >> > > >> drivers/input/rmi4/rmi_f01.c | 96 ++----------------------------------- > > >> drivers/input/rmi4/rmi_f01.h | 110 +++++++++++++++++++++++++++++++++++++++++++ > > >> 2 files changed, 114 insertions(+), 92 deletions(-) > [...] > > > > > > I might be missing something, but these seem like the only defines used > > > in the flash code. Why not keep these in the f01 driver, and export > > > a couple more functions, like rmi_f01_reset() and rmi_f01_set_sleep_mode() ? > > > > It seems better to me to have the information defined in a single place, > > rather than scattered hither and yon through the source files. > > Uh. Exactly? This is why I'm suggesting that you keep this information > isolated in the driver to which is directly related. > > Perhaps what you mean is that the regs/bits for the entire chip > functionality should be exposed in header files, so one can read/write > it from anywhere? That seems backwards to the idea of separating these > 'functions' out into drivers. Ah. Wait. I think there was some mis-communication on my part. What I should have said: Why not keep all of the defines in the driver, and export a couple more functions? My point is exactly yours. Keep the defines with the code. Expose what's needed. -Courtney