From: vz@mleia.com (Vladimir Zapolskiy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] arm: dts: lpc32xx: fix improper usage of ranges property
Date: Wed, 14 Oct 2015 02:13:49 +0300 [thread overview]
Message-ID: <561D902D.7020503@mleia.com> (raw)
In-Reply-To: <5493797.P10V9v7QAu@wuerfel>
Arnd,
On 13.10.2015 22:36, Arnd Bergmann wrote:
> On Tuesday 13 October 2015 18:51:24 Vladimir Zapolskiy wrote:
>> On 13.10.2015 15:44, Arnd Bergmann wrote:
>>> I don't get it. What kind of errors do you see? The existing
>>> version looks cleaner than the new one, as it only translates
>>> the MMIO areas that are actually used.
>>>
>>
>> The problem is found when I add PL175 device node to lpc32xx.dtsi and
>> expand the node in my board file. The external memory controller manages
>> up to 4 memory devices, which by means of the controller are mapped into
>> physical memory starting from address 0xe0000000.
>>
>> Below are my declarations, similar to one found in lpc18xx.dtsi.
>>
>> lpc32xx.dtsi change common for all LPC32xx boards:
>>
>> emc: emc at 31080000 {
>> compatible = "arm,pl175", "arm,primecell";
>> reg = <0x31080000 0x1000>;
>> clocks = <&scf LPC32XX_CLK_DDRAM>;
>> clock-names = "mpmcclk";
>>
>> #address-cells = <1>;
>> #size-cells = <1>;
>> ranges = <0 0xe0000000 0x01000000>,
>> <1 0xe1000000 0x01000000>,
>> <2 0xe2000000 0x01000000>,
>> <3 0xe3000000 0x01000000>;
>> status = "disabled";
>> };
>>
>
> Ok, got it.
>
>> Support of EMC device node will be added to lpc32xx.dtsi, when this kind
>> of problem is fixed.
>
> As I see it, the problem is that you now have ranges that are not
> for devices inside of the device but that are external. As the
> memory-controller node needs both its own registers and the translation
> for the external ones, we unfortunately can't just put it in the root
> node, which would avoid the issue.
>
> Instead, I would suggest adding a range for the 0xe0000000 area.
Ok, practically it should work for my purposes, but the change must be
done along with added EMC device node description.
I'm not so confident that it is correct to add description of static
memory banks to ahb node though, please give me a short confirmation,
then I'll send a change for inclusion of EMC description -- the one
above excluding clocks and clock-names properties, work on CCF is in
progress.
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2015-10-13 23:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 23:54 [PATCH 0/5] arm: dts: lpc32xx: fixes and updates to lpc32xx.dtsi Vladimir Zapolskiy
2015-10-12 23:54 ` [PATCH 1/5] arm: dts: lpc32xx: change include syntax to be C preprocessor friendly Vladimir Zapolskiy
2015-10-12 23:54 ` [PATCH 2/5] arm: dts: lpc32xx: fix improper usage of ranges property Vladimir Zapolskiy
2015-10-13 12:44 ` Arnd Bergmann
2015-10-13 15:51 ` Vladimir Zapolskiy
2015-10-13 19:36 ` Arnd Bergmann
2015-10-13 23:13 ` Vladimir Zapolskiy [this message]
2015-10-14 13:52 ` Arnd Bergmann
2015-10-14 14:07 ` Vladimir Zapolskiy
2015-10-14 14:13 ` Arnd Bergmann
2015-10-14 17:23 ` Joachim Eastwood
2015-10-14 20:07 ` Arnd Bergmann
2015-10-14 21:15 ` Joachim Eastwood
2015-10-12 23:54 ` [PATCH 3/5] arm: dts: lpc32xx: add labels to all defined peripheral nodes Vladimir Zapolskiy
2015-10-12 23:54 ` [PATCH 4/5] arm: dts: lpc32xx: remove unneeded cell settings from cpus Vladimir Zapolskiy
2015-10-13 8:18 ` Joachim Eastwood
2015-10-13 10:03 ` Vladimir Zapolskiy
2015-10-13 16:20 ` [PATCH v2 4/5] arm: dts: lpc32xx: add reg property to cpu device node Vladimir Zapolskiy
2015-10-12 23:54 ` [PATCH 5/5] arm: dts: lpc32xx: add device node for the second pwm controller Vladimir Zapolskiy
2015-10-14 18:04 ` Joachim Eastwood
2015-10-15 10:25 ` Vladimir Zapolskiy
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=561D902D.7020503@mleia.com \
--to=vz@mleia.com \
--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).