Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp100722pxk; Thu, 24 Sep 2020 00:08:50 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzIDEzSghBuR3Xw6tmlt5swy+VuFQIBBDrwq42c4bY8lHE46fFxDB1NhIHECCbhKULi19mo X-Received: by 2002:aa7:d750:: with SMTP id a16mr3217807eds.362.1600931330498; Thu, 24 Sep 2020 00:08:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600931330; cv=none; d=google.com; s=arc-20160816; b=OVY/HzpCwLGdgy+UdERBeI+eAz3WA5ZiwQBe0Wn2Blcgg1dj3Bu7uFGvmgONu00ZzU mlSg+WIwFRxVMBJxyDginYR0dK3AUeq87CgnyEQyIKjxHbnGGciDoRirCc/4cnxo07qm gl6dzL81ao3xpovdUIx5gb5wm2O+1gRF38f8GygoCI5cpbBUimj38hsNHLXoBa7bUwiX IDnF4LH5akdugZlvikAJCA/ofZAi7q3XCeD3ORhH39CwiVgzSke/jNj4Kxrijm4j3rZ6 PPjW54bj+v33gq8oSaVWpkHND2xbkEBbbWqg0DGiTeFQAORBmX3YXf3Y9XpK6FVC0ckS fJOA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date; bh=YuZe1FlMTdFZaX9apzxMloXRuydAGcG1qTQHQigjSg0=; b=cjD+cBiLzT3ymBbF+TRa/Ylu6LaNOmAt/aGDFauhBWv17OGWHHXGT7NQEFqhrhh90n 1LA+MkkUhl1eUXsaf7R0UfJoYciDEC8jZFjW+jIe9PeUSTFXfkDIsPghe1YJ3daAJyNG 5Bm2Qiaeok4FxC4Hv+kqweLrefyceFMeT3tfl/mTbNFi4fZ8aC5t3mjdP3m3ZxNA+ltZ KlH5HE+04SooxOy3xkkJm6C9/M94u1CZn11QbM/TMdjM3y1ANwBWP131k1oRRtV4uN7Y LCYvACtDUTVSW4WJ4DE/mTHR3R4hcta2EXACMOvbLuct9Srnp/o3rnKjtMsvGHzngmYV Igaw== 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 j12si1479022ejf.511.2020.09.24.00.08.25; Thu, 24 Sep 2020 00:08:50 -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 S1727114AbgIXHEu (ORCPT + 99 others); Thu, 24 Sep 2020 03:04:50 -0400 Received: from muru.com ([72.249.23.125]:45356 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727001AbgIXHEt (ORCPT ); Thu, 24 Sep 2020 03:04:49 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 8E4708027; Thu, 24 Sep 2020 07:04:49 +0000 (UTC) Date: Thu, 24 Sep 2020 10:04:43 +0300 From: Tony Lindgren To: Trent Piepho Cc: Drew Fustini , Rob Herring , Linus Walleij , Jason Kridner , Robert Nelson , linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-gpio , Christina Quast Subject: Re: [PATCH] ARM: dts: document pinctrl-single,pins when #pinctrl-cells = 2 Message-ID: <20200924070443.GF9471@atomide.com> References: <20200917092004.GA2468349@x1> <20200917103942.GA2477958@x1> <20200923065755.GR7101@atomide.com> <20200924054324.GB9471@atomide.com> <20200924060645.GD9471@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Trent Piepho [200924 06:31]: > On Wed, Sep 23, 2020 at 11:06 PM Tony Lindgren wrote: > > > > * Trent Piepho [200924 05:49]: > > > On Wed, Sep 23, 2020 at 10:43 PM Tony Lindgren wrote: > > > > > > > > * Trent Piepho [200924 01:34]: > > > > > On Tue, Sep 22, 2020 at 11:57 PM Tony Lindgren wrote: > > > > > > > > > > > > Also FYI, folks have also complained for a long time that the pinctrl-single > > > > > > binding mixes mux and conf values while they should be handled separately. > > > > > > > > > > > > > > > > Instead of combining two fields when the dts is generated they are now > > > > > combined when the pinctrl-single driver reads the dts. Other than > > > > > this detail, the result is the same. The board dts source is the > > > > > same. The value programmed into the pinctrl register is the same. > > > > > There is no mechanism currently that can alter that value in any way. > > > > > > > > > > What does combining them later allow that is not possible now? > > > > > > > > It now allows further driver changes to manage conf and mux separately :) > > > > > > The pinctrl-single driver? How will that work with boards that are > > > not am335x and don't use conf and mux fields in the same manner as > > > am335x? > > > > For those cases we still have #pinctrl-cells = <1>. > > If pincntrl-single is going to be am335x specific, then shouldn't it > be a different compatible string? Certainly different compatible strings can be used as needed. But pinctrl-single is not going to be am335x specific though :) We have quite a few SoCs using it: $ git grep pinctrl-single,function-mask arch/*/boot/dts/ | wc -l 41 > Are the driver changes something that can be not be done with the > pinconf-single properties? They all include a mask. Sure but in the long term we're better off with using #pinctrl-cells along the lines what we have for example for #interrupt-cells and #gpio-cells. Regards, Tony