All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2-l0cyMroinI0@public.gmane.org>
To: device-tree <devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org>
Subject: PCIE device tree bindings - Could you help me to understand?
Date: Wed, 6 Mar 2013 13:07:43 -0500	[thread overview]
Message-ID: <513785EF.7000508@ti.com> (raw)

Hello All,

I am working to develop a PCIE driver that requires DT bindings. Could 
someone point me to a documentation or code or explain how to interpret 
the following device tree bindings. I understand the reg property only. 
There is outbound PCIE memory and inbound PCIE memory. But can't 
understand the below bindings for the same. Also how the interrupt 
mapping works? Below dts bindings is copied from 
powerpc/boot/dts/ep405.dts. Surprisingly I am not seeing any example 
pcie bindings on ARM architecture even though there PCI or PCIE drivers 
available on ARM. Your help is appreciated.

                 PCI0: pci@ec000000 {
                         device_type = "pci";
                         #interrupt-cells = <1>;
                         #size-cells = <2>;
                         #address-cells = <3>;
                         compatible = "ibm,plb405gp-pci", "ibm,plb-pci";
                         primary;
                         reg = <0xeec00000 0x00000008    /* Config space 
access */
                                0xeed80000 0x00000004    /* IACK */
                                0xeed80000 0x00000004    /* Special cycle */
                                0xef480000 0x00000040>;  /* Internal 
registers */

                         /* Outbound ranges, one memory and one IO,
                          * later cannot be changed. Chip supports a second
                          * IO range but we don't use it for now
                          */
                         ranges = <0x02000000 0x00000000 0x80000000 
0x80000000 0x00000000 0x20000000
                                   0x01000000 0x00000000 0x00000000 
0xe8000000 0x00000000 0x00010000>;

                         /* Inbound 2GB range starting at 0 */
                         dma-ranges = <0x42000000 0x0 0x0 0x0 0x0 
0x80000000>;

                         /* That's all I know about IRQs on that thing 
... */
                         interrupt-map-mask = <0xf800 0x0 0x0 0x0>;
                         interrupt-map = <
                                 /* USB */
                                 0x7000 0x0 0x0 0x0 &UIC0 0x1e 0x8 /* 
IRQ5 */
                         >;
                 };

             reply	other threads:[~2013-03-06 18:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06 18:07 Murali Karicheri [this message]
     [not found] ` <513785EF.7000508-l0cyMroinI0@public.gmane.org>
2013-03-07  9:34   ` PCIE device tree bindings - Could you help me to understand? Prabhakar Lad
     [not found]     ` <CA+V-a8vY_qfh0-4yyFW4JgWanjycPcbc1LzgL2HhQVEzwxOHMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-03-07 15:01       ` Murali Karicheri

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=513785EF.7000508@ti.com \
    --to=m-karicheri2-l0cymroini0@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.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.