Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp371378rwi; Wed, 26 Oct 2022 01:55:14 -0700 (PDT) X-Google-Smtp-Source: AMsMyM5HzSlwikKv28A44CQpgGRJm9umeiwI5dxUreoKoJcEb0kPjqthIcCm1qLq62L4xku9T2Yl X-Received: by 2002:a63:2d05:0:b0:460:55e3:df91 with SMTP id t5-20020a632d05000000b0046055e3df91mr36528375pgt.177.1666774514415; Wed, 26 Oct 2022 01:55:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666774514; cv=none; d=google.com; s=arc-20160816; b=Zm971h0s3nr/aza7hagfpeKsID923sAOrkfcJYx6oalymWk12CZyVtb/p0MZOwHxdy NOgclXlV/sBt8OOr6gU4VTR6P248GT+XkwhYXlEUzlQdzPwKByBt38t1+LiyfHvRBbAz Dz+wxjqtTrA1Uohsz5BVr7yp0bi78xWjtp1LAkP4QjXz9D0a2NbARYgV0iny+yrgCRFB MkIi3/bNZ0TH+ilXGsARM18qTL9rwEjXwsJemrPchDOnDFPw7HJsnzUB2i8HF6D7VbkD PExmqP2NgqaZM8uE0r72h8Vs7zzRPwlt1ypDn3vG1BVfRCemFanNI8WiyW6S6I99TQ3N 2g6Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=dHciPpZ1UgXbXRvGPu7x5GbGmWOSivcZ/5MPRV1/Ons=; b=VKZdLSzC6a1+9Y+G1yO0jvvcKjmzpjiAq7zpgTw9Qm7v2gzT9tDbtAtJPWoaWyEAtD 3d9fLcGAer2YfM7EG8G0TlfL69r7nnzKiFL8+4kklIwvZG08fd8PWfl53oV2XHFdniAA xzBe6GONyuqhBEAdlPJUSaG2XqvEIuAojWBkhMFtSTfsiaTT1MDZAwzLVUVJDqrzr+AM CXkvtilqNCzEg3xBx3ghA+qO4ZZYujmgXYDNB/EUkEVdigoJZ31AcP86BvfP+jqHWQ2i cfVIuA4JzbYX0ihgxZKpa6/RfdDNz3rvHa7jLurTga39Ws2oAm3wH/jOpfEFG0sr7BB5 ye/Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=HBPuNLia; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id b21-20020a17090aa59500b00202c7f4631esi1753729pjq.19.2022.10.26.01.55.02; Wed, 26 Oct 2022 01:55:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=HBPuNLia; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232946AbiJZIrO (ORCPT + 99 others); Wed, 26 Oct 2022 04:47:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51724 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229904AbiJZIrM (ORCPT ); Wed, 26 Oct 2022 04:47:12 -0400 Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D33107696D; Wed, 26 Oct 2022 01:47:11 -0700 (PDT) Received: by mail-ej1-x636.google.com with SMTP id sc25so19303379ejc.12; Wed, 26 Oct 2022 01:47:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=dHciPpZ1UgXbXRvGPu7x5GbGmWOSivcZ/5MPRV1/Ons=; b=HBPuNLiaf8LEoGHt9vdgvBgH+wID/hJDgyUmFN/i+CrvJANhSJKYN+sb7Izc/w4+sk /WfcGVJFkOxLUC/ykQV/1YAV659IcfSeTt9JqJcL9CuPdClwVGWD/w1zR92g79O/vR2R mcEShBP+h+mW5LSuEkWsMqlW8ud1IvPo86sm2UMEvwajuTlxza3iHb8rSUdyeDmTsr2P c/mezJVXUzW9CHb/2jn+dmHa2gzqI0prXGlljJRzM+IbKl5CeHdF3V+UgFizqkMZkRBD eteUctnBLmGvvur5uxHo+MiEVcrz3y9siQ4flTfn5WyjItSRXNalJmV6D2XSD8PQQOpO Nxow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=dHciPpZ1UgXbXRvGPu7x5GbGmWOSivcZ/5MPRV1/Ons=; b=nPLlWY3R0PFp0z25B4bwcQT/MTOT1AyANSZuSAlaAjBHyGWfykuMJgGDMeE7ncFp3x frikMlNe1mcyttER3SN9AiV1aggqcvjoUp2ZAdJ52v7nIXqj45bB4RaplA1CDsfNgn0s yQ1wWBjFlQpsSTiuCYIZ257R9QaspXQh0MhQn8KPlZfHArxQQ8wHRCCMTv+4EOhtSK63 9r9B3F10h/ZCWcnf/+lp1rWTWM6vO80BD9Zo/upFCYgGNfaOC7h2uAilWy/Y+lWpdK9q Ijw6taWMzEP3Bf6IIRG+qBuRzwAYyWRUuCaPDf1GJRFBljea09CWxHQpffBVl+5AtCGg hsgg== X-Gm-Message-State: ACrzQf30nvQotWqyKAWdjsQuo8+shaMBjiTKqYmLeExEREcrBlN6sML0 xRteCSsV9gb2GJhDWQquRqlfHlSPwQzTK+WqIzg= X-Received: by 2002:a17:906:c14f:b0:793:30e1:96be with SMTP id dp15-20020a170906c14f00b0079330e196bemr31466869ejc.447.1666774030318; Wed, 26 Oct 2022 01:47:10 -0700 (PDT) MIME-Version: 1.0 References: <20220915165256.352843-1-prabhakar.mahadev-lad.rj@bp.renesas.com> <20220915165256.352843-3-prabhakar.mahadev-lad.rj@bp.renesas.com> In-Reply-To: From: "Lad, Prabhakar" Date: Wed, 26 Oct 2022 09:46:43 +0100 Message-ID: Subject: Re: [PATCH 2/2] arm64: dts: renesas: rzg2ul-smarc: Add /omit-if-no-ref/ to pinmux To: Geert Uytterhoeven Cc: Magnus Damm , Rob Herring , Krzysztof Kozlowski , linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Biju Das , Lad Prabhakar Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Geert, On Wed, Oct 26, 2022 at 8:29 AM Geert Uytterhoeven wrote: > > Hi Prabhakar, > > On Wed, Oct 26, 2022 at 12:39 AM Lad, Prabhakar > wrote: > > On Tue, Oct 25, 2022 at 9:13 AM Geert Uytterhoeven wrote: > > > On Thu, Sep 15, 2022 at 6:53 PM Prabhakar wrote: > > > > From: Lad Prabhakar > > > > > > > > In preparation to re-use the RZ/G2UL SMARC SoM and carrier DTS/I with the > > > > RZ/Five add /omit-if-no-ref/ keyword to pinmux entries as the support for > > > > RZ/Five SMARC EVK will be gradually added. > > > > > > > > Once we have full blown support for RZ/Five SMARC EVK we can get rid of > > > > the /omit-if-no-ref/ keyword. > > > > > > > > Signed-off-by: Lad Prabhakar > > > > > > Thanks for your patch! > > > > > > I finally had a deeper look at this... > > > > > > Why do you want to disable these nodes? While they are indeed not > > > used yet on RZ/Five, they are valid hardware descriptions for the > > > RZ/Five SMARC EVK, and their presence doesn't harm anything. > > > > > > I do see a valid use case for marking pin control subnodes with > > > /omit-if-no-ref/: you can provide all possible configurations as a > > > convenience for the user, so the user no longer has to look up the > > > numeric parameters of the RZG2L_PORT_PINMUX() macros. > > > But IMHO those would belong in the SoC-specific .dtsi, not in a > > > board .dtsi. See e.g. the massive use of /omit-if-no-ref/ in sunxi > > > and rockchip .dtsi files. > > > > > > Am I missing something? > > > > > My intention was to keep the DTB as minimal as possible so that it > > includes just the required pinmuxes which were enabled on the RZ/Five. > > For example [0], [1] we do delete the pinctrl for the nodes which are > > marked as disabled. Do you think we should drop it? > > You mean > > /delete-property/ pinctrl-0; > /delete-property/ pinctrl-names; > > ? > These do not delete pinctrl subnodes, but pinctrl properties in disabled > device nodes pointing to pinctrl subnodes. The actual pinctrl subnodes > are still present. > Ahh right the pinctrl subnodes will still remain. Cheers, Prabhakar