From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: Identifying Primecells
Date: Fri, 23 Sep 2011 08:30:36 -0500 [thread overview]
Message-ID: <4E7C89FC.4090209@gmail.com> (raw)
In-Reply-To: <CAKON4OzGEo+XvcNg=mzp3jhq3d3m7Z9bvZTSVCNLNjZ=KYbNBQ@mail.gmail.com>
On 09/23/2011 08:11 AM, jonsmirl at gmail.com wrote:
> On Fri, Sep 23, 2011 at 8:46 AM, Rob Herring <robherring2@gmail.com> wrote:
>> On 09/22/2011 01:19 PM, jonsmirl at gmail.com wrote:
>>> I'm working on device tree support for the NXP LPC3130. To do this
>>> right I need to know what specific Primecells were used in the chip.
>>> How do I identify the primecell numbers for the devices? It is a
>>> 926ejs core.
>>>
>>
>> I'm not sure I understand the question.
>>
>> The primecell periph id numbers are only in the DT if they are wrong in
>> the h/w for some reason. The compatible property should contain the
>> device model number (i.e. "arm,pl011" for the uart).
>
> So how do I figure out which id numbers to use for the NXP LPC3130?
> Is the UART a pl011?
>
The chip's documentation or ARM's documentation. The existing board
code. Read each periph ID register.
Or the ones with drivers in the kernel:
find drivers -name '*pl[0-3]*'
Rob
next prev parent reply other threads:[~2011-09-23 13:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 18:19 Identifying Primecells jonsmirl at gmail.com
2011-09-23 12:46 ` Rob Herring
2011-09-23 13:11 ` jonsmirl at gmail.com
2011-09-23 13:30 ` Rob Herring [this message]
2011-09-23 13:35 ` jonsmirl at gmail.com
2011-09-23 14:10 ` Pawel Moll
2011-09-23 14:17 ` jonsmirl at gmail.com
2011-09-23 14:22 ` jonsmirl at gmail.com
2011-09-23 14:22 ` Pawel Moll
2011-09-23 19:11 ` jonsmirl at gmail.com
2011-09-24 13:27 ` Linus Walleij
2011-09-24 23:15 ` Vitaly Wool
2011-09-25 3:03 ` jonsmirl at gmail.com
2011-09-23 19:53 ` Russell King - ARM Linux
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=4E7C89FC.4090209@gmail.com \
--to=robherring2@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.