From: bhupesh.sharma@freescale.com (Bhupesh Sharma)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] ARM64: Update support for FSL's LS2085A SoC
Date: Wed, 1 Apr 2015 17:10:54 +0530 [thread overview]
Message-ID: <1427888463-29549-1-git-send-email-bhupesh.sharma@freescale.com> (raw)
This patchset updates the support for FSL's LS2085A SoC which is based on
ARMv8 architecture:
- Updates the support of various peripherals (PMU, Watchdog, SMMU,
SPI, etc.) present on FSL LS2085a SoC in the SoC DTSI.
- Updates the DTS LS2085a simulator platform to reflect the new
peripherals added in the DTSI.
- Adds new DTS files for LS2085a based QDS and RDB boards.
Rebased against arm-soc git tree, branch: next/dt
Further details of the LS2085a based platforms can be seen here:
http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=LS2085A
Note:
-----
I get a checkpatch warning for the amba-bus compatible string
being missing from Documentation/devicetree/bindings/ . I am not aware
if some patch is already being worked on, to solve the same:
compatible = "arm,amba-bus";
If not, I can try to send a patch, with the re-spin of this patchset.
Bhupesh Sharma (7):
Documentation: DT: Add entry for FSL LS2085A QDS and RDB boards
doc/bindings: Update PCIe devicetree binding documentation for
LS2085A
doc/bindings: Update clk-qoriq bindings for FSL's chassis-3.0 SoCs
dts/ls2085a: Update DTSI to add support of various peripherals
dts/ls2085a: Update Simulator DTS to add support of various
peripherals
dts/ls2085a: Add DTS support for LS2085a QDS & RDB boards
dts/Makefile: Add build support for LS2085a QDS & RDB board DTS
Wang Dongsheng (1):
layerscape/ftm: Add compatible string for FTM0 be used as alarm
timer.
Documentation/devicetree/bindings/arm/fsl.txt | 8 +
.../devicetree/bindings/clock/qoriq-clock.txt | 14 +-
.../devicetree/bindings/pci/layerscape-pci.txt | 3 +-
.../devicetree/bindings/timer/fsl,ftm-timer.txt | 46 +-
arch/arm64/boot/dts/freescale/Makefile | 2 +-
.../{fsl-ls2085a-simu.dts => fsl-ls2085a-qds.dts} | 140 +++++-
.../{fsl-ls2085a-simu.dts => fsl-ls2085a-rdb.dts} | 76 ++-
arch/arm64/boot/dts/freescale/fsl-ls2085a-simu.dts | 40 ++
arch/arm64/boot/dts/freescale/fsl-ls2085a.dtsi | 523 +++++++++++++++++++-
9 files changed, 812 insertions(+), 40 deletions(-)
copy arch/arm64/boot/dts/freescale/{fsl-ls2085a-simu.dts => fsl-ls2085a-qds.dts} (51%)
copy arch/arm64/boot/dts/freescale/{fsl-ls2085a-simu.dts => fsl-ls2085a-rdb.dts} (69%)
--
1.7.9.5
next reply other threads:[~2015-04-01 11:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 11:40 Bhupesh Sharma [this message]
2015-04-01 11:40 ` [PATCH 1/8] Documentation: DT: Add entry for FSL LS2085A QDS and RDB boards Bhupesh Sharma
2015-04-01 11:40 ` [PATCH 2/8] doc/bindings: Update PCIe devicetree binding documentation for LS2085A Bhupesh Sharma
2015-04-01 11:48 ` Mark Rutland
2015-04-01 11:52 ` bhupesh.sharma at freescale.com
2015-04-21 5:06 ` Minghuan.Lian at freescale.com
2015-04-01 11:40 ` [PATCH 3/8] doc/bindings: Update clk-qoriq bindings for FSL's chassis-3.0 SoCs Bhupesh Sharma
2015-04-01 11:40 ` [PATCH 4/8] layerscape/ftm: Add compatible string for FTM0 be used as alarm timer Bhupesh Sharma
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=1427888463-29549-1-git-send-email-bhupesh.sharma@freescale.com \
--to=bhupesh.sharma@freescale.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 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).