Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp3112536pxb; Sun, 31 Jan 2021 04:46:27 -0800 (PST) X-Google-Smtp-Source: ABdhPJzgCzDwJEiYMQRSTI4FF50Vzzt5Ef4z8TckXdmDS8WJ8auEvE+BvqeK4zPk6zMsa99QkR8w X-Received: by 2002:a17:907:961c:: with SMTP id gb28mr12547697ejc.393.1612097187480; Sun, 31 Jan 2021 04:46:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1612097187; cv=none; d=google.com; s=arc-20160816; b=YmyNkgfzCv8vxAoO0CRAWlNIwDNMZ/83puF1wvAIGyBl7VoJTcJ9p/xRLfiFu708TC Ta+46gEl6Qd1MMpYjdQF+XArH7rBgUwAp8PkNMuu8ZWS2N5+WN57dGLmmFTcyyTU2dBJ B7ZFklcgTcBSNfW9F8ijdMyuREpUeyJC/GRbcSaAV8xbKcEs6V7DcG0jr4aheRJsEErt zs1UH29bDv2NQBMO1s3Q2TCIAj6seDQfgWAiIkRcT/WZzkj2YFb4nycPnVmcQ16sZIwh fjCNV3kSuYgVmMJLpAHqh4WPHikiOpEGfLoBlrjGDEZD+Dm/IxogYF1YYuWRTweaQDFu sbpQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=HWCgx/8PoCOz2kzfaFNO4REAZvFPtXtD4t9gSeCBA1o=; b=OWafuOmNUMDTnOtajFZ4OkDZ79//MmrW51DBlK4i3tuTPBlmlDsTiNMRabspWRacn3 hqqtfCnpjCLsFTod5pBM1R1dlbmxSF+M5+MzzU4DkO3Kk+LvlX+6fI0t/5UtkBvcY0u0 /P2bxIv1EsAW+Por9s3i4AHpWhz+4RGYXUhrvgYdTjmDCbTKFt/cit/lXMt1DeBBL9uJ Aou/MyqJA9pUmsAp3V2+CkXrV7MxukTkvQ5rXvNg/4ga/Tf/tFKugRTWvQMQtHUaXG3R We2ME35wgxx1p+FJEMBSqCn8gKCL8xNMS9MZgakN5U2GIgkABuDzXQ6wRo1gpaSUwtBY oo6g== 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f27si9065086ejf.555.2021.01.31.04.46.03; Sun, 31 Jan 2021 04:46:27 -0800 (PST) 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231925AbhAaMOc (ORCPT + 99 others); Sun, 31 Jan 2021 07:14:32 -0500 Received: from mail.kernel.org ([198.145.29.99]:53230 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231518AbhAaLd5 (ORCPT ); Sun, 31 Jan 2021 06:33:57 -0500 Received: from archlinux (cpc108967-cmbg20-2-0-cust86.5-4.cable.virginm.net [81.101.6.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id CB71D64E1F; Sun, 31 Jan 2021 10:58:48 +0000 (UTC) Date: Sun, 31 Jan 2021 10:58:44 +0000 From: Jonathan Cameron To: Stephen Boyd Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org, Dmitry Torokhov , Benson Leung , Guenter Roeck , Douglas Anderson , Gwendal Grignou Subject: Re: [PATCH 3/3] iio: proximity: Add a ChromeOS EC MKBP proximity driver Message-ID: <20210131105844.2dfe9380@archlinux> In-Reply-To: <161159998973.76967.1213998704222248070@swboyd.mtv.corp.google.com> References: <20210122225443.186184-1-swboyd@chromium.org> <20210122225443.186184-4-swboyd@chromium.org> <20210124173820.4528b9c9@archlinux> <161159998973.76967.1213998704222248070@swboyd.mtv.corp.google.com> X-Mailer: Claws Mail 3.17.8 (GTK+ 2.24.33; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ... > > > + > > > +#ifdef CONFIG_OF > > > > As a general rule, we are trying to clear out protections on CONFIG_OF etc > > and use of of_match_ptr() on the basis they don't really gain us anything > > and prevent use of some other firmware types. Here I guess you know what > > your firmware looks like, but I'm still keen to drop it in the interests > > of there being fewer places to copy it from. > > > > It may be a good idea to give this a more specific name as well given > > we already have cros-ec-prox as a platform device id from > > the cros_ec_light_prox driver. > > Alright. I renamed it to cros_ec_mkbp_proximity throughout this driver. > I'm concerned about dropping CONFIG_OF because of_match_ptr() and > CONFIG_OF=n makes it unused but I suppose that will be OK as long as > compilation passes. It's a trivial overhead + note that it can be used by certain ACPI tables. Lookup the delights of PRP0001 which lets ACPI use device-tree descriptions. It may well be that no one uses that for this driver, but it's nice not to exclude it and that works with CONFIG_OF=n. Jonathan