From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Date: Mon, 11 Apr 2016 11:44:59 +0300 From: Vlad Dogaru To: Akinobu Mita Cc: linux-iio@vger.kernel.org, Christoph Mair , Jonathan Cameron , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald Subject: Re: [PATCH] iio: pressure: bmp280: add support for BMP180 Message-ID: <20160411084459.GA31705@vdogaru> References: <1460044621-17274-1-git-send-email-akinobu.mita@gmail.com> <20160408104313.GA12944@vdogaru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: List-ID: On Sat, Apr 09, 2016 at 03:53:39AM +0900, Akinobu Mita wrote: > 2016-04-08 19:43 GMT+09:00 Vlad Dogaru : > > On Fri, Apr 08, 2016 at 12:57:01AM +0900, Akinobu Mita wrote: > [...] > >> +static int bmp180_chip_init(struct bmp280_data *data) > >> +{ > >> + return 0; > >> +} > > > > When setting the oversampling ratio, we do a lookup in the available > > values array, then call ops->init to write the values to the register. > > This function does nothing in the bmp180 case. Or am I missing > > something? > > Your understanding is correct. There is nothing to do for bmp180 when > the oversampling setting is changed by the user. When the actual > measurement is requested, the measurement conversion is started by > writing ctrl_meas register with the oversampling setting and start > conversion bit. Ah, I see. That makes sense, thanks for the explanation. Vlad