From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: BCM5301X: DT changes for v3.19
Date: Thu, 20 Nov 2014 10:38:06 +0100 [thread overview]
Message-ID: <201411201038.07191.arnd@arndb.de> (raw)
In-Reply-To: <546299BC.4060704@hauke-m.de>
On Wednesday 12 November 2014, Hauke Mehrtens wrote:
> ARM: BCM5301X: Add some more devices to device tree
>
> The most important part is adding the axi bus to the SoC dtsi file,
> this is the main bus on the SoC.
>
> These patches were all send to the arm list and I haven't got any
> negative responses.
>
> ----------------------------------------------------------------
> Hauke Mehrtens (1):
> ARM: BCM5301X: activate early printk for Netgear R6250
>
> Rafa? Mi?ecki (2):
> ARM: BCM5301X: Add Broadcom's bus-axi to the DTS file
> ARM: BCM5301X: Add LEDs for Netgear R6250 V1
>
Same comments as for the SoC changes. Note that in general, enabling
'earlyprintk' in the dts is a bad idea because it breaks booting a
kernel that has an incompatible debug_ll setting enabled, I'd rather
see you drop that patch.
Starting with 3.19, the shiny new 'earlycon' support should work, so
I'd prefer you to set the 'stdout-path' property in the /chosen
node. Unfortunately enabling earlycon at the command line is still
broken on 3.18-rc because the fixmap patches are only in Russell's
'ronx-next' branch. We could think about pulling that into arm-soc
if we want to start enabling earlycon drivers.
Arnd
next prev parent reply other threads:[~2014-11-20 9:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 23:20 [GIT PULL] ARM: BCM5301X: DT changes for v3.19 Hauke Mehrtens
2014-11-20 9:38 ` Arnd Bergmann [this message]
2014-11-20 21:17 ` Hauke Mehrtens
2014-11-27 17:03 ` Arnd Bergmann
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=201411201038.07191.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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