From: Tabi Timur-B04825 <B04825@freescale.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH][v2] powerpc/85xx: Rework P1022DS device tree
Date: Thu, 17 Nov 2011 16:04:00 +0000 [thread overview]
Message-ID: <CAOZdJXW9Ygz9nMmXgV_GaTPEQHi0zHB7d7uBAPV4fN7-p+ST-Q@mail.gmail.com> (raw)
In-Reply-To: <1321540377-3672-1-git-send-email-galak@kernel.crashing.org>
On Thu, Nov 17, 2011 at 8:32 AM, Kumar Gala <galak@kernel.crashing.org> wro=
te:
> Utilize new split between board & SoC, and new SoC device trees split
> into pre & post utilizing 'template' includes for SoC IP blocks.
>
> Other changes include:
>
> * Reworked PCIe nodes to allow supportin IRQs for controller (errors)
> =A0and moved PCI device IRQs down to virtual bridge level
> * Changed GPIO compatiable from 'fsl,mpc8572-gpio' to 'fsl,pq3-gpio' as t=
he
> =A0'mpc8572' compatiable is to deal with a 'mpc8572' specific to an errat=
um
> * Updated spi node to new espi binding specification
> * Renamed SDHC node from 'sdhci' to 'sdhc'
> * Added usb node for 2nd usb controller
> * Dropping "fsl,p1022-IP..." from compatibles for standard blocks
> * Fixed bug in local bus range node for CS2, was maping to
> =A00x0 0x0xffa00000 instead of 0xf 0xffa00000
> * Fixed localbus reg property should have been 0xf 0xffe05000
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> v2: fixed localbus reg property
Acked-by: Timur Tabi <timur@freescale.com>
--=20
Timur Tabi
Linux kernel developer at Freescale=
next prev parent reply other threads:[~2011-11-17 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 14:32 [PATCH][v2] powerpc/85xx: Rework P1022DS device tree Kumar Gala
2011-11-17 14:32 ` [PATCH][v2] powerpc/85xx: Rework P2041RDB " Kumar Gala
2011-11-17 16:04 ` Tabi Timur-B04825 [this message]
2011-11-17 16:55 ` [PATCH][v2] powerpc/85xx: Rework P1022DS " Kumar Gala
2011-11-17 16:58 ` Timur Tabi
2011-12-06 22:44 ` Tabi Timur-B04825
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=CAOZdJXW9Ygz9nMmXgV_GaTPEQHi0zHB7d7uBAPV4fN7-p+ST-Q@mail.gmail.com \
--to=b04825@freescale.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).