arm64: first set of Kconfig patches for Tegra132 support
Get series with b4
b4 am 20150107142520.GB1621@ulmoVersions newest first
- v1 Latest2 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | arm64: Kconfig: add basic support for the Tegra SoC family and the Tegra132 SoC | +0 | 1 reply | |
| 1/2 | arm64: Kconfig: add basic support for the Tegra SoC family and the Tegra132 SoC | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/2] arm64: first set of Kconfig patches for Tegra132 support
Quoted 21 lines · Will Deacon
Quoted 1 line · Paul Walmsley
Hi Catalin & Will,
Hi Paul,
Quoted 11 lines
These patches start the ARM64
Kconfigand defconfig changes to support the Tegra132 (aka Tegra K1 64-bit) SoC and the NVIDIA Norrin64 FFD board.Tegra132 support is made conditional on
CONFIG_BROKEN, since there are some patches pending for other maintainers to fix compilation whenCONFIG_ARCH_TEGRAis set during an ARM64 build. Once those patches have been merged, a subsequent patch will be sent to remove theCONFIG_BROKENdependency and to make a few other defconfig changes that are dependent onCONFIG_ARCH_TEGRA.Quoted 4 lines
These patches apply on the arm64 fixes/core branch, commit
5d96e0cba263. They have been boot-tested on QEMU 2.2.0 AArch64, and (after other patches have been applied) have been boot-tested on the Tegra132 Norrin64 FFD board.
Quoted 4 lines
Whilst I'm happy to take the second patch for 3.20 (getting those dependencies building and keeping them building is a Good Thing), can we hold off on the first patch until it's not broken? Having an unconditional depends on BROKEN isn't really that useful.
The two patches that require the BROKEN dependency are fairly trivial, so I don't think it would be a stretch to merge them for 3.20. But they apply to different trees (one to the clocksource tree, the other to the Tegra tree).
How do you usually handle the ARM64 patches? Do you manually pick up the patches that touch arch/arm64 or would you prefer for me to collect them in a pull request?
Either way I could probably provide a stable branch for you to pull into the arm64 tree to resolve the build dependencies provided that Daniel or Thomas will ack the clocksource patch.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150107/f54cd099/attachment.sig>