From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 94420C433F5 for ; Mon, 28 Mar 2022 13:02:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238219AbiC1NEZ (ORCPT ); Mon, 28 Mar 2022 09:04:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40224 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232827AbiC1NEY (ORCPT ); Mon, 28 Mar 2022 09:04:24 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 0BBF25D18B for ; Mon, 28 Mar 2022 06:02:44 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 9AC4A60F28 for ; Mon, 28 Mar 2022 13:02:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7EDE6C340ED; Mon, 28 Mar 2022 13:02:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1648472563; bh=4BNd/nr5yAr1TLLYnFwVd4+nHk8Hao7pRJssMMM+m4w=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mTn53ivRLlkPXgMJzrcLMIOgTslPRAexnBeQM+cD029i+ZTMoY0Vj+INlMn1oKJKw N68zIGfkEJsfI0vob/Bgrp+pofhV/OSXc0xwHiPmHTa9PKnlz7VrYfRXF4u0zE/D0o 2IoV963zxtZTjXZ3jInWpnT3gd3SJZtaNZEPuVG8= Date: Mon, 28 Mar 2022 15:02:39 +0200 From: Greg Kroah-Hartman To: Jonathan Cameron Cc: Andrea Merello , Peter Meerwald-Stadler , linux-iio , Andrea Merello Subject: Re: [v3 07/13] iio: imu: add Bosch Sensortec BNO055 core driver Message-ID: References: <20220217162710.33615-1-andrea.merello@gmail.com> <20220217162710.33615-8-andrea.merello@gmail.com> <20220219174141.4937297a@jic23-huawei> <20220327171104.051fcbd2@jic23-huawei> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220327171104.051fcbd2@jic23-huawei> Precedence: bulk List-ID: X-Mailing-List: linux-iio@vger.kernel.org On Sun, Mar 27, 2022 at 05:11:04PM +0100, Jonathan Cameron wrote: > On Tue, 22 Mar 2022 11:27:14 +0100 > Andrea Merello wrote: > > > Il giorno sab 19 feb 2022 alle ore 18:34 Jonathan Cameron > > ha scritto: > > > > > > On Thu, 17 Feb 2022 22:58:14 +0100 (CET) > > > Peter Meerwald-Stadler wrote: > > > > > > > On Thu, 17 Feb 2022, Andrea Merello wrote: > > > > > > > > nice work, minor comments below > > > > > > I'll review on top of Peter to save on duplication. > > > > > > Mostly really minor stuff. > > +CC Greg for binary attribute questions. > > > > > :) > > > > As usual, comments inline; OK for all the rest. > > > > > Given this has crossed with the introduction of namespaces to quite > > > a few IIO drivers (I have another series to do on that once I get > > > caught up with reviews) I'd prefer it if you would move this into > > > a symbol namespace (EXPORT_SYMBOL_NS_GPL() and appropriate namespace > > > statements in the two bus modules. > > > > > > Save it being done as a follow up series. If you prefer not to then > > > that's fine too as it'll be a trivial follow up patch. > > > > I'll include it in V4 directly. > > > > [...] > > > > > > > + case IIO_CHAN_INFO_SCALE: > > > > > + /* Table 3-31: 1 quaternion = 2^14 LSB */ > > > > > + if (size < 2) > > > > > + return -EINVAL; > > > > > + vals[0] = 1; > > > > > + vals[1] = 1 << 14; > > > > > + return IIO_VAL_FRACTIONAL_LOG2; > > > > > > This doesn't look right. Not vals[1] = 14 given FRACTIONAL_LOG2? > > > > Hum.. maybe just IIO_VAL_FRACTIONAL ? > > That works as well, though I'd argue FRACTIONAL_LOG2 is the > better option as it makes it clear the divisor is a power of 2 > and the precision might potentially be better as a result (I've not > checked!) > > > > > > > > + default: > > > > > + return -EINVAL; > > > > > + } > > > > > +} > > > > > + > > > > [...] > > > > > > > +static IIO_DEVICE_ATTR_RO(sys_calibration_auto_status, 0); > > > > > +static IIO_DEVICE_ATTR_RO(in_accel_calibration_auto_status, 0); > > > > > +static IIO_DEVICE_ATTR_RO(in_gyro_calibration_auto_status, 0); > > > > > +static IIO_DEVICE_ATTR_RO(in_magn_calibration_auto_status, 0); > > > > > +static IIO_DEVICE_ATTR_RO(calibration_data, 0); > > > > > > This is documented as providing binary data but it's not using > > > a binary attribute and that rather surprised me. > > > > > > Off the top of my head I can't recall why it matters though, so please > > > take a look at whether a bin_attribute makes more sense for this. > > > > As far as I can see, it seems that a non-binary attributes only > > support to be read at once while the binary attributes read() > > operation supports random access i.e. it has the file position > > parameter. > > > > The calibration data is "dynamic", it's read from the HW every time, > > and I'm not sure it makes any sense to read it in several chunks (what > > if we read a chunk and the calibration data is updated by the HW > > before reading the second chunk?). So, despide the fitting "binary" > > name I'm tempted to stick with regular attribute. However I'm not sure > > this is the only difference related to binary attributes. > > +Cc Greg. Valid choice to use a normal attribute for this? binary attributes are to ONLY be used for data that flows to/from a device without the kernel ever modifying the data at all. The kerneln is just a pass-through here. There are a few minor exceptions, but they were exceptions, please don't use them as a valid reason to use a binary attribute. does that help? greg k-h