From: p.fedin@samsung.com (Pavel Fedin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 2/4] ARM: dts: Add SROMc to Exynos 5410
Date: Fri, 30 Oct 2015 13:51:03 +0300 [thread overview]
Message-ID: <00d501d11300$e0b4fb60$a21ef220$@samsung.com> (raw)
In-Reply-To: <56333731.1000400@samsung.com>
Hello!
> >>> + sromc: sromc at 12250000 {
> >>> + #address-cells = <1>;
> >>> + #size-cells = <1>;
> >>> + ranges;
> >>> +
> >>
> >> We do not need to specify these three properties as they are already
> >> present in parent node "soc".
> >
> > We do, otherwise dtc complains about defaults of #address-cells = 2 and #size-cells=1, and
> without empty "ranges" subnode's resources are not correctly translated.
> >
>
> First of all this patch will not give this error. So this part should
> not be a part of this patch.
> You should be getting above error after applying v4 4/4 "ARM: dts: Add
> Ethernet chip to SMDK5410". So if its failing for ethernet subnode, you
> can move this address-cells and size-cells in dts file just above
> ethernet node as shown below:
>
> index 311e7be..d69981d 100644
> --- a/arch/arm/boot/dts/exynos5410-smdk5410.dts
> +++ b/arch/arm/boot/dts/exynos5410-smdk5410.dts
> @@ -95,6 +95,9 @@
> };
>
> &sromc {
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges;
> pinctrl-names = "default";
> pinctrl-0 = <&srom_ctl>, <&srom_ebi>;
>
IMHO this makes little of sense, because in this case you would have to duplicate these properties for every supported machine. address-cells, size-cells and ranges belong to the controller itself, not to its children.
Of course i could split up the patch into two, first introduce sromc, second introduce mapping. But does it worth that? Both patches would be 3 lines of code each.
Anyway, this specific talk is outdated by now, please check out neighbor topic, we are discussing significantly improved binding with Krzystof.
> And another question still remains open, we can't just like that change
> "smsc,lan9115" binding by adding samsung specific properties.
I am sorry, but you either do not understand us with Krzystof, or not reading at all...
This is not a change in the binding. And these properties do not belong to smsc at all. They would be added to *ANY* device which sits on top of SROMc. This is more like a bus-specific extra. It's similar to "reg" property having different meanings for different buses.
> Probably you can check suggestions from Krzysztof, where he pointed out
> some hint on how other places this is getting used.
Did you read them? I did, and they do exactly the same thing as i do.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-30 10:51 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 12:42 [PATCH v4 0/4] [PATCH v4 0/4] Exynos SROMc configuration and Ethernet support for SMDK5410 Pavel Fedin
2015-10-29 12:42 ` [PATCH v4 1/4] Documentation: dt-bindings: Describe SROMc configuration Pavel Fedin
2015-10-30 6:30 ` Krzysztof Kozlowski
2015-10-30 6:58 ` Pavel Fedin
2015-10-30 7:23 ` Krzysztof Kozlowski
2015-10-30 17:15 ` Rob Herring
2015-11-01 8:15 ` Krzysztof Kozlowski
2015-10-30 10:43 ` Pavel Fedin
2015-11-01 8:48 ` Krzysztof Kozlowski
2015-11-02 7:31 ` Pavel Fedin
2015-11-03 0:16 ` Krzysztof Kozlowski
2015-11-03 6:58 ` Pavel Fedin
2015-11-03 7:18 ` Krzysztof Kozlowski
2015-10-29 12:42 ` [PATCH v4 2/4] ARM: dts: Add SROMc to Exynos 5410 Pavel Fedin
2015-10-29 17:28 ` Pankaj Dubey
2015-10-30 6:41 ` Pavel Fedin
2015-10-30 9:24 ` Pankaj Dubey
2015-10-30 10:51 ` Pavel Fedin [this message]
2015-10-29 12:42 ` [PATCH v4 3/4] drivers: exynos-srom: Add support for bank configuration Pavel Fedin
2015-10-29 12:42 ` [PATCH v4 4/4] ARM: dts: Add Ethernet chip to SMDK5410 Pavel Fedin
2015-10-29 17:40 ` Pankaj Dubey
2015-10-29 17:46 ` [PATCH v4 0/4] [PATCH v4 0/4] Exynos SROMc configuration and Ethernet support for SMDK5410 Pankaj Dubey
2015-10-30 6:43 ` Pavel Fedin
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='00d501d11300$e0b4fb60$a21ef220$@samsung.com' \
--to=p.fedin@samsung.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).