Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp1136493ybz; Sat, 25 Apr 2020 11:47:28 -0700 (PDT) X-Google-Smtp-Source: APiQypKfn1SOKLQcAzWavlCIpnKrwXfQz0kNHlmaE092jHIhYk2cFUC/mlO/+RDYYTJRKtBbVjKg X-Received: by 2002:a50:cd89:: with SMTP id p9mr12560083edi.188.1587840447910; Sat, 25 Apr 2020 11:47:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587840447; cv=none; d=google.com; s=arc-20160816; b=c0BcVzzsBN9ey1fBCL+imNRXAMahz7m/TR6hw+HZPJ50/6cbXLK2BKJfLGyWLAPNtI Vk7LSf8FIF/l8ITNwoGNNON6uwd6UdoTL8ubSguS2tDvdWZXV34Wa7FZ7+9VaI74sDGx cydIVNiGeW0wT/hxVLLG5Fgba3SiorWcF5MMuO/7YLG/HIl6i2mJW1ILpQaXQMGE6Yme bBrTT+JdPZ+9TVwkD3mY7MBtX0aiQ5vbocDr9ZAPLlKzgMZ/qOErNx59hRSmC1pdU1FY ffzwDpJWSZwyfquo42GQRsJXBNJKkojWKC8kh7R9eaCnYXLusa/rFuENoP1an9Og47zy Zo7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=N6ztXQxAFKypsi/nSBdztN1q6u1K4RR9vkmIhpLlC0c=; b=09fDs5FzkINz6V1ktl5g8bUzqmUIMP/pwcqln9E2lXjdQy6CXbPUS9IsLdutX1hggv przJjI039Cx+n8SZ6RkHrHi3G67e1DJ3tot4dElqw6f8PbamY1gZpm0oE2+VuNs10R/E rFvaJ3K15ZclPSuTDSFnUGEgccOTV2baMFRYBzBaMPjPNKg9TlWv3FCHhJpBTaKqST8+ PAPfmbL0Qt2qLGdoFhEDoDuEOoI9ZDtGmDF2bvwgL92SaPGDfQmgBEmG3W40AaXOvE7v dyXs4KOZiQ81keEdKB4jbSHuqoXis267kajrMQseki2aCjsjWfKxs2MF7rHYvNDty8SA qYhA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o16si5971255edz.569.2020.04.25.11.47.04; Sat, 25 Apr 2020 11:47:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726335AbgDYSm5 (ORCPT + 99 others); Sat, 25 Apr 2020 14:42:57 -0400 Received: from smtpout1.mo803.mail-out.ovh.net ([79.137.123.219]:47383 "EHLO smtpout1.mo803.mail-out.ovh.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726303AbgDYSm4 (ORCPT ); Sat, 25 Apr 2020 14:42:56 -0400 Received: from pro2.mail.ovh.net (unknown [10.108.4.220]) by mo803.mail-out.ovh.net (Postfix) with ESMTPS id C74854FAE313; Sat, 25 Apr 2020 20:42:53 +0200 (CEST) Received: from localhost (89.70.31.203) by DAG2EX1.emp2.local (172.16.2.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1847.3; Sat, 25 Apr 2020 20:42:53 +0200 Date: Sat, 25 Apr 2020 20:41:30 +0200 From: Tomasz Duszynski To: Andy Shevchenko CC: Tomasz Duszynski , linux-iio , Linux Kernel Mailing List , devicetree , Rob Herring , Jonathan Cameron Subject: Re: [PATCH 1/6] iio: chemical: scd30: add core driver Message-ID: <20200425184130.GA37271@arch> References: <20200422141135.86419-1-tomasz.duszynski@octakon.com> <20200422141135.86419-2-tomasz.duszynski@octakon.com> <20200424190413.GA2731@arch> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: X-Originating-IP: [89.70.31.203] X-ClientProxiedBy: DAG2EX1.emp2.local (172.16.2.11) To DAG2EX1.emp2.local (172.16.2.11) X-Ovh-Tracer-Id: 9560297584316538015 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrheeggddutdehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepfffhvffukfhfgggtuggjihesthdtredttddtjeenucfhrhhomhepvfhomhgrshiiucffuhhsiiihnhhskhhiuceothhomhgrshiirdguuhhsiiihnhhskhhisehotghtrghkohhnrdgtohhmqeenucffohhmrghinhepshgvnhhsihhrihhonhdrtghomhenucfkpheptddrtddrtddrtddpkeelrdejtddrfedurddvtdefnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpqdhouhhtpdhhvghlohepphhrohdvrdhmrghilhdrohhvhhdrnhgvthdpihhnvghtpedtrddtrddtrddtpdhmrghilhhfrhhomhepthhomhgrshiirdguuhhsiiihnhhskhhisehotghtrghkohhnrdgtohhmpdhrtghpthhtohepjhhitgdvfeeskhgvrhhnvghlrdhorhhg Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Apr 25, 2020 at 02:43:35PM +0300, Andy Shevchenko wrote: > On Fri, Apr 24, 2020 at 10:05 PM Tomasz Duszynski > wrote: > > On Wed, Apr 22, 2020 at 10:49:44PM +0300, Andy Shevchenko wrote: > > > On Wed, Apr 22, 2020 at 5:22 PM Tomasz Duszynski > > > wrote: > > ... > > > > > Add Sensirion SCD30 carbon dioxide core driver. > > > > > > And DocLink tar of Datasheet: with a link? > > > > I never do this. These files change their location way too often to be > > worthwhile putting here. Nobody has that much time to fallow all this > > and keep respective files up to date. > > > > But that doesn't mean I can't drop a link here. > > https://developer.sensirion.com/fileadmin/user_upload/customers/sensirion/Dokumente/9.5_CO2/Sensirion_CO2_Sensors_SCD30_Interface_Description.pdf > > Yes, just make it a tag > > DocLink: .... > > ... > > > > > +int scd30_probe(struct device *dev, int irq, const char *name, void *priv, > > > > + int (*command)(struct scd30_state *state, enum scd30_cmd cmd, > > > > + u16 arg, char *rsp, int size)); > > > > > > My gosh. > > > Please, supply proper structure member in priv or alike. > > > > Not sure it's worth the fuss. Wrapping all into structure means either > > copying respective members or more dereferences later on. > > At least you may introduce a typedef, because above really hurts my eyes. > May be. > ... > > > > > +enum { > > > > + CONC, > > > > + TEMP, > > > > + HR, > > > > +}; > > > > > > Way too generic names for anonymous enum. > > > > I'd argue that they are pretty well understood abbreviations in iio generally > > and here specifically. But adding some prefix won't harm. > > Yes, prefix is what I was talking about. > > ... > > > > > +static int scd30_wait_meas_poll(struct scd30_state *state) > > > > +{ > > > > + int tries = 5; > > > > + > > > > + while (tries--) { > > > > + int ret; > > > > + u16 val; > > > > + > > > > + ret = scd30_command(state, CMD_MEAS_READY, 0, (char *)&val, > > > > + sizeof(val)); > > > > + if (ret) > > > > + return -EIO; > > > > + > > > > + /* new measurement available */ > > > > + if (val) > > > > + break; > > > > + > > > > + msleep_interruptible(state->meas_interval * 250); > > > > + } > > > > + > > > > + if (tries == -1) > > > > + return -ETIMEDOUT; > > > > > > unsigned int tries = ...; > > > > > > do { > > > ... > > > } while (--tries); > > > if (!tries) > > > return ...; > > > > > > looks better and I guess less code in asm. > > > > > > > You mean that one extra branch in case of while? > > There are few things: > a) do {} while notation immediately tells that at least one cycle of > body will be done (unconditionally); > b) it makes a loop variable unsigned and no need to check for specific > negative numbers; > c) it quite likely will generate slightly better assembly code. > > > But it comes to code > > itself it looks more compact. And I am okay with that. > > > > > > + return 0; > > > > +} > > ... > > > > > + if (kstrtou16(buf, 0, &val)) > > > > + return -EINVAL; > > > > > > Shadowed error code. Don't do like this. > > > > Integer parsing either returns EINVAL or ERANGE. Passing the latter to > > the user is not worth the trouble, especially because majority of writable attrs > > have a fellow _available attr. > > It's simple a bad coding practice. Please, change. > Fair enough. > > > > + if (kstrtou16(buf, 0, &val)) > > > > + return -EINVAL; > > > > > > Ditto. > > > > > > > + if (kstrtou16(buf, 0, &val)) > > > > + return -EINVAL; > > > > > > Ditto. > > ... > > > > > + if (kstrtou16(buf, 0, &val)) > > > > + return -EINVAL; > > > > > > No shadowed error code, please. Check entire code. > > Same here. > > ... > > > > > +static IIO_DEVICE_ATTR_RW(pressure_comp, 0); > > > > +static IIO_DEVICE_ATTR_RO(pressure_comp_available, 0); > > > > +static IIO_DEVICE_ATTR_RW(meas_interval, 0); > > > > +static IIO_DEVICE_ATTR_RO(meas_interval_available, 0); > > > > +static IIO_DEVICE_ATTR_RW(asc, 0); > > > > +static IIO_DEVICE_ATTR_RW(frc, 0); > > > > +static IIO_DEVICE_ATTR_RO(frc_available, 0); > > > > +static IIO_DEVICE_ATTR_RW(temp_offset, 0); > > > > +static IIO_CONST_ATTR(temp_offset_available, "[0 1 65535]"); > > > > +static IIO_DEVICE_ATTR_WO(reset, 0); > > > > > > Do you need all of them? Doesn't IIO core provides a tons of helpers for these? > > > Btw, where is ABI documentation? It's a show stopper. > > > > They are sensor specific and none falls into a category of iio generic > > attrs. Maybe, except the measurement interval which could be represented as > > a SAMP_FREQ. > > IIO ABI becomes already a big pile of nodes and I hope we will become > stricter about adding new ones. > Try persuading vendors to use unified interfaces and problem will disappear completely :). > > But given that measurement interval spans from 2s to 1800s > > it becomes a little bit awkward to have it in Hz. > > > As for ABI that's in > > a separate patch. > > It's not good from bisectability point of view. If by some reason this > patch or documentation patch gets reverted, the other one will be > dangling. > Please, unify them. > Huh? Reverting core and leaving leftovers would be wrong and pointless. > -- > With Best Regards, > Andy Shevchenko