Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753515AbeAFAtQ (ORCPT + 1 other); Fri, 5 Jan 2018 19:49:16 -0500 Received: from mail-pf0-f194.google.com ([209.85.192.194]:46165 "EHLO mail-pf0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753289AbeAFAsJ (ORCPT ); Fri, 5 Jan 2018 19:48:09 -0500 X-Google-Smtp-Source: ACJfBouN5ePhQTKu61ghiq1l1gqjaEHtPGurugXs4mJN6jspiJUZLtTyQAZQawlCov3zlIYnUKpu+A== From: Brian Norris To: Heiko Stuebner , Thierry Reding , Jonathan Hunter Cc: , linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, linux-tegra@vger.kernel.org, Lin Huang , Brian Norris Subject: [PATCH 2/3] ARM: tegra: paz00: drop nonstandard 'backlight-boot-off' Date: Fri, 5 Jan 2018 16:47:56 -0800 Message-Id: <20180106004757.8239-2-briannorris@chromium.org> X-Mailer: git-send-email 2.16.0.rc0.223.g4a4ac83678-goog In-Reply-To: <20180106004757.8239-1-briannorris@chromium.org> References: <20180106004757.8239-1-briannorris@chromium.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: This was used out-of-tree as a hack for resolving issues where some systems expect the backlight to turn on automatically at boot, while others expect to manage the backlight status via a DRM/panel driver. Those issues have since been fixed upstream in pwm_bl.c without device tree hacks, and so this un-documented property should no longer be useful. Signed-off-by: Brian Norris --- arch/arm/boot/dts/tegra20-paz00.dts | 2 -- 1 file changed, 2 deletions(-) diff --git a/arch/arm/boot/dts/tegra20-paz00.dts b/arch/arm/boot/dts/tegra20-paz00.dts index 30436969adc0..12c63b23ed5e 100644 --- a/arch/arm/boot/dts/tegra20-paz00.dts +++ b/arch/arm/boot/dts/tegra20-paz00.dts @@ -504,8 +504,6 @@ brightness-levels = <0 16 32 48 64 80 96 112 128 144 160 176 192 208 224 240 255>; default-brightness-level = <10>; - - backlight-boot-off; }; clocks { -- 2.16.0.rc0.223.g4a4ac83678-goog