Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1784509pxk; Sun, 13 Sep 2020 16:28:54 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyAVzmPP9kEtaoWy0LnqGar4qj7vteAQDgnaWch1swAH7t8CkPOb5MRYbAMItUd588GmxI0 X-Received: by 2002:a17:906:7cc6:: with SMTP id h6mr12015190ejp.266.1600039733820; Sun, 13 Sep 2020 16:28:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600039733; cv=none; d=google.com; s=arc-20160816; b=Wz/GB3xlGokCZXg2uT8GkuMHO11dTZLFO2WXCDWGgYdYBKtm0xF5ksFiuIOOAkxNSv 0RpAr0FqKo5XDjQIHwb2/PPdznIrXsuVNoQfPxRvxz6GG6wdTMfWmYRjQEsiT0aCU0+z IHH7yvYelF/m3QkxS9oXOBH/txxmJ0jWF23JRY5AG4tItWaKh5PO2V+qkNd43RafKzzC zFjMh057HtmR7hulIQy+QEg0kCK5F/QWAVghJMtaPSVzIzDMWVNKAb8P483b66P0hfyA PcdSccRPVHEt8WFxnT2A02E3MnbclxsOd1eOgnXI2f7QWynBdZGA4jvzd2DRjyeH1cTV 4EtA== 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 :dkim-signature; bh=7v1NPAzkydR89JgSgtMekj7yJTyNSI10q1eiI/1zrxo=; b=AkvONl97d07/QJAMDJS3z23lPWIyu7ZOMwnOSqP4bAL4yeUd4ZOuZbuim5aJIsw2wu pa8af/VXcPP45+Nvr2dTNvmlnGIl5dcFaahlvaUMwZsI/hqeQQfGmrhi6rW4jJHHonk4 dfD2ZBjIWGITxfda7FguGtwfr/PqM4R4Xb9TXXa0mitxq0yZByHMxeQCu0VmL0yQ+54T R/10PPx4i/flcvMtfq9tWvujTUAGGwKqY383sq/iLyWgapb+Bf3IjE0DhKRNQCjhN0jz zYQzuViP/0wASmmWantbZ4PK2C6/iN+4S8VRNHy3PMirHcQbnDHuKGE25N4mePtjOZSq tQaw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@beagleboard-org.20150623.gappssmtp.com header.s=20150623 header.b=LbtnCqyg; 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 dd3si5670635ejb.499.2020.09.13.16.28.28; Sun, 13 Sep 2020 16:28:53 -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; dkim=pass header.i=@beagleboard-org.20150623.gappssmtp.com header.s=20150623 header.b=LbtnCqyg; 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 S1725975AbgIMX1Z (ORCPT + 99 others); Sun, 13 Sep 2020 19:27:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40236 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725962AbgIMX1X (ORCPT ); Sun, 13 Sep 2020 19:27:23 -0400 Received: from mail-ej1-x644.google.com (mail-ej1-x644.google.com [IPv6:2a00:1450:4864:20::644]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8EFDEC061788 for ; Sun, 13 Sep 2020 16:27:20 -0700 (PDT) Received: by mail-ej1-x644.google.com with SMTP id z23so20568897ejr.13 for ; Sun, 13 Sep 2020 16:27:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beagleboard-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=7v1NPAzkydR89JgSgtMekj7yJTyNSI10q1eiI/1zrxo=; b=LbtnCqygM/AuEhSdhgY7FRI2gjpUMcxbHXdfb0uHIYeZA9t2vwKhMboyANhMt+5f67 qvP9iZ5nFKResiZfOg14T1PJKOFCcBkJeb8i5gSc/PUsuz13KLo38haND0jXqkp/Kj0d 5EEIUQFMlCLklphxKJd3PNUc+J4+66ohkvBfI99e+gc1lMr6ORQj4FIclvYNdUrbCop5 5OIayk+vT1zzsgy0UtOTUKxkO7YDVNuZ5Wr7r/uRY60Fp+9CTZz5Kum22fzHgASJk4U4 Kws1Gz4Y06JJzEouM/B/ntLM7vGqqU73D085Uw+j+V7ThIfmhlec9Y6j21mNBB7hnUzG I6wQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=7v1NPAzkydR89JgSgtMekj7yJTyNSI10q1eiI/1zrxo=; b=A82SWvvScKBxBtVDUmXd0M0AldNoLTKhpdksGUQtv3wrX7M+43JbfQ1GvX+XClZWUL VOq2kvkJTctImRlqIkyDIvSCCJ7JAiuU3M9EKIsAb5OcRMxMVfPiTWriRZ698shBy2PK eY9FNlZIJekdnyzTYKQ2OrvGuUxA1PvZD1kGQ9B+z/ijDj2Jzd91dwWGMz2K7BqbN6oh TdXV1rderviQjoZ2aIPppTbVExdOuZZbZxz/Rf9lOBDBpJmQaIqYJzbk99443jr+MrdI 1YWZJ1ni9T7/lfehJ95XGBkEhbnpP5E41e4kPM7pUP+iGarILaRVa/0nYRgxxZK01THa kWnA== X-Gm-Message-State: AOAM533eXkcll9s2ne/I83z7uezmrc4qLGU1ML16f8ya/GSubTin9E8m 9ZhHo+wvOI+ECS5F9WY0Awt0EQ== X-Received: by 2002:a17:906:4cd6:: with SMTP id q22mr11753793ejt.139.1600039639010; Sun, 13 Sep 2020 16:27:19 -0700 (PDT) Received: from x1 ([2604:a880:400:d0::26:8001]) by smtp.gmail.com with ESMTPSA id br7sm6356560ejb.76.2020.09.13.16.27.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 13 Sep 2020 16:27:18 -0700 (PDT) Date: Mon, 14 Sep 2020 01:27:11 +0200 From: Drew Fustini To: Trent Piepho Cc: linux-arm-kernel@lists.infradead.org, Tony Lindgren , Rob Herring , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, Linus Walleij , Haojian Zhuang , devicetree@vger.kernel.org, bcousson@baylibre.com, Jason Kridner , Robert Nelson Subject: Re: [PATCH v4 1/2] pinctrl: single: parse #pinctrl-cells = 2 Message-ID: <20200913232711.GA2065644@x1> References: <20200701013320.130441-1-drew@beagleboard.org> <20200701013320.130441-2-drew@beagleboard.org> <3139716.CMS8C0sQ7x@zen.local> <20200913194233.GA1955808@x1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200913194233.GA1955808@x1> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Sep 13, 2020 at 09:42:33PM +0200, Drew Fustini wrote: > On Tue, Sep 08, 2020 at 04:52:58PM -0700, Trent Piepho wrote: > > On Tuesday, June 30, 2020 6:33:19 PM PDT Drew Fustini wrote: > > > If "pinctrl-single,pins" has 3 arguments (offset, conf, mux), then > > > pcs_parse_one_pinctrl_entry() does an OR operation on conf and mux to > > > get the value to store in the register. > > > > > > > - vals[found].val = pinctrl_spec.args[1]; > > > + > > > + switch (pinctrl_spec.args_count) { > > > + case 2: > > > + vals[found].val = pinctrl_spec.args[1]; > > > + break; > > > + case 3: > > > + vals[found].val = (pinctrl_spec.args[1] | > > pinctrl_spec.args[2]); > > > + break; > > > + } > > > > > > dev_dbg(pcs->dev, "%pOFn index: 0x%x value: 0x%x\n", > > > pinctrl_spec.np, offset, > > pinctrl_spec.args[1]); > > > > If #pinctrl-cells value is greater than 2, nothing will set vals[found].val to > > anything other than zero (from when it's calloc'ed) and the pinctrl will > > silently be programmed to zero. > > If #pinctrl-cells is 3, then it will be: > > vals[found].val = (pinctrl_spec.args[1] | pinctrl_spec.args[2]); > > Do you mean if #pinctrl-cells is great than 3 then it will just have a > default value of zero? > > That does appear to be the case and is probably not the behavior we > want. Thank you for pointing this out. Earlier, there is a check to > make sure there are at least 2 arguments: > > if (pinctrl_spec.args_count < 2) { > dev_err(pcs->dev, "invalid args_count for spec: %i\n", > pinctrl_spec.args_count); > break; > } > > I'll submit a patch where the upper bound is also checked: > > if (pinctrl_spec.args_count < 2 || pinctrl_spec.args_count > 3) { > dev_err(pcs->dev, "invalid args_count for spec: %i\n", > pinctrl_spec.args_count); > break; > } > I was mistaken when I wrote the above. I was using the term #pinctrl-cells when I should have been writing pinctrl_spec.args_count. pinctrl_spec.args_count is 2 when #pictrl-cells is 1. pinctrl_spec.args_count is 3 when #pictrl-cells is 2. I have submitted patches [1][2] with fixes for the bounds check and the dev_dbg(). > > The debug printout was not change to print vals[found].val, so it will > > continue to print the value of the 2nd cell. > > Thank you for pointing this out. Yes, this is an oversight and I will > submit a patch. > > > The result is that a #pinctrl-cells of 3 will produce no warning or error, > > program the pinctrl to zero, whilst at the same time emit debug log messages > > that it is programming the expected values. > > > > The device tree documentation still states that #pinctrl-cells must be 1 when > > using pinctrl-single,pins. This new special case of ORing two values is not > > documented. > > This is a good point, too. I will make a patch to update the > documentation. > > > -Drew [1] https://lore.kernel.org/linux-omap/20200913231557.2063071-1-drew@beagleboard.org/ [2] https://lore.kernel.org/linux-omap/20200913230306.2061645-1-drew@beagleboard.org/