From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eva Rachel Retuya Subject: Re: [PATCH v3 4/4] iio: accel: adxl345: Add SPI support Date: Fri, 24 Feb 2017 17:12:33 +0800 Message-ID: <20170224091231.GC5012@Socrates-UM> References: <515297e48abd139993cab56dbf980711400d6534.1487757223.git.eraretuya@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Andy Shevchenko Cc: Lars-Peter Clausen , Jonathan Cameron , linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Hartmut Knaack , Peter Meerwald , Dmitry Torokhov , Michael Hennerich , Daniel Baluta , Alison Schofield , Florian Vaussard , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Rob Herring , Mark Rutland , devicetree List-Id: devicetree@vger.kernel.org On Thu, Feb 23, 2017 at 06:58:12PM +0200, Andy Shevchenko wrote: > On Thu, Feb 23, 2017 at 6:47 PM, Lars-Peter Clausen wrote: > > On 02/23/2017 05:43 PM, Andy Shevchenko wrote: > >> On Wed, Feb 22, 2017 at 12:23 PM, Eva Rachel Retuya wrote: > >>> Add SPI driver that initializes SPI regmap for the adxl345 core driver. > >>> The driver supports the same functionality as I2C namely the x, y, z and > >>> scale readings. > > >>> config ADXL345_I2C > >>> tristate > >>> select REGMAP_I2C > >>> > >>> +config ADXL345_SPI > >>> + tristate > >>> + select REGMAP_SPI > >> > >> Hmm... > >> I saw another pattern > >> > >> Library / core part is non-visible to user, while > >> SPI and I2C parts are selectable by user. > >> > >> Why do you use inverted pattern? What did I miss? > > > > The first version of the patch used the other pattern SPI/I2C visible. > > Jonathan suggested this other pattern. I prefer the explicit SPI/I2C visible > > pattern, but in the end it doesn't really matter as long as both work. > > Yes, but this pattern makes extra footprint of the kernel and > basically dead code when I would like, for example, to have SPI bus > enabled, I2C module available, but SPI module not compiled. > > Other one is when I want to have one compiled in, one as a module by > whatever reason. > > At the end I have no strong opinion, though rationale for the opposite is above. > Hello Lars and Andy, I'll revert to the explicit SPI/I2C pattern in order to give more freedom in configuring as per the scenarios previously stated. Thanks, Eva > -- > With Best Regards, > Andy Shevchenko -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html