From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] arm64: dts: add QorIQ LS1046A SoC support
Date: Fri, 08 Jul 2016 14:00:12 +0200 [thread overview]
Message-ID: <1984740.gmAYAJ1bIT@wuerfel> (raw)
In-Reply-To: <1467972944-12293-2-git-send-email-shh.xie@gmail.com>
On Friday, July 8, 2016 6:15:40 PM CEST shh.xie at gmail.com wrote:
> +
> + memory at 80000000 {
> + device_type = "memory";
> + reg = <0x0 0x80000000 0 0x80000000>;
> + /* DRAM space 1, size: 2GiB DRAM */
> + };
The memory size is usually in the .dts file, unless this is on-chip
eDRAM.
> + clockgen: clocking at 1ee1000 {
> + compatible = "fsl,ls1046a-clockgen";
> + scfg: scfg at 1570000 {
> + compatible = "fsl,ls1046a-scfg", "syscon";
> + dcfg: dcfg at 1ee0000 {
> + compatible = "fsl,ls1046a-dcfg", "syscon";
None of the fsl,ls1046a-* devices seem to have any binding documentation.
> + wdog0: wdog at 2ad0000 {
watchdog at 2ad0000
> + usb0: usb3 at 2f00000 {
usb at 2f00000
> + pcie at 3400000 {
> + compatible = "fsl,ls1046a-pcie", "snps,dw-pcie";
> + reg = <0x00 0x03400000 0x0 0x00100000 /* controller registers */
> + 0x40 0x00000000 0x0 0x00002000>; /* configuration space */
> + reg-names = "regs", "config";
> + interrupts = <0 118 0x4>, /* controller interrupt */
> + <0 117 0x4>; /* PME interrupt */
> + interrupt-names = "intr", "pme";
> + #address-cells = <3>;
> + #size-cells = <2>;
> + device_type = "pci";
> + num-lanes = <4>;
> + bus-range = <0x0 0xff>;
> + ranges = <0x81000000 0x0 0x00000000 0x40 0x00010000 0x0 0x00010000 /* downstream I/O */
> + 0x82000000 0x0 0x40000000 0x40 0x40000000 0x0 0x40000000>; /* non-prefetchable memory */
No prefetchable memory area?
> + msi-parent = <&msi>;
You seem to have a gic-400, could you use that as the MSI sink instead?
> + #interrupt-cells = <1>;
> + interrupt-map-mask = <0 0 0 7>;
> + interrupt-map = <0000 0 0 1 &gic 0 110 0x4>,
> + <0000 0 0 2 &gic 0 110 0x4>,
> + <0000 0 0 3 &gic 0 110 0x4>,
> + <0000 0 0 4 &gic 0 110 0x4>;
> + };
>
If the four interrupts are all the same, why do you have separate entries?
Arnd
next prev parent reply other threads:[~2016-07-08 12:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 10:15 [PATCH 0/5] arm64: dts: add QorIQ LS1046A SoC and boards support shh.xie at gmail.com
2016-07-08 10:15 ` [PATCH 1/5] arm64: dts: add QorIQ LS1046A SoC support shh.xie at gmail.com
2016-07-08 12:00 ` Arnd Bergmann [this message]
2016-08-18 10:27 ` Shaohui Xie
2016-08-23 10:04 ` Arnd Bergmann
2016-07-08 10:15 ` [PATCH 2/5] Documentation: DT: Add entry for QorIQ LS1046A-RDB board shh.xie at gmail.com
2016-07-16 0:08 ` Rob Herring
2016-07-08 10:15 ` [PATCH 3/5] arm64: dts: add LS1046A-RDB board support shh.xie at gmail.com
2016-07-08 10:15 ` [PATCH 4/5] Documentation: DT: Add entry for QorIQ LS1046A-QDS board shh.xie at gmail.com
2016-07-16 0:09 ` Rob Herring
2016-07-08 10:15 ` [PATCH 5/5] arm64: dts: add LS1046A-QDS board support shh.xie at gmail.com
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=1984740.gmAYAJ1bIT@wuerfel \
--to=arnd@arndb.de \
--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