From: sudeep.holla@arm•com (Sudeep Holla)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2] ARM: vexpress: Add unified-cache Device Tree property
Date: Thu, 30 Apr 2015 18:45:10 +0100 [thread overview]
Message-ID: <55426A26.9060704@arm.com> (raw)
In-Reply-To: <20150430133011.GE15254@pengutronix.de>
On 30/04/15 14:30, Robert Schwebel wrote:
> Hi Liviu,
>
> On Thu, Apr 30, 2015 at 12:08:53PM +0100, Liviu Dudau wrote:
>> Sorry Robert, this fell through the cracks. VExpress gets very few
>> patches in general and we're new to this :(
>
> Thanks for the help!
>
> I still see these errors with 4.1-rc1:
>
> [ 0.000000] L2C: platform modifies aux control register: 0x02020000 -> 0x02420000
> [ 0.000000] L2C: DT/platform modifies aux control register: 0x02020000 -> 0x02420000
> [ 0.268626] platform 10000000.sysreg: Error -2 creating of_node link
> [ 0.271997] platform basic-mmio-gpio.1.auto: Error -2 creating of_node link
> [ 0.272266] platform basic-mmio-gpio.2.auto: Error -2 creating of_node link
> [ 0.272681] platform basic-mmio-gpio.3.auto: Error -2 creating of_node link
OK, I was able to debug this, it boils down to initcall ordering.
Both of_init where the firmware sysfs is initialized and
vexpress_sysreg_init are at same core_initcall level. Needs some
thinking and more time to fix this.
Regards,
Sudeep
next prev parent reply other threads:[~2015-04-30 17:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 18:31 [PATCH] ARM: vexpress: Add unified-cache Device Tree property Robert Schwebel
2015-03-18 9:21 ` Sudeep Holla
2015-03-18 9:29 ` Robert Schwebel
2015-03-18 9:34 ` [PATCH v2] " Robert Schwebel
2015-04-29 19:12 ` Robert Schwebel
2015-04-30 11:08 ` Liviu Dudau
2015-04-30 13:30 ` Robert Schwebel
2015-04-30 13:45 ` Liviu Dudau
2015-04-30 13:50 ` Sudeep Holla
2015-04-30 14:11 ` Robert Schwebel
2015-04-30 14:14 ` Sudeep Holla
2015-04-30 17:45 ` Sudeep Holla [this message]
2015-05-16 20:13 ` Robert Schwebel
2015-05-18 8:58 ` Sudeep Holla
2015-05-21 12:26 ` Robert Schwebel
2015-05-22 6:18 ` Robert Schwebel
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=55426A26.9060704@arm.com \
--to=sudeep.holla@arm$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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