From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/3] mfd: db8500-prcmu: Fetch the PRCMU TCDM base address from Device Tree
Date: Tue, 26 Mar 2013 08:17:04 +0000 [thread overview]
Message-ID: <20130326081704.GB11734@gmail.com> (raw)
In-Reply-To: <CACRpkdbn4WARSp7_MUpCZTghTrsPYvsa9GEUC31T7nP_=9oZag@mail.gmail.com>
On Mon, 25 Mar 2013, Linus Walleij wrote:
> On Mon, Mar 25, 2013 at 5:46 PM, Lee Jones <lee.jones@linaro.org> wrote:
>
> >> > res = platform_get_resource_byname(pdev, IORESOURCE_MEM,
> >> > "prcmu-tcpm");
> >> > if (!res) {
> >> > - dev_err(&pdev->dev,
> >> > - "Error: no prcmu tcpm memory region provided\n");
> >> > - return;
> >> > - }
> >> > - tcpm_base = ioremap(res->start, resource_size(res));
> >> > + if (np) {
> >> > + tcpm_np = of_find_node_by_name(np->parent,
> >> > + "prcmu-tcpm-per4");
> >> > + if (!tcpm_np) {
> >> > + dev_err(&pdev->dev,
> >> > + "no prcmu tcpm mem region provided\n");
> >> > + return;
> >> > + }
> >> > + tcpm_base = of_iomap(tcpm_np, 0);
> >> > + }
> >> > + } else
> >> > + tcpm_base = ioremap(res->start, resource_size(res));
> >> > +
> >>
> >> Why don't you just add these extra registers to the prcmu node itself like
> >>
> >> diff --git a/arch/arm/boot/dts/dbx5x0.dtsi b/arch/arm/boot/dts/dbx5x0.dtsi
> >> index 9de9309..6ee6c31 100644
> >> --- a/arch/arm/boot/dts/dbx5x0.dtsi
> >> +++ b/arch/arm/boot/dts/dbx5x0.dtsi
> >> @@ -191,8 +191,8 @@
> >>
> >> prcmu: prcmu at 80157000 {
> >> compatible = "stericsson,db8500-prcmu";
> >> - reg = <0x80157000 0x1000>;
> >> - reg-names = "prcmu";
> >> + reg = <0x80157000 0x1000>, <0x801b0000 0x1000>, <0x801b8000 0x1000>;
> >> + reg-names = "prcmu", "prcmu-tcpm", "prcmu-tcdm-per4";
> >> interrupts = <0 47 0x4>;
> >> #address-cells = <1>;
> >> #size-cells = <1>;
> >>
> >>
> >> and document those in the prcmu binding?
> >>
> >> That would keep the code simpler and the same for both cases.
> >
> > I'm not sure you can. These addresses differ from platform to
> > platform, so I'd need to provide the base PRCMU address in
> > dbx5x0.dtsi, then the other two in the dts files. Can you do that?
>
> Better ask on devicetree-discuss.
>
> What it reflects are differences between SoC:s, so I think the
> right solution is to split it in a three-layer cake:
>
> dbx5x0.dtsi -> included by
> db8500.dtsi -> included by
> snowball/hrefv60plus.dts
>
> dbx5x0.dtsi -> included by
> dbx540.dtsi -> included by
> ccu9540/ccu8540.dts
>
> Here you may insert the reg property into the node at the
> db8500.dtsi or dbx540.dtsi layer.
It's easy done, if that's the right way.
> If you prefer I can cook a patch...
... and I'm fine to do it.
[5 mins later]
Hmm... it appears that in STE's kernel, the same address is used for
all SoCs:
#define U8500_PRCMU_TCDM_BASE (U8500_PER4_BASE + 0x68000)
However, in Mainline there is another definition:
#define U9540_PRCMU_TCDM_BASE (U8500_PER4_BASE + 0x6A000)
... which doesn't seem to be in use anywhere - even for the u9540.
What's the deal big-man?
--
Lee Jones
Linaro ST-Ericsson Landing Team Lead
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-03-26 8:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 15:02 [PATCH 1/3] ARM: ux500: Add device nodes for TCDM and TCPM memory locations Lee Jones
2013-03-25 15:02 ` [PATCH 2/3] mfd: db8500-prcmu: Fetch the PRCMU TCDM base address from Device Tree Lee Jones
2013-03-25 15:32 ` Lee Jones
2013-03-25 15:40 ` Arnd Bergmann
2013-03-25 16:46 ` Lee Jones
2013-03-25 21:32 ` Linus Walleij
2013-03-26 8:17 ` Lee Jones [this message]
2013-03-26 9:11 ` Linus Walleij
2013-03-26 9:48 ` Lee Jones
2013-03-26 10:00 ` Arnd Bergmann
2013-03-26 10:19 ` Lee Jones
2013-03-25 15:02 ` [PATCH 3/3] mfd: db8500-prcmu: Fetch the PRCMU TCPM " Lee Jones
2013-03-25 15:31 ` Lee Jones
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=20130326081704.GB11734@gmail.com \
--to=lee.jones@linaro.org \
--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).