Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp730238imd; Sat, 3 Nov 2018 09:06:24 -0700 (PDT) X-Google-Smtp-Source: AJdET5cwwTU4xsOiEip8Gx9ZGEoLSeInhN0e9Ov3DUW83BXWDOdzIvZhYwhHOsOxSqiO+rumRXKr X-Received: by 2002:a62:714a:: with SMTP id m71-v6mr9316972pfc.89.1541261184786; Sat, 03 Nov 2018 09:06:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1541261184; cv=none; d=google.com; s=arc-20160816; b=WRytOIQdCguZ5NIwfvsYfxxi6vC5QbaF1e8mKS/k/eOD+g24oHFD2uijGWrhgJhCrZ z3aQYKo883uPdIB+B1mp4mgg5mPGol/XUNa4dsIoujL56OXa/XGgMLSS/dY8aV+QUefn WhiIGstIHEjAIi/naeR5z1qRhYnN3UmUSAZuBDMcUo13jUqVx7mPF5e+DTw3chsp5GIg 0zfFP09JyEYlXt5WqARcObIA4tsMdpFe0uooUMSA1GQKS0arvAMXXzi+O7GpqfIyQgPm teke0QCK0KieFfmKi7qhUNEnZxuLkQLJSgG05u9CdVUL1s0YS+xlS0dSRNppqUYCnGJ2 dOCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=51G9oFDcHMm10eDoLdhzF0sRCk3eyUQ9x1B4Tndyvnc=; b=sLYrQOSUHKGUowq3YiiBom+rx98HemmjM++jSYTVFT7Gqdhx0kYBf5Lq6ykeEyE1L4 H+YdrQzIkACw4RKocwmCZOMFsTUMlU0sVI0sM61LiQASHW6SlT3XgmLrE4kf8J1gjwGM q+mAWlxFE+EaaUKtOgWNL8PLc+3w4xISwRgRANjrulV3LMikWO3lRKHBfVqKnx5lX+TA 2E07Ly9gUgHBim7Shj+8NemNmTYeY07jNI/jpUiisHAg+9mBFUkQ1xwByJTA7ZuuwsrP hpvvsyMcZ9WGO5aaUmAFaNt4C04huJ87T5DukngNyKhxeOjfPONO/FTZH8/841cPinQm JQvg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@usp-br.20150623.gappssmtp.com header.s=20150623 header.b=EA8rg6WY; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=usp.br Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f10-v6si35778823pgs.362.2018.11.03.09.06.09; Sat, 03 Nov 2018 09:06:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@usp-br.20150623.gappssmtp.com header.s=20150623 header.b=EA8rg6WY; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=usp.br Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728641AbeKDBP7 (ORCPT + 99 others); Sat, 3 Nov 2018 21:15:59 -0400 Received: from mail-it1-f196.google.com ([209.85.166.196]:52667 "EHLO mail-it1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728334AbeKDBP6 (ORCPT ); Sat, 3 Nov 2018 21:15:58 -0400 Received: by mail-it1-f196.google.com with SMTP id t190-v6so1478492itb.2 for ; Sat, 03 Nov 2018 09:04:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=usp-br.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=51G9oFDcHMm10eDoLdhzF0sRCk3eyUQ9x1B4Tndyvnc=; b=EA8rg6WYuRgGY7GqGEx3MEcALoicLoHvjH6LX27WaxkhwW+wnqFjblWzviHX5yNCZR c8wLvCVjvUEdio0D7aPSl0FmXst/bLcmWoTj57Tr/aTwbLXKUhdhlZiIPLaLCyZSmdXU SPSETRUoJ0YtiRVFlXHngqPfnrjmNREIWw2KKBg3vsxQWdPz3582j5LU0Ee3G9kYhwHF H+bx0jD5sp9+07hFPqLk7ousZYkll3iwcjgSIH6r6Lzociu1ELiaGTCuqsyABxdStrx3 u0DF07ZdFseoJTWzx5XvdXafge9S4nCm1/wU+hwTaKjCKETbgfsePkhKugbA+/wqXHWa j3gw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=51G9oFDcHMm10eDoLdhzF0sRCk3eyUQ9x1B4Tndyvnc=; b=uYIStAwRwECEfY/0tGiaWAlj+3SKTA+udGFIf9/xlfL0VqkUMnzNfhgdpuz144ToZu Wi6xF4ewtRUHtTQF0lq2uJQxrHkUjFfJ5e1BPntDcQMRWoYZ06bUtfHtNu11xYJimRnv CLAsDuhraILyk+zBCIcQbwrGAR6bEX8UtYtCifBpY41uyELSwVtWjyrozBFoCgaX7Yxk S7HlS+gIOMeFCZlxR1MJ/EUg8I9sPefH4to+OC0YIbCRyLAZf5QdYTm+VXdP64mWJIgo qI/Ef1GNCP8wto+6IR1JukU386zkt77hlGPsfCN9F/EbIMVpGhtK02C7vy0kH0P/Kdqy 9dXg== X-Gm-Message-State: AGRZ1gL26bEdOXAH8IeBPHSoeeI48gi2gLgIX6jnUblOEiYL21GgtJwD PME4O+BKr0TfUe+RIIUs6G7WalKGSO6vJBFcIE/1SQ== X-Received: by 2002:a24:338e:: with SMTP id k136-v6mr1198223itk.86.1541261055867; Sat, 03 Nov 2018 09:04:15 -0700 (PDT) MIME-Version: 1.0 References: <20181027020005.3140-1-matheus.bernardino@usp.br> <20181027020005.3140-6-matheus.bernardino@usp.br> <20181028165040.27c69fc5@archlinux> In-Reply-To: <20181028165040.27c69fc5@archlinux> From: Matheus Tavares Bernardino Date: Sat, 3 Nov 2018 13:04:04 -0300 Message-ID: Subject: Re: [PATCH v2 5/6] staging:iio:ad2s90: Add IIO_CHAN_INFO_SCALE to channel spec and read_raw To: Jonathan Cameron Cc: Lars-Peter Clausen , Michael Hennerich , Hartmut Knaack , Peter Meerwald-Stadler , Greg Kroah-Hartman , linux-iio@vger.kernel.org, devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, kernel-usp@googlegroups.com, Victor Colombo Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Oct 28, 2018 at 1:50 PM Jonathan Cameron wrote: > > On Fri, 26 Oct 2018 23:00:04 -0300 > Matheus Tavares wrote: > > > This patch adds the IIO_CHAN_INFO_SCALE mask to ad2s90_chan and > > implements the relative read behavior at ad2s90_read_raw. > > > > Signed-off-by: Victor Colombo > > Signed-off-by: Matheus Tavares > > Hi, > > A suggestion inline. This is a common case that we have infrastructure > to simplify. + I think your scale factor is very slightly wrong. > > Jonathan > > > --- > > drivers/staging/iio/resolver/ad2s90.c | 32 ++++++++++++++++++--------- > > 1 file changed, 22 insertions(+), 10 deletions(-) > > > > diff --git a/drivers/staging/iio/resolver/ad2s90.c b/drivers/staging/iio/resolver/ad2s90.c > > index b4a6a89c11b0..52b656875ed1 100644 > > --- a/drivers/staging/iio/resolver/ad2s90.c > > +++ b/drivers/staging/iio/resolver/ad2s90.c > > @@ -34,19 +34,31 @@ static int ad2s90_read_raw(struct iio_dev *indio_dev, > > int ret; > > struct ad2s90_state *st = iio_priv(indio_dev); > > > > - mutex_lock(&st->lock); > > + switch (m) { > > + case IIO_CHAN_INFO_SCALE: > > + /* 2 * Pi / (2^12 - 1) ~= 0.001534355 */ > > + *val = 0; > > + *val2 = 1534355; > Definitely 2^12 - 1? That's a bit unusual if true as it would imply > that 2^12 - 1 and 0 were the same value. > > Imagine a smaller version with on 2^2 bits so 0, 1, 2, 3 > Values of each are > > 0, M_PI/2, M_PI, 3*M_PI/2 > > So the multiplier is 2*M_PI/(2^2) not 2*M_PI/(2^2 - 1) > 1/2 vs 2/3 * M_PI Oh, that makes a lot of sense! We used 2^12 - 1 here based on driver drivers/iio/resolver/ad2s1200.c, whose resolution is also 12 bits, as the ad2s90.c. Do you think this section is, perhaps, wrong on ad2s1200.c too, or maybe there is some difference between these two drivers that I didn't catch regarding the resolution? Matheus. > Now this is a very common case so we have the return type > IIO_VAL_FRACTIONAL_LOG2 to give a more obvious and potentially > more accurate representation. > > > + return IIO_VAL_INT_PLUS_NANO; > > + case IIO_CHAN_INFO_RAW: > > + mutex_lock(&st->lock); > > + > > + ret = spi_read(st->sdev, st->rx, 2); > > + if (ret < 0) { > > + mutex_unlock(&st->lock); > > + return ret; > > + } > > + > > + *val = (((u16)(st->rx[0])) << 4) | ((st->rx[1] & 0xF0) >> 4); > > > > - ret = spi_read(st->sdev, st->rx, 2); > > - if (ret < 0) { > > mutex_unlock(&st->lock); > > - return ret; > > - } > > > > - *val = (((u16)(st->rx[0])) << 4) | ((st->rx[1] & 0xF0) >> 4); > > - > > - mutex_unlock(&st->lock); > > + return IIO_VAL_INT; > > + default: > > + break; > > + } > > > > - return IIO_VAL_INT; > > + return -EINVAL; > > } > > > > static const struct iio_info ad2s90_info = { > > @@ -57,7 +69,7 @@ static const struct iio_chan_spec ad2s90_chan = { > > .type = IIO_ANGL, > > .indexed = 1, > > .channel = 0, > > - .info_mask_separate = BIT(IIO_CHAN_INFO_RAW), > > + .info_mask_separate = BIT(IIO_CHAN_INFO_RAW) | BIT(IIO_CHAN_INFO_SCALE), > > }; > > > > static int ad2s90_probe(struct spi_device *spi) >