From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751871AbcDSGFl (ORCPT ); Tue, 19 Apr 2016 02:05:41 -0400 Received: from mx07-00178001.pphosted.com ([62.209.51.94]:29403 "EHLO mx07-00178001.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751479AbcDSGFj (ORCPT ); Tue, 19 Apr 2016 02:05:39 -0400 Date: Tue, 19 Apr 2016 14:05:10 +0800 From: Denis Ciocca To: Lucas De Marchi CC: Jonathan Cameron , Crestez Dan Leonard , "linux-iio@vger.kernel.org" , Giuseppe BARBA , "linux-kernel@vger.kernel.org" , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler , Daniel Baluta , Peter Rosin , Wolfram Sang Subject: Re: [RFC] iio: st: Add lsm9ds0 support for gyro accel and magn Message-ID: <20160419060510.GB9712@beicxl1122> References: <2bcce23e64d53f542a9436b11509b107d63cb8dc.1460573498.git.leonard.crestez@intel.com> <57137732.40507@kernel.org> <20160418060742.GA2981@beicxl1122> <5714B609.4020502@intel.com> <57153AC3.9020603@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2016-04-19_05:,, signatures=0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Lucas, yup. Just need to add the lsm9ds0_gyro entry in the same table of l3gd20. Thanks, Denis On |19 Apr 16 @ 07:10|, Lucas De Marchi wrote: > On Mon, Apr 18, 2016 at 4:51 PM, Jonathan Cameron wrote: > > On 18/04/16 11:25, Crestez Dan Leonard wrote: > >> On 04/18/2016 09:07 AM, Denis Ciocca wrote: > >> Then st_combo_* implementation functions would forward to st_magn_* or > >> st_accel_* depending on chan->type. Does this make sense? > > Perhaps. If you have a short term need for this perhaps Denis and you can > > work together to speed up what he has 'in the works' for this? > > No point in duplicating work! > > > > The gyro element can go forward separately in the meantime. > > Isn't LSM9DS0 just a package of LSM303D and L3GD20 that could reuse > the drivers already present? > > > Lucas De Marchi