From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] arm64: Kconfig: add basic support for the Tegra SoC family and the Tegra132 SoC
Date: Wed, 7 Jan 2015 15:20:06 +0100 [thread overview]
Message-ID: <20150107142005.GA1621@ulmo> (raw)
In-Reply-To: <20150107081729.14381.47835.stgit@dusk.lan>
On Wed, Jan 07, 2015 at 01:17:33AM -0700, Paul Walmsley wrote:
> Add basic Kbuild support for the Tegra SoC family, and specifically,
> the Tegra132 SoC. Tegra132 pairs the NVIDIA Denver CPU complex with
> the SoC integration of Tegra124 - hence the use of ARCH_TEGRA and the
> Tegra124 pinctrl option.
>
> For the time being, Tegra ARM64 support is added with a dependency on
> CONFIG_BROKEN. This is temporary and can be removed when the
> following two patches for compilation failures have been merged:
>
> "soc: tegra: pmc: restrict compilation of suspend-related support to ARM"
> https://git.kernel.org/cgit/linux/kernel/git/pjw/tegra-dev.git/commit/?id=053decbf3900d4e8fee799f9a29cf8d905b2fcb1
I think you said you were going to respin this on top of v3.19-rc1, but
the above doesn't seem to be rebased yet. Given that the only comments
were bikeshed from my part, do you have any objections to me taking the
patch and apply the bikeshed myself?
> "clocksource: tegra: wrap arch/arm-specific sections in CONFIG_ARM"
> https://git.kernel.org/cgit/linux/kernel/git/pjw/tegra-dev.git/commit/?id=220aa7fcc74a1a089916be6cb34b0e326f31841f
I don't think I've seen any comments other than mine on this patch.
Given that this patch depends on the above to get rid of the BROKEN
dependency, it might still be preferable to take both via the Tegra
tree. Otherwise we probably have to wait until v3.21 before we can
apply this.
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/f7299807/attachment.sig>
next prev parent reply other threads:[~2015-01-07 14:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 8:17 [PATCH 0/2] arm64: first set of Kconfig patches for Tegra132 support Paul Walmsley
2015-01-07 8:17 ` [PATCH 1/2] arm64: Kconfig: add basic support for the Tegra SoC family and the Tegra132 SoC Paul Walmsley
2015-01-07 14:20 ` Thierry Reding [this message]
2015-01-08 10:37 ` Paul Walmsley
2015-01-08 10:55 ` Thierry Reding
2015-01-07 8:17 ` [PATCH 2/2] arm64: defconfig: add some Kconfig entries used by Tegra132 Norrin FFD board Paul Walmsley
2015-01-07 11:07 ` [PATCH 0/2] arm64: first set of Kconfig patches for Tegra132 support Will Deacon
2015-01-07 14:25 ` Thierry Reding
2015-01-07 14:54 ` Will Deacon
2015-01-07 15:09 ` Catalin Marinas
2015-01-08 7:39 ` Paul Walmsley
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=20150107142005.GA1621@ulmo \
--to=thierry.reding@gmail.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).