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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id BDDDCC7EE31 for ; Tue, 30 May 2023 13:37:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232545AbjE3NhD (ORCPT ); Tue, 30 May 2023 09:37:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57820 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231202AbjE3NhC (ORCPT ); Tue, 30 May 2023 09:37:02 -0400 Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E1F86A1; Tue, 30 May 2023 06:37:00 -0700 (PDT) Received: by mail-ed1-x536.google.com with SMTP id 4fb4d7f45d1cf-514ab6cb529so2529951a12.1; Tue, 30 May 2023 06:37:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1685453819; x=1688045819; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=R0IWIqkvCL18T9qeOtu9NAQt+OvEofJMXnjblcNmSjY=; b=IyReP3q8IxnCSaJs0VU0mJ/YfofrvlenASA7XMfhGyL0VL7qiz6RLkDUPFz//scKQj ufIrgg1ZxzFUpRDqlXtkZw7a8MAcsrWbyLhNBxUGF/M5sE8UCKqLFrLcIsMlrvJhadMy tNt89YyHdTniRqYz/baPSmNOpnibtebm2hJ3osqpsTK1+CWJWfDFo8T6cOzs/RIjDFSa 8u0FkEIIO4hLHeMvD9ly08rRuLISQ57X+vjXCdKisFreJNwls06r+BtOTZN5SwQ/MEkH UdcilrAxqJXM6OyvnXZBAyzFk7zCTJWx6m8jdT+E3TZJlUxzqun7QclbrwtjSj4qPeZU JY8Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685453819; x=1688045819; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=R0IWIqkvCL18T9qeOtu9NAQt+OvEofJMXnjblcNmSjY=; b=Q9uTKKfAoXFV9GYEUGmzIAvlPK6+24vMo24IUzr2blUlkSbbRMYMRtW0EVifwgNV1V T13xobj2gWirVqD6QfzoTxmHt1BYTg78N1Db2cbHn0UrCOPob+wI4MzMR1MwrJHZMIDk QyocAwGlFwN+KqqyP3gNY+xP4MOtA0MXOtTgA6qKWQbp+pZ+ro5hC8RfCcgfcj7cp+qD StTvyF/3ZtwSgkIkXbmMCdS5v4egQ6cmcTdsjikAR3jjD5PfTGC8iiTYcq8kLfwdTYVd yiMdq7rxgLxsdd0tcafe7L63DcThMl+ZXW1JPL6FRFab58r1dDfOPXtJ3vtz3e19Lu1/ Wq4A== X-Gm-Message-State: AC+VfDwibABuneIufoxxCdH+CiGP19rK/2kpN6fhJQzBwjUD0Z+bes7g VWyX/sX5PJAYwKGMBghBRlJ2hT7+S9Y= X-Google-Smtp-Source: ACHHUZ7aR6lQs3L4LjqWBy2qx1L3csAHgpKgAoWPIujOHePrHL+ALGRZ9P80yzz/BhEwnNvLzbZYnw== X-Received: by 2002:a17:907:9712:b0:94a:4739:bed9 with SMTP id jg18-20020a170907971200b0094a4739bed9mr2374976ejc.13.1685453819127; Tue, 30 May 2023 06:36:59 -0700 (PDT) Received: from localhost (p200300e41f305300f22f74fffe1f3a53.dip0.t-ipconnect.de. [2003:e4:1f30:5300:f22f:74ff:fe1f:3a53]) by smtp.gmail.com with ESMTPSA id qt11-20020a170906eceb00b009655eb8be26sm7373130ejb.73.2023.05.30.06.36.58 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 30 May 2023 06:36:58 -0700 (PDT) From: Thierry Reding To: Linus Walleij , Thierry Reding , Rob Herring , Krzysztof Kozlowski , Conor Dooley Cc: Jon Hunter , Prathamesh Shete , linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org Subject: [PATCH v3 0/3] pinctrl: tegra: Add Tegra234 pinmux driver Date: Tue, 30 May 2023 15:36:51 +0200 Message-Id: <20230530133654.1296480-1-thierry.reding@gmail.com> X-Mailer: git-send-email 2.40.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-tegra@vger.kernel.org From: Thierry Reding Hi, this is an updated version of Prathamesh's v2 of the series, which can be found here: https://patchwork.ozlabs.org/project/linux-tegra/list/?series=345256 The most prominent change is the split of the device tree bindings into multiple files to make them more readable, as agreed upon with Krzysztof during review. Changes in v3: - split up device tree bindings into multiple files for better readability - do not permit underscore in pinmux node names - use correct #address-cells and #size-cells for DT nodes - fixup a typo in the gpio-ranges property name Note that the driver patch applies on top of the function table fix that I sent out earlier: http://patchwork.ozlabs.org/project/linux-tegra/list/?series=357206 Once accepted, patches 1 and 2 can go through the pinctrl tree and I can pick up patch 3 into the Tegra tree. Alternatively I can also pick up patch 1 into the Tegra tree to help with validation. We're not quite at a point yet where the Tegra DTs fully validate, so it doesn't matter much which way these get applied. Thanks, Thierry Prathamesh Shete (3): dt-bindings: pinctrl: Document Tegra234 pin controllers pinctrl: tegra: Add Tegra234 pinmux driver arm64: tegra: Add Tegra234 pin controllers .../pinctrl/nvidia,tegra234-pinmux-aon.yaml | 61 + .../nvidia,tegra234-pinmux-common.yaml | 65 + .../pinctrl/nvidia,tegra234-pinmux.yaml | 141 ++ arch/arm64/boot/dts/nvidia/tegra234.dtsi | 12 + drivers/pinctrl/tegra/Kconfig | 4 + drivers/pinctrl/tegra/Makefile | 1 + drivers/pinctrl/tegra/pinctrl-tegra234.c | 1969 +++++++++++++++++ drivers/soc/tegra/Kconfig | 1 + 8 files changed, 2254 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-aon.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux-common.yaml create mode 100644 Documentation/devicetree/bindings/pinctrl/nvidia,tegra234-pinmux.yaml create mode 100644 drivers/pinctrl/tegra/pinctrl-tegra234.c -- 2.40.1