From: Javier Martinez Canillas <javier@osg.samsung.com>
To: linux-kernel@vger.kernel.org
Cc: "Pali Rohar" <pali.rohar@gmail.com>,
"Javier Martinez Canillas" <javier@osg.samsung.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
devicetree@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
"Tony Lindgren" <tony@atomide.com>,
"Mark Rutland" <mark.rutland@arm.com>,
linux-omap@vger.kernel.org,
"Russell King" <linux@armlinux.org.uk>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/9] ARM: omap: Add empty chosen node in SoCs top level DTSI
Date: Mon, 19 Dec 2016 11:44:32 -0300 [thread overview]
Message-ID: <1482158681-4530-1-git-send-email-javier@osg.samsung.com> (raw)
Hello Tony,
As discussed in [0], there's a regression when booting a kernel with a DTB
that doesn't have a pre-existing chosen node. This is usually not an issue
for most boards since u-boot creates an empty chosen node if isn't present
in the DTB.
But it can be an issue for others bootloaders as Pali pointed out with the
N9/900/950 phones and the Nokia Loader (NoLo).
This patch series add chosen nodes in the top level DTSI for all OMAP SoCs.
[0]: http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1294379.html
Best regards,
Javier
Javier Martinez Canillas (9):
ARM: dts: omap2: Add an empty chosen node to top level DTSI
ARM: dts: omap3: Add an empty chosen node to top level DTSI
ARM: dts: omap4: Add an empty chosen node to top level DTSI
ARM: dts: omap5: Add an empty chosen node to top level DTSI
ARM: dts: am33xx: Add an empty chosen node to top level DTSI
ARM: dts: am4372: Add an empty chosen node to top level DTSI
ARM: dts: dm814x: Add an empty chosen node to top level DTSI
ARM: dts: dm816x: Add an empty chosen node to top level DTSI
ARM: dts: dra7: Add an empty chosen node to top level DTSI
arch/arm/boot/dts/am33xx.dtsi | 1 +
arch/arm/boot/dts/am4372.dtsi | 1 +
arch/arm/boot/dts/dm814x.dtsi | 1 +
arch/arm/boot/dts/dm816x.dtsi | 1 +
arch/arm/boot/dts/dra7.dtsi | 1 +
arch/arm/boot/dts/omap2.dtsi | 1 +
arch/arm/boot/dts/omap3.dtsi | 1 +
arch/arm/boot/dts/omap4.dtsi | 1 +
arch/arm/boot/dts/omap5.dtsi | 1 +
9 files changed, 9 insertions(+)
--
2.7.4
next reply other threads:[~2016-12-19 14:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 14:44 Javier Martinez Canillas [this message]
2016-12-19 14:44 ` [PATCH 1/9] ARM: dts: omap2: Add an empty chosen node to top level DTSI Javier Martinez Canillas
2016-12-19 14:44 ` [PATCH 2/9] ARM: dts: omap3: " Javier Martinez Canillas
2017-01-02 18:01 ` Pali Rohár
2016-12-19 14:44 ` [PATCH 3/9] ARM: dts: omap4: " Javier Martinez Canillas
2016-12-19 14:44 ` [PATCH 4/9] ARM: dts: omap5: " Javier Martinez Canillas
2016-12-19 14:44 ` [PATCH 5/9] ARM: dts: am33xx: " Javier Martinez Canillas
2016-12-19 14:44 ` [PATCH 6/9] ARM: dts: am4372: " Javier Martinez Canillas
2016-12-19 14:44 ` [PATCH 7/9] ARM: dts: dm814x: " Javier Martinez Canillas
2016-12-19 14:44 ` [PATCH 8/9] ARM: dts: dm816x: " Javier Martinez Canillas
2016-12-19 14:44 ` [PATCH 9/9] ARM: dts: dra7: " Javier Martinez Canillas
2016-12-27 17:30 ` [PATCH 0/9] ARM: omap: Add empty chosen node in SoCs " Tony Lindgren
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=1482158681-4530-1-git-send-email-javier@osg.samsung.com \
--to=javier@osg.samsung.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=pali.rohar@gmail.com \
--cc=robh+dt@kernel.org \
--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 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).