openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: rentao.bupt@gmail.com
To: Rob Herring <robh+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
	Andrew Jeffery <andrew@aj.id.au>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
	openbmc@lists.ozlabs.org, taoren@fb.com
Cc: Tao Ren <rentao.bupt@gmail.com>
Subject: [PATCH 2/4] ARM: dts: aspeed: wedge40: Remove redundant ADC device
Date: Sun, 18 Jul 2021 17:17:22 -0700	[thread overview]
Message-ID: <20210719001724.6410-3-rentao.bupt@gmail.com> (raw)
In-Reply-To: <20210719001724.6410-1-rentao.bupt@gmail.com>

From: Tao Ren <rentao.bupt@gmail.com>

Remove ADC device from wedge40 device tree because the device is already
enabled in "ast2400-facebook-netbmc-common.dtsi".

Signed-off-by: Tao Ren <rentao.bupt@gmail.com>
---
 arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts b/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts
index 2dcfeae3c92a..6624855d8ebd 100644
--- a/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts
+++ b/arch/arm/boot/dts/aspeed-bmc-facebook-wedge40.dts
@@ -23,10 +23,6 @@
 	status = "disabled";
 };
 
-&adc {
-	status = "okay";
-};
-
 &pwm_tacho {
 	status = "okay";
 	pinctrl-names = "default";
-- 
2.17.1


  parent reply	other threads:[~2021-07-19  0:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  0:17 [PATCH 0/4] ARM: dts: aspeed: Enable ADC for wedge100 BMC rentao.bupt
2021-07-19  0:17 ` [PATCH 1/4] ARM: dts: aspeed: Enable ADC in Facebook AST2400 common dtsi rentao.bupt
2021-07-19  0:17 ` rentao.bupt [this message]
2021-07-19  0:17 ` [PATCH 3/4] ARM: dts: aspeed: galaxy100: Remove redundant ADC device rentao.bupt
2021-07-19  0:17 ` [PATCH 4/4] ARM: dts: aspeed: wedge100: Enable ADC channels rentao.bupt
2021-07-19  0:21 ` [PATCH 0/4] ARM: dts: aspeed: Enable ADC for wedge100 BMC Joel Stanley
2021-07-19  1:03   ` Tao Ren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210719001724.6410-3-rentao.bupt@gmail.com \
    --to=rentao.bupt@gmail.com \
    --cc=andrew@aj.id.au \
    --cc=devicetree@vger.kernel.org \
    --cc=joel@jms.id.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-aspeed@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=openbmc@lists.ozlabs.org \
    --cc=robh+dt@kernel.org \
    --cc=taoren@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).