Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1042428imm; Fri, 17 Aug 2018 10:49:20 -0700 (PDT) X-Google-Smtp-Source: AA+uWPzUvr4R49//7JB43zqdA1q8F3xFbbw5CCCRILzKO2sB2ZOejRfLLeAumQE4Tkq1t8l2jpZk X-Received: by 2002:a65:5bc4:: with SMTP id o4-v6mr33420679pgr.448.1534528160535; Fri, 17 Aug 2018 10:49:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1534528160; cv=none; d=google.com; s=arc-20160816; b=kl55XNN3NLSZt2FoeyfTAhYJ/AR+91PSvLP3gECPO7GNf6kT37M4E28UJU+DBGYf1W vgrz2lNv4C95yFsciqP5gJKsj4KzofMqwex5EUC/686zcZOvo1KRuS2a/RqMNGNcb+QF rtuKJsDbsfX/R56IVbSnz/LAuxzY99ZUCM/JbxKm6No9o15E5ANxjK+UD1aK5HYwlSzr taXJnJdBzQbLNch29cn9tI2jqlK2Xa/sdXciWiwIjcRZ1tbTVUeUeuBYUfSYgBszKvqF vqB80soZpSLsSxYJxAWtk9obXVZ3RwsOolvaFFtyknY08kI5ZZK2yEddmVvJnIxfqABB +nwQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature:arc-authentication-results; bh=C4Ejh4H3HNbON2RHvou25auTHCA+zd93OIFz7wrwY6Q=; b=UPkpag7MxYajBBqXnGNr7H1ZoOloEv2OtVjSfYAJ7B/odiAQbwyt5nYurOhjdMGMi4 1wmj+uPCPByF5ZPFo5vzMR2WFmSwjBbwiThinjw5YQfSV9H2hs5s/ZWjp0i2ANYOPVOJ 96ngJF9NGiSKvPwC5W+o7/II5JeK+AnUQapf7Cp62V5o4JtmzXrZjkPXl3sklVf4JkmJ F+L1Grl0WPt0AEQIG3BqffKb3Kd1GUOQ6Y2aUdEWKAtNBoKGyND/NVMeXo4C73p51Skq b3tQD68ZkEfvvyavxH2NHls9suKK4wffOVsRK/d+08FgYzC5AGR/5yx9mmA+62/XZx96 P9nw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=XjfQM5BO; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c192-v6si2536508pfg.347.2018.08.17.10.49.05; Fri, 17 Aug 2018 10:49:20 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=XjfQM5BO; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727981AbeHQUwS (ORCPT + 99 others); Fri, 17 Aug 2018 16:52:18 -0400 Received: from mail.kernel.org ([198.145.29.99]:42502 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727612AbeHQUwS (ORCPT ); Fri, 17 Aug 2018 16:52:18 -0400 Received: from mail-qt0-f174.google.com (mail-qt0-f174.google.com [209.85.216.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 674A521A28; Fri, 17 Aug 2018 17:48:00 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1534528080; bh=z/5ZXNrx3/HqKYWq60LZsUq86ZQ/t3YeMwxVJwm0pXA=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=XjfQM5BOb7INTZ7poHHVl1gHfPh+8AFiH1YGHXj22aZs19uLPOSzZK0nneewCl+HJ jM4ONfHE0RjsDkSRuW4sHS5mRBS2G5v1jcgl/H1JLJW7mPJyzqPjIoe2fiZI8rf4Tg yQ6MmnBssxvOjd3BfxmjK8PUrv1rU5Zha26ilGlI= Received: by mail-qt0-f174.google.com with SMTP id n6-v6so9626803qtl.4; Fri, 17 Aug 2018 10:48:00 -0700 (PDT) X-Gm-Message-State: AOUpUlGMOFnA1DZjqaFcjMfXfyJwNlXyB9aRzY9Xa2jx93jJuAio6PV5 QFeBtKi5NKuW01gK2EeOgHusHsgVN73EKzCJxQ== X-Received: by 2002:ac8:2c72:: with SMTP id e47-v6mr36502752qta.60.1534528079599; Fri, 17 Aug 2018 10:47:59 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Rob Herring Date: Fri, 17 Aug 2018 11:47:48 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: How delete node or property in overlayd dts? To: zbsdta@gmail.com, Frank Rowand Cc: devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 14, 2018 at 7:26 PM Frank Rowand wrote= : > > On 08/14/18 07:46, =E5=BC=A0=E6=B3=A2 wrote: > > /delete-node/ /delete-prop/ could be used in dtsi files without device > > tree overlay. > > > > but with device tree overlay, /delete-node/ and /delete-prop/ are not= work. > > How to delete property and node in overlay dts? > > > > for example, > > in basel.dts have following node > > node1 { > > property1; > > property3; > > node2 { > > property2; > > } > > } > > > > in overlay.dts as following > > node1 { > > /delete-property/ property1; > > /delete-node/ node2; > > } > > > > after overlay, property1 and node2 is not deleted. > > > > The /delete-node/ and /delete-prop/ directives are only used by the > dtc compiler within a single compilation. > > There is nothing in the format of a devicetree blob to represent the > notion of deleting a property or a node. > > You can not delete a property or a node in an overlay dtb. Though you can add/override 'status' with 'status =3D "disabled";' which should be treated very similar to a node not being present. I say similar because it's a source of bugs for the OS to fail to pay attention to status property. Rob