From: Simon Horman <horms+renesas@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Renesas ARM Based SoC GIC Cleanup for v4.5
Date: Fri, 18 Dec 2015 02:30:41 +0000 [thread overview]
Message-ID: <cover.1450401902.git.horms+renesas@verge.net.au> (raw)
Hi Olof, Hi Kevin, Hi Arnd,
Please consider these Renesas ARM based SoC GIC cleanup for v4.5.
This pull-request includes staging-board changes which have been
acked by Greg Kroah-Hartman. They are bundled into this pull-request
as not-doing so would break the drivers they update.
The following changes since commit 8005c49d9aea74d382f474ce11afbbc7d7130bec:
Linux 4.4-rc1 (2015-11-15 17:00:27 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas.git tags/renesas-gic-cleanup-for-v4.5
for you to fetch changes up to 1474136ce6a457a10a797b3de04adbb035e90901:
staging: board: armadillo800eva: Use "arm,pl390" (2015-12-18 10:21:10 +0900)
----------------------------------------------------------------
Renesas ARM Based SoC GIC Cleanup for v4.5
On several Renesas ARM SoCs, the GIC is described in DT as being a
Cortex A9 GIC, while it's actually a PL390. This is not only stated in
the documentation, but has been verified by reading the GICD_IIDR
register.
To correct this:
1. Update the DT compatible value to match reality,
2. Update the board staging drivers to match the above.
----------------------------------------------------------------
Geert Uytterhoeven (6):
ARM: shmobile: r7s72100 dtsi: Use "arm,pl390" for GIC
ARM: shmobile: r8a7740 dtsi: Use "arm,pl390" for GIC
ARM: shmobile: emev2 dtsi: Use "arm,pl390" for GIC
ARM: shmobile: r8a7778 dtsi: Use "arm,pl390" for GIC
staging: board: kzm9d: Use "arm,pl390"
staging: board: armadillo800eva: Use "arm,pl390"
arch/arm/boot/dts/emev2.dtsi | 2 +-
arch/arm/boot/dts/r7s72100.dtsi | 2 +-
arch/arm/boot/dts/r8a7740.dtsi | 2 +-
arch/arm/boot/dts/r8a7778.dtsi | 2 +-
drivers/staging/board/armadillo800eva.c | 2 +-
drivers/staging/board/kzm9d.c | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
next reply other threads:[~2015-12-18 2:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 2:30 Simon Horman [this message]
2015-12-18 2:30 ` [PATCH 1/6] ARM: shmobile: r7s72100 dtsi: Use "arm,pl390" for GIC Simon Horman
2015-12-18 2:30 ` [PATCH 2/6] ARM: shmobile: r8a7740 " Simon Horman
2015-12-18 2:30 ` [PATCH 3/6] ARM: shmobile: emev2 " Simon Horman
2015-12-18 2:30 ` [PATCH 4/6] ARM: shmobile: r8a7778 " Simon Horman
2015-12-18 2:30 ` [PATCH 5/6] staging: board: kzm9d: Use "arm,pl390" Simon Horman
2015-12-18 2:30 ` [PATCH 6/6] staging: board: armadillo800eva: " Simon Horman
2015-12-22 20:55 ` [GIT PULL] Renesas ARM Based SoC GIC Cleanup for v4.5 Olof Johansson
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=cover.1450401902.git.horms+renesas@verge.net.au \
--to=horms+renesas@verge.net.au \
--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;
as well as URLs for NNTP newsgroup(s).