| Message ID | 20221020160305.18711-1-afd@ti.com |
|---|---|
| Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org>
Delivered-To: ouuuleilei@gmail.com
Received: by 2002:a5d:4242:0:0:0:0:0 with SMTP id s2csp192317wrr;
Thu, 20 Oct 2022 09:05:56 -0700 (PDT)
X-Google-Smtp-Source:
AMsMyM4j8CMt1YlQkCGcdjCafKkqw97zHIhlyqXX5bk3eoi9m5f7ytPYx7ROnkSr9XFFopMafTuU
X-Received: by 2002:a05:6402:27c9:b0:45d:4539:b462 with SMTP id
c9-20020a05640227c900b0045d4539b462mr12961571ede.226.1666281956131;
Thu, 20 Oct 2022 09:05:56 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1666281956; cv=none;
d=google.com; s=arc-20160816;
b=xdjJs5m2MR0ElGyIH8rAKbcYpbIPZnUsJB/yRvTFOMW+1dDX9wn57t9amD7eQKzbL2
QZQWYlqXXZCurkj8Ve2XH+Wtaa+xDPwqzw9zWnsG9qf1KVbHekdq2lIWfmbVaiqF0Hds
FVPwNkuYCDdR+mIpGWw+2/rztsGPDaBlLFkARYF7Is2MCz5Ne9+fznkmjA/1JU9L+yuJ
SXLCBn0hjM7OwrUlseNDPUoJNnQ18Wfi4KiQfzypj0LLsnlRB+IVkFwMajczjqk3kOw9
0ebgctkEm6PR4EG3CORFYESQb8D0KnPjVZ3owjS6GCmDBKtWvLDwOAMaVYHglxWQ0oCc
84cw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=arc-20160816;
h=list-id:precedence:content-transfer-encoding:mime-version
:message-id:date:subject:cc:to:from:dkim-signature;
bh=wvUQik+bt9an5Axw/prGLLpTfoToXrmSW0PRYTs+jbU=;
b=Napuw6a+p6/aGSKEkinqBSVL+m4Cy5nTuZ3Goe415UC2Mamvw4bl/GSsCCsKh5TPv3
u/tsDf7Q0xyyskieQInSlmLrMp1+kXXzFmeru+JKZD6NplovGslub3NJRcXf/259Z2vf
Gy2BAo5vEwC1QNLl9HtfW2hkoo8fvzkLaAXv+537rnT0ku0YSVu6X3lkzfUBRVXjQ9Lm
G4hbd1jx6DypjnHZI7y0JeKY0ZRjIFRRpS0THhxoS/U1awZJyqiNBgKhypEAf9KQrkXJ
gz9em7DGTbmd67hgFANTwcbIXMrOfQDWY9CSobJ6vu+XeNQAKok3UBtg5BdE+jQERweu
ad1A==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=eX7HQ6dY;
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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com
Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20])
by mx.google.com with ESMTP id
n12-20020a05640205cc00b0045c29d74fcesi21554355edx.568.2022.10.20.09.05.21;
Thu, 20 Oct 2022 09:05:56 -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=@ti.com header.s=ti-com-17Q1 header.b=eX7HQ6dY;
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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
id S230497AbiJTQDv (ORCPT <rfc822;ruipengqi7@gmail.com> + 99 others);
Thu, 20 Oct 2022 12:03:51 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60328 "EHLO
lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
with ESMTP id S230454AbiJTQDa (ORCPT
<rfc822;linux-kernel@vger.kernel.org>);
Thu, 20 Oct 2022 12:03:30 -0400
Received: from fllv0015.ext.ti.com (fllv0015.ext.ti.com [198.47.19.141])
by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4E8261B233B;
Thu, 20 Oct 2022 09:03:28 -0700 (PDT)
Received: from lelv0265.itg.ti.com ([10.180.67.224])
by fllv0015.ext.ti.com (8.15.2/8.15.2) with ESMTP id 29KG37eS119630;
Thu, 20 Oct 2022 11:03:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com;
s=ti-com-17Q1; t=1666281787;
bh=wvUQik+bt9an5Axw/prGLLpTfoToXrmSW0PRYTs+jbU=;
h=From:To:CC:Subject:Date;
b=eX7HQ6dYlDuKmMQ7sYKqZ1R+tg8+l6aeqco/VrpD6PADT6O8yhAz5GMg/74EVmj8N
x0L1qJBGyJF9wv1Gr0lugETRWf7uXlMIh7qobFuIMusDRq6Xv7UnyYpjCMwqvTXHfF
UqIBSlKu2cBsHyRCTXd5UwOcZR93yVVqTtzae2lk=
Received: from DFLE103.ent.ti.com (dfle103.ent.ti.com [10.64.6.24])
by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 29KG37UO014799
(version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL);
Thu, 20 Oct 2022 11:03:07 -0500
Received: from DFLE103.ent.ti.com (10.64.6.24) by DFLE103.ent.ti.com
(10.64.6.24) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.6; Thu, 20
Oct 2022 11:03:06 -0500
Received: from fllv0040.itg.ti.com (10.64.41.20) by DFLE103.ent.ti.com
(10.64.6.24) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.6 via
Frontend Transport; Thu, 20 Oct 2022 11:03:06 -0500
Received: from ula0226330.dal.design.ti.com (ileaxei01-snat.itg.ti.com
[10.180.69.5])
by fllv0040.itg.ti.com (8.15.2/8.15.2) with ESMTP id 29KG3638059665;
Thu, 20 Oct 2022 11:03:06 -0500
From: Andrew Davis <afd@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Bryan Brattlof <bb@ti.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
CC: Andrew Davis <afd@ti.com>
Subject: [PATCH 00/12] TI J7x Disable Incomplete DT Nodes
Date: Thu, 20 Oct 2022 11:02:53 -0500
Message-ID: <20221020160305.18711-1-afd@ti.com>
X-Mailer: git-send-email 2.37.3
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,
DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED,
SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?=
X-GMAIL-THRID: =?utf-8?q?1747223268281653620?=
X-GMAIL-MSGID: =?utf-8?q?1747223268281653620?=
|
| Series |
TI J7x Disable Incomplete DT Nodes
|
|
Message
Andrew Davis
Oct. 20, 2022, 4:02 p.m. UTC
Hello all, Same story as for AM64x[0] and AM62x[1], this time for J7x. This one was a little more involved that the last 2 rounds as some IP (like UART) are pinned out using the default pinmux. Perhaps we should be explicit here and have pinmux nodes that simply restate the defaults. I can go solve that in a follow up series if we think that is what we want to do. I have the last round for AM65x ready to post, but that involves a few boards that I do not have (Simatic IOT2050) but would like to do some additional re-work with, so holding off until after I get that sorted. Thanks, Andrew [0] https://www.spinics.net/lists/arm-kernel/msg1018532.html [1] https://www.spinics.net/lists/arm-kernel/msg1018864.html Andrew Davis (12): arm64: dts: ti: k3-j721e: Enable UART nodes at the board level arm64: dts: ti: k3-j721e: Enable I2C nodes at the board level arm64: dts: ti: k3-j721e: Enable MCASP nodes at the board level arm64: dts: ti: k3-j721e: Enable MCAN nodes at the board level arm64: dts: ti: k3-j7200: Enable UART nodes at the board level arm64: dts: ti: k3-j7200: Enable I2C nodes at the board level arm64: dts: ti: k3-j721s2: Enable UART nodes at the board level arm64: dts: ti: k3-j721e: Enable Mailbox nodes at the board level arm64: dts: ti: k3-j7200: Enable Mailbox nodes at the board level arm64: dts: ti: k3-j721s2: Enable Mailbox nodes at the board level arm64: dts: ti: k3-j721s2: Enable MCAN nodes at the board level arm64: dts: ti: k3-j721s2: Enable I2C nodes at the board level .../dts/ti/k3-j7200-common-proc-board.dts | 48 ++---- arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 29 ++++ .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 5 + arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi | 42 +---- .../dts/ti/k3-j721e-common-proc-board.dts | 141 +++------------- arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 55 ++++++ .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 7 + arch/arm64/boot/dts/ti/k3-j721e-sk.dts | 158 ++---------------- arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi | 33 +--- .../dts/ti/k3-j721s2-common-proc-board.dts | 132 +-------------- arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 58 +++++++ .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 7 + arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi | 98 +---------- 13 files changed, 231 insertions(+), 582 deletions(-)
Comments
On October 20, 2022 thus sayeth Andrew Davis: > Hello all, > > Same story as for AM64x[0] and AM62x[1], this time for J7x. > > This one was a little more involved that the last 2 rounds as some IP > (like UART) are pinned out using the default pinmux. Perhaps we should be > explicit here and have pinmux nodes that simply restate the defaults. I > can go solve that in a follow up series if we think that is what we > want to do. > > I have the last round for AM65x ready to post, but that involves a few > boards that I do not have (Simatic IOT2050) but would like to do some > additional re-work with, so holding off until after I get that sorted. > > Thanks, > Andrew > > [0] https://www.spinics.net/lists/arm-kernel/msg1018532.html > [1] https://www.spinics.net/lists/arm-kernel/msg1018864.html > > Andrew Davis (12): > arm64: dts: ti: k3-j721e: Enable UART nodes at the board level > arm64: dts: ti: k3-j721e: Enable I2C nodes at the board level > arm64: dts: ti: k3-j721e: Enable MCASP nodes at the board level > arm64: dts: ti: k3-j721e: Enable MCAN nodes at the board level > arm64: dts: ti: k3-j7200: Enable UART nodes at the board level > arm64: dts: ti: k3-j7200: Enable I2C nodes at the board level > arm64: dts: ti: k3-j721s2: Enable UART nodes at the board level > arm64: dts: ti: k3-j721e: Enable Mailbox nodes at the board level > arm64: dts: ti: k3-j7200: Enable Mailbox nodes at the board level > arm64: dts: ti: k3-j721s2: Enable Mailbox nodes at the board level > arm64: dts: ti: k3-j721s2: Enable MCAN nodes at the board level > arm64: dts: ti: k3-j721s2: Enable I2C nodes at the board level > > .../dts/ti/k3-j7200-common-proc-board.dts | 48 ++---- > arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 29 ++++ > .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 5 + > arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi | 42 +---- > .../dts/ti/k3-j721e-common-proc-board.dts | 141 +++------------- > arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 55 ++++++ > .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 7 + > arch/arm64/boot/dts/ti/k3-j721e-sk.dts | 158 ++---------------- > arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi | 33 +--- > .../dts/ti/k3-j721s2-common-proc-board.dts | 132 +-------------- > arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 58 +++++++ > .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 7 + > arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi | 98 +---------- > 13 files changed, 231 insertions(+), 582 deletions(-) > *whew* these Jacinto boards have a lot of stuff on them :) but it LGTM Reviewed-by: Bryan Brattlof <bb@ti.com> ~Bryan
On 20/10/22 9:32 pm, Andrew Davis wrote: > Andrew Davis (12): > arm64: dts: ti: k3-j721e: Enable UART nodes at the board level > arm64: dts: ti: k3-j721e: Enable I2C nodes at the board level > arm64: dts: ti: k3-j721e: Enable MCASP nodes at the board level > arm64: dts: ti: k3-j721e: Enable MCAN nodes at the board level > arm64: dts: ti: k3-j7200: Enable UART nodes at the board level > arm64: dts: ti: k3-j7200: Enable I2C nodes at the board level > arm64: dts: ti: k3-j721s2: Enable UART nodes at the board level > arm64: dts: ti: k3-j721e: Enable Mailbox nodes at the board level > arm64: dts: ti: k3-j7200: Enable Mailbox nodes at the board level > arm64: dts: ti: k3-j721s2: Enable Mailbox nodes at the board level > arm64: dts: ti: k3-j721s2: Enable MCAN nodes at the board level > arm64: dts: ti: k3-j721s2: Enable I2C nodes at the board level > > .../dts/ti/k3-j7200-common-proc-board.dts | 48 ++---- > arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 29 ++++ > .../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 5 + > arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi | 42 +---- > .../dts/ti/k3-j721e-common-proc-board.dts | 141 +++------------- > arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 55 ++++++ > .../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 7 + > arch/arm64/boot/dts/ti/k3-j721e-sk.dts | 158 ++---------------- > arch/arm64/boot/dts/ti/k3-j721e-som-p0.dtsi | 33 +--- > .../dts/ti/k3-j721s2-common-proc-board.dts | 132 +-------------- > arch/arm64/boot/dts/ti/k3-j721s2-main.dtsi | 58 +++++++ > .../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 7 + > arch/arm64/boot/dts/ti/k3-j721s2-som-p0.dtsi | 98 +---------- > 13 files changed, 231 insertions(+), 582 deletions(-) Acked-by: Vignesh Raghavendra <vigneshr@ti.com>
Hi Andrew Davis, On Thu, 20 Oct 2022 11:02:53 -0500, Andrew Davis wrote: > Same story as for AM64x[0] and AM62x[1], this time for J7x. > > This one was a little more involved that the last 2 rounds as some IP > (like UART) are pinned out using the default pinmux. Perhaps we should be > explicit here and have pinmux nodes that simply restate the defaults. I > can go solve that in a follow up series if we think that is what we > want to do. > > [...] I have applied the following to branch ti-k3-dts-next on [1]. Thank you! [01/12] arm64: dts: ti: k3-j721e: Enable UART nodes at the board level commit: fe17e20fde14c6cbaf1cae97aef370b6f4c73518 [02/12] arm64: dts: ti: k3-j721e: Enable I2C nodes at the board level commit: 282c4ad3b8c1da99095e0edbbe617cdf4dcb138b [03/12] arm64: dts: ti: k3-j721e: Enable MCASP nodes at the board level commit: 256596ad158c80c8e4104a6310a411ec8829f9eb [04/12] arm64: dts: ti: k3-j721e: Enable MCAN nodes at the board level commit: 39e7758b94e31071a87489364c723afe92849ae7 [05/12] arm64: dts: ti: k3-j7200: Enable UART nodes at the board level commit: dae322f8a7ef11a06bfb61bada4ebbcac219783e [06/12] arm64: dts: ti: k3-j7200: Enable I2C nodes at the board level commit: a9ed915cd55c883fed72e50b45988fa4305496a7 [07/12] arm64: dts: ti: k3-j721s2: Enable UART nodes at the board level commit: 0e63f35a9c6acf1d74bd693c492f8955bb16c89a [08/12] arm64: dts: ti: k3-j721e: Enable Mailbox nodes at the board level commit: 7e48b665100ee84bdaa163dece6d40351077f664 [09/12] arm64: dts: ti: k3-j7200: Enable Mailbox nodes at the board level commit: 74f0f58d3122c3e2cc313dd6311b9742dbfd54e0 [10/12] arm64: dts: ti: k3-j721s2: Enable Mailbox nodes at the board level commit: 3fb0402f65959edc9a14842dc36828d2c7109ae2 [11/12] arm64: dts: ti: k3-j721s2: Enable MCAN nodes at the board level commit: 06639b8ae0e9be0cf0195209e6b69f4e254687b0 [12/12] arm64: dts: ti: k3-j721s2: Enable I2C nodes at the board level commit: 0aef5131380628e2a9bfcbbcfed5d6477c8f9651 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent up the chain during the next merge window (or sooner if it is a relevant bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. [1] git://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git