From: "Grant Likely" <grant.likely@secretlab.ca>
To: Nick <ndroogh@rogers.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: DTS question - MPC5200b
Date: Tue, 12 Feb 2008 11:28:01 -0700 [thread overview]
Message-ID: <fa686aa40802121028l75c1a150obea8a72975af121a@mail.gmail.com> (raw)
In-Reply-To: <47B1D943.6020708@rogers.com>
On Feb 12, 2008 10:37 AM, Nick <ndroogh@rogers.com> wrote:
> Hi,
>
> I need some help. I am trying to access timer 7 on the MPC5200B
> processor. I have the DTS file setup like this
>
> gpt@670 { // General Purpose Timer
> device_type = "gpt";
> compatible = "fsl,mpc5200b-gpt","fsl,mpc5200-gpt";
> cell-index = <7>;
> reg = <670 10>;
> interrupts = <1 10 0>;
> interrupt-parent = <&mpc5200_pic>;
> };
>
> I have timers 0 to 6 defined the same way except the cell-index reflects
> the timer number.
>
> In my platform file where I am doing my board setup, I tried the following.
>
> timer7 = mpc52xx_find_and_map ("mpc5200b-gpt");
Don't use find_and_map; it was a stupid API that I never should have written.
Instead, use for_each_compatible_node() or for_each_matching_node() to
iterate over them until you find the one with the correct reg address.
Then you can use of_iomap() to map the device registers.
> How do I specify the timer based on the cell-index?
Match on the reg property instead of cell-index; I'll probably be
dropping the cell-index property from future 5200 device trees because
it just ends up duplicating information already provided by reg.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-02-12 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 17:37 DTS question - MPC5200b Nick
2008-02-12 18:07 ` Jarno Manninen
2008-02-12 19:47 ` Grant Likely
2008-02-12 18:28 ` Grant Likely [this message]
2008-02-12 22:49 ` David Gibson
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=fa686aa40802121028l75c1a150obea8a72975af121a@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=ndroogh@rogers.com \
/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).