From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CADE6C4363D for ; Thu, 24 Sep 2020 01:34:37 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 91E5E21D7F for ; Thu, 24 Sep 2020 01:34:37 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="cchMfWJL" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726064AbgIXBed (ORCPT ); Wed, 23 Sep 2020 21:34:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51360 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725208AbgIXBed (ORCPT ); Wed, 23 Sep 2020 21:34:33 -0400 Received: from mail-ej1-x643.google.com (mail-ej1-x643.google.com [IPv6:2a00:1450:4864:20::643]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 3C2D3C0613CE; Wed, 23 Sep 2020 18:34:33 -0700 (PDT) Received: by mail-ej1-x643.google.com with SMTP id j11so2269429ejk.0; Wed, 23 Sep 2020 18:34:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BdVDi/8E9qWkSdKxeY/lJ0KoRE68VzIF4q1Pns2xhD4=; b=cchMfWJLbTknIU61451rYND7QC8qYeJgN6egxZppAsXuwTvDsYc8htefTrxT/eSqO2 UpbmZvOVIOme+TpfwdjZlHCxpi3/pZ0cFL0T7Cy53lpD+RIIJivxhkE8VFGDITwx1+2G GqQMPHSYce5cwuh3vbcF6Q8rzMquc/XpFaWkWnnti0GdilXS/yHP8J/lGSO9/ThbbeqG ERtZ4fUOdGA25Tjn/USYwtASuI4VqyagxKDF9VZ3QMEgaZN1Af5Xo3f4oIKA1ZVUqrQe /xHhL5Lglc4moV/iF/KCCMYx2F47VucWY1rCPnFkkyUKzs5l38akdbY0/EBCzzC8lau+ 0FHA== 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=BdVDi/8E9qWkSdKxeY/lJ0KoRE68VzIF4q1Pns2xhD4=; b=WTatE0FBzVXzu8Ll87+idsqSOzwJNVNPqNJQq31B8nb4QlIjEnxBKpMCifcNKzs4U+ GJ7981db3sWT9vrhi9eRqq3Hp0HcVRbgTou30lhHgtVaD6uBp8t9wlPZvUIi5tUAqwUC 5vnzEgWjM3Jf7Ofo+1U2DnHdRDE2Alc0RvGAtXmBoLehtJikKpNdDjznipOBoJcH+qUB 60OXMQM+V6Umt55y/ADsf4vgXlr125XZwcalbq+5I/3uzXKdolak7G7KWEDMrutZBrak ioF+bZABn86IvDJODoHjVEQ8tXkL2sDaNU6L2rgdte35NS20zHl+VvrE2UpmrEBOyhlz 6Rug== X-Gm-Message-State: AOAM533b/jH3jcGM5ldP9cS8QUU6wRBoM1cdcR1j9/yY6DXLCWABl1HT t+p6ie65ALpmrG0kDBu7ocyui8BbGFm5NJcTOnk= X-Google-Smtp-Source: ABdhPJzMxMdP4kSFMn/hJnAwQtYoFTQZYIFjGNisG2wS8nogdPXCZQxSXQvjrd6XQufmIDZ0SbrxRnwJ3VNn3PbOR1w= X-Received: by 2002:a17:906:390d:: with SMTP id f13mr2326309eje.86.1600911271918; Wed, 23 Sep 2020 18:34:31 -0700 (PDT) MIME-Version: 1.0 References: <20200914104352.2165818-1-drew@beagleboard.org> <20200917092004.GA2468349@x1> <20200917103942.GA2477958@x1> <20200923065755.GR7101@atomide.com> In-Reply-To: <20200923065755.GR7101@atomide.com> From: Trent Piepho Date: Wed, 23 Sep 2020 18:34:21 -0700 Message-ID: Subject: Re: [PATCH] ARM: dts: document pinctrl-single,pins when #pinctrl-cells = 2 To: Tony Lindgren 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 Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-omap@vger.kernel.org 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?