From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752807AbaKJMbX (ORCPT ); Mon, 10 Nov 2014 07:31:23 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:51828 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752553AbaKJMbU (ORCPT ); Mon, 10 Nov 2014 07:31:20 -0500 Date: Mon, 10 Nov 2014 13:31:18 +0100 From: Pavel Machek To: pali.rohar@gmail.com, sre@debian.org, sre@ring0.de, kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, tony@atomide.com, khilman@kernel.org, aaro.koskinen@iki.fi, freemangordon@abv.bg Subject: Tiny dts change breaks boot on n900 Message-ID: <20141110123118.GA31134@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi! I'm confused: This fixes boot on n900. Strange thing is ... adp1653 driver is not even compiled in -- it is module. It looks like tiny change in dts noone should care about breaks boot... I don't even have adp1653 device parsing code written. Something similar happened before -- change in device tree order broke boot. Any ideas? What is going on? Pavel diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts index f3118bf..557a19e 100644 --- a/arch/arm/boot/dts/omap3-n900.dts +++ b/arch/arm/boot/dts/omap3-n900.dts @@ -565,11 +565,6 @@ adp1653: adp1653@30 { compatible = "ad,adp1653"; reg = <0x30>; - - max-flash-timeout-usec = <500000>; - max-flash-intensity-mA = <0>; - max-torch-intensity-mA = <0>; - max-indicator-intensity-uA = <0>; }; }; -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html