Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp322828pxf; Thu, 11 Mar 2021 04:56:38 -0800 (PST) X-Google-Smtp-Source: ABdhPJwDjWawJEBkgjvKdr4EYcd3or+4zh+mqTDTDO0OBvj4Vtd7KgMkZLz743TCwaXW0xdBuc52 X-Received: by 2002:a17:906:3b47:: with SMTP id h7mr2900455ejf.377.1615467397969; Thu, 11 Mar 2021 04:56:37 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615467397; cv=none; d=google.com; s=arc-20160816; b=Uf5Xii+g9Ssvem0Ki9ETtd8wLQCX7A8iJQpujZMthoiFZKsituG8awipakufHhW/RX XxyKTbyRU8Eci3+P2s01rZCYVXC7yUqUn6+5rgRZmOqpKPy1vjumHGVfqeftXno71TMX bN/vqGR/bjQ9g4HgbxkmsZg8QsmkC6K8EHPeWPFdBaGhYGH+rL8u/hdQ4DjUbLIL+HvK qU9zJl4tnq3KiwEl9beDNwIUhd6bV41/r2Pq1iplCdve7FW4p+tidFRryq+r3W3r/SDB fLJ3Eaypld+zy5HKyOVcoJIFVs/Tvmfui7EClJbLt9Ctgnw7iZa2NGwVEY4UYt2eBDO0 OyAQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=MNvZ4bXw2hj1Os0jbIudI0MFmq0h14u7LR0x+CA8uTg=; b=XXZZ/0yhrhd37c9nGSUqkG21Z8V+eLoeDHbuu9YGqJZq+Jq2+4fNOW3/nObFSbhADn TYk8vbrhyh/1j8fxbdfmrvfkIrEzyyHODzXhQrbdicXLspnkLF5fEKTsiPp2y43C9H5C zDuydc95mvb53Z+ZeC71qRrqaKSwlsNyZHcB/KgGQF8fuDe3ENQ8NT+Cu4/FeYmLCPs7 h1pu/aNtlFtCWscxJaGolIfE4NHzMFV2INC7FFDyCEdypMMkJZ+1i71xJLR7Lz2o+Hag +tiweHlmMJPej9sT4Bc78eSzLbYlgNgcauliXEelsCbB4MBtXPVycigIZp76phKp+Cwc ssaw== 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 c1si1699963edt.469.2021.03.11.04.56.15; Thu, 11 Mar 2021 04:56:37 -0800 (PST) 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 S233061AbhCKMzG (ORCPT + 99 others); Thu, 11 Mar 2021 07:55:06 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39116 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233036AbhCKMy7 (ORCPT ); Thu, 11 Mar 2021 07:54:59 -0500 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 03425C061574 for ; Thu, 11 Mar 2021 04:54:59 -0800 (PST) Received: from gallifrey.ext.pengutronix.de ([2001:67c:670:201:5054:ff:fe8d:eefb] helo=[IPv6:::1]) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1lKKq2-0005KZ-KO; Thu, 11 Mar 2021 13:54:50 +0100 Subject: Re: [Linux-stm32] [PATCH 5/8] ARM: dts: stm32: introduce stm32h7-pinctrl.dtsi to support stm32h75x To: dillon min , Alexandre TORGUE Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Vladimir Murzin , Linux Kernel Mailing List , linux@armlinux.org.uk, Rob Herring , Maxime Coquelin , afzal.mohd.ma@gmail.com, linux-stm32@st-md-mailman.stormreply.com, Linux ARM References: <1614758717-18223-1-git-send-email-dillon.minfei@gmail.com> <1614758717-18223-6-git-send-email-dillon.minfei@gmail.com> From: Ahmad Fatoum Message-ID: Date: Thu, 11 Mar 2021 13:54:48 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit X-SA-Exim-Connect-IP: 2001:67c:670:201:5054:ff:fe8d:eefb X-SA-Exim-Mail-From: a.fatoum@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Dillon, On 11.03.21 13:23, dillon min wrote: > For stm32h7's new board support , I guess following the stm32f7/stm32f4's style > is a reasonable way to do it, but add a little optimization。 > which means : > old structure > stm32h7-pinctrl.dtsi --> stm32h743-pinctrl.dtsi (referenced by > stm32h743i-disco, -eval) > |--> stm32h750-pinctrl.dtsi > (referenced by stm32h750i-art-pi, etc) > add art-pi other board's pin definition in stm32h750-pinctrl.dtsi with > xxx_pins_a, xxx_pins_b > xxx_pins_a used for art-pi, xxx_pins_b used for other boards. > > after more boards add in support, there will be more xxx_pin_c, .... defined > > as the pin map is according to the hardware schematic diagram io connection. > so, why not move xxx_pin_x to a board specific place. such as > stm32h750i-art-pi.dts > > new structure: > 1, rename stm32h743-pinctrl.dtsi to stm32h7-pinctrl.dtsi (only > preserve gpioa...k,) > 2, move xxx_pins_x from stm32h7-pinctrl.dtsi to > stm32h7xx-disco/eval/art-pi/etc.dts (as they depends on hardware > schematic) > > stm32h7-pinctrl.dtsi --> stm32h743i-discon.dts > |--> stm32h743i-eval.dts > |--> stm32h750i-art-pi.dts > |--> stm32h7xxx.dts > would you agree this ? If the optimization you intend is reducing DTB size, you can flag all pinctrl groups with /omit-if-no-ref/ to have dtc throw them away if they are unused. (But in general, I am in favor of having board-specific configuration in the board dts) Cheers, Ahmad -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |