From: Pavel Machek <pavel@ucw.cz>
To: pali.rohar@gmail.com, sre@debian.org, sre@ring0.de,
kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
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
Date: Mon, 10 Nov 2014 13:31:18 +0100 [thread overview]
Message-ID: <20141110123118.GA31134@amd> (raw)
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
WARNING: multiple messages have this Message-ID (diff)
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: Tiny dts change breaks boot on n900
Date: Mon, 10 Nov 2014 13:31:18 +0100 [thread overview]
Message-ID: <20141110123118.GA31134@amd> (raw)
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 at 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
next reply other threads:[~2014-11-10 12:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 12:31 Pavel Machek [this message]
2014-11-10 12:31 ` Tiny dts change breaks boot on n900 Pavel Machek
2014-11-10 12:58 ` dtb size limit? was " Pavel Machek
2014-11-10 12:58 ` Pavel Machek
2014-11-10 15:09 ` Tony Lindgren
2014-11-10 15:09 ` Tony Lindgren
2014-11-10 15:25 ` Andreas Färber
2014-11-10 15:25 ` Andreas Färber
2014-11-16 8:38 ` Pavel Machek
2014-11-16 8:38 ` Pavel Machek
2014-11-16 9:38 ` Geert Uytterhoeven
2014-11-16 9:38 ` Geert Uytterhoeven
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=20141110123118.GA31134@amd \
--to=pavel@ucw.cz \
--cc=aaro.koskinen@iki.fi \
--cc=freemangordon@abv.bg \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=sre@debian.org \
--cc=sre@ring0.de \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.