From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from www381.your-server.de ([78.46.137.84]:33860 "EHLO www381.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751401AbcDOOoq (ORCPT ); Fri, 15 Apr 2016 10:44:46 -0400 Subject: Re: generic_buffer and 24 bits samples To: Gregor Boirie , Crestez Dan Leonard , "linux-iio@vger.kernel.org" References: <570FB712.5070903@parrot.com> <570FBE87.9050006@metafoo.de> <5710BADC.3000000@intel.com> <5710C2E6.2080303@metafoo.de> <5710E746.1080102@intel.com> <20160415143525.GA4020@geburah.sephiroth> From: Lars-Peter Clausen Message-ID: <5710FE5A.1010300@metafoo.de> Date: Fri, 15 Apr 2016 16:44:42 +0200 MIME-Version: 1.0 In-Reply-To: <20160415143525.GA4020@geburah.sephiroth> Content-Type: text/plain; charset=utf-8 Sender: linux-iio-owner@vger.kernel.org List-Id: linux-iio@vger.kernel.org On 04/15/2016 04:35 PM, Gregor Boirie wrote: > On Fri, Apr 15, 2016 at 04:06:14PM +0300, Crestez Dan Leonard wrote: > [snip...] >> The only drivers that seem to use an unusual storagebits value are >> st_pressure (the one that this thread is about) and AD5791 which doesn't >> seem to actually expose buffer support. >> >> There is also the curious case of AD7303 which specifies realbits and >> storage bits as the char value '8', again without exposing buffer support. >> >> Perhaps storagebits=24 in st_pressure should be considered a bug. Maybe try >> to modify this to 32 and check the readings? > I'll take care of st_pressure since I'm currently working on a patch series. I > don't have AD7303 device however. I'll send a patch, but is non-critical as it does not have buffer support yet.