From: hauke@hauke-m.de (Hauke Mehrtens)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/4] ARM: BCM5301X: initial support for the BCM5301X/BCM470X SoCs with ARM CPU
Date: Mon, 06 Jan 2014 00:30:37 +0100 [thread overview]
Message-ID: <52C9EB1D.802@hauke-m.de> (raw)
In-Reply-To: <201401052030.07765.arnd@arndb.de>
On 01/05/2014 08:30 PM, Arnd Bergmann wrote:
> On Sunday 05 January 2014, Hauke Mehrtens wrote:
>> +static void __init bcm5301x_timer_init(void)
>> +{
>> + of_clk_init(NULL);
>> + clocksource_of_init();
>> +}
>> +
>> +static void __init bcm5301x_dt_init(void)
>> +{
>> + l2x0_of_init(0, ~0UL);
>> + of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
>> +}
>
> I'm pretty sure the first of these two functions is no longer needed,
> and there were at least plans to make the second one optional as well.
>
> Can you remove bcm5301x_timer_init() now?
Yes I will remove bcm5301x_timer_init(), but calling l2x0_of_init() is
still needed with kernel 3.13-rc7.
Hauke
next prev parent reply other threads:[~2014-01-05 23:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 17:58 [PATCH v4 0/4] ARM: BCM5301X: initial support for the BCM5301X/BCM470X SoCs with ARM CPU Hauke Mehrtens
2014-01-05 17:58 ` [PATCH v4 1/4] " Hauke Mehrtens
2014-01-05 19:30 ` Arnd Bergmann
2014-01-05 23:30 ` Hauke Mehrtens [this message]
2014-01-05 20:37 ` Alexander Shiyan
2014-01-05 17:58 ` [PATCH v4 2/4] ARM: BCM5301X: add early debugging support Hauke Mehrtens
2014-01-05 17:58 ` [PATCH v4 3/4] ARM: BCM5301X: add dts files for BCM4708 SoC Hauke Mehrtens
2014-01-05 17:58 ` [PATCH v4 4/4] ARM: BCM5301X: workaround suppress fault Hauke Mehrtens
2014-01-05 20:25 ` Arnd Bergmann
2014-01-05 22:29 ` Hauke Mehrtens
2014-01-05 19:52 ` [PATCH v4 0/4] ARM: BCM5301X: initial support for the BCM5301X/BCM470X SoCs with ARM CPU 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=52C9EB1D.802@hauke-m.de \
--to=hauke@hauke-m.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;
as well as URLs for NNTP newsgroup(s).