From: Thierry Reding <thierry.reding@gmail.com>
To: Russell King <linux@armlinux.org.uk>
Cc: linux-kernel@vger.kernel.org,
"Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
"Robert Yang" <decatf@gmail.com>,
linux-tegra@vger.kernel.org, "Dmitry Osipenko" <digetx@gmail.com>,
"Jonathan Hunter" <jonathanh@nvidia.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/8] Support Trusted Foundations firmware on Tegra30
Date: Mon, 18 Feb 2019 09:51:14 +0100 [thread overview]
Message-ID: <20190218085114.GC19363@ulmo> (raw)
In-Reply-To: <20190218001726.16785-1-digetx@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 3447 bytes --]
On Mon, Feb 18, 2019 at 03:17:18AM +0300, Dmitry Osipenko wrote:
> Hello,
>
> This patchset adds support for the Trusted Foundations firmware on
> NVIDIA Tegra30. Pretty much all of Tegra30 consumer devices have that
> firmware and upstream kernel can't boot on those devices without the
> firmware support.
>
> Changelog:
>
> v4: - Fixed Thumb2-kernel hanging on Tegra20, turned out it was not a
> good idea to switch CPU into Thumb2 mode right after jumping into
> the reset handler.
>
> - Moved LP2-mode-set firmware call invocation to a later stage to
> better replicate what downstream kernel does. This change was
> suggested by Robert Yang and fixes system hang on Ouya game
> console.
>
> - Added references to the original work made by Michał Mirosław
> into commit messages of the relevant patches.
>
> v3: - Implemented suspend-resume support.
>
> - Reworked arm/firmware/trusted_foundations.c a tad. Now cache
> is getting properly initialized, cache enabling / disabling is
> supported.
>
> v2:
> - The "Don't apply CPU erratas in insecure mode" patch got some
> cleanup, in particular resolved the messiness in
> __tegra_cpu_reset_handler_data.
>
> - Added a comment to tf_cache_write_sec(), justifying the warning
> message.
>
> Dmitry Osipenko (8):
> ARM: trusted_foundations: Implement L2 cache initialization callback
> ARM: trusted_foundations: Make prepare_idle call to take mode argument
> ARM: trusted_foundations: Provide information about whether firmware
> is registered
> ARM: tegra: Set up L2 cache using Trusted Foundations firmware
> ARM: tegra: Don't apply CPU erratas in insecure mode
> ARM: tegra: Always boot CPU in ARM-mode
> ARM: tegra: Support L2 cache maintenance done via firmware
> ARM: tegra: Add firmware calls required for suspend-resume
>
> arch/arm/firmware/trusted_foundations.c | 80 +++++++++++++++++++++-
> arch/arm/include/asm/firmware.h | 2 +-
> arch/arm/include/asm/trusted_foundations.h | 13 ++++
> arch/arm/mach-tegra/cpuidle-tegra114.c | 3 +-
> arch/arm/mach-tegra/pm.c | 50 ++++++++++++++
> arch/arm/mach-tegra/reset-handler.S | 52 ++++++++++----
> arch/arm/mach-tegra/reset.c | 3 +
> arch/arm/mach-tegra/reset.h | 9 ++-
> arch/arm/mach-tegra/sleep-tegra20.S | 4 ++
> arch/arm/mach-tegra/sleep.S | 11 +--
> arch/arm/mach-tegra/tegra.c | 10 +++
> 11 files changed, 214 insertions(+), 23 deletions(-)
Hi Russell,
I'm not sure if this is something that you have a vested interest in. It
looks like Tegra is the only platform that uses this, and usage is
limited to two generations (Tegra30 and Tegra114). Do you mind if I pick
this up into the Tegra tree and send this as part of the pull requests
for v5.2?
Actually, Trusted Foundations is the only firmware implementation left
in arch/arm/firmware, so how about we move this file over to
drivers/firmware (perhaps even the tegra subdirectory given that nobody
else seems to be using it) and get rid of arch/arm/firmware?
I can prepare a patch that does that on top of this series, just let me
know how you want to handle this.
Thanks,
Thierry
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-02-18 8:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-18 0:17 [PATCH v4 0/8] Support Trusted Foundations firmware on Tegra30 Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 1/8] ARM: trusted_foundations: Implement L2 cache initialization callback Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 2/8] ARM: trusted_foundations: Make prepare_idle call to take mode argument Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 3/8] ARM: trusted_foundations: Provide information about whether firmware is registered Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 4/8] ARM: tegra: Set up L2 cache using Trusted Foundations firmware Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 5/8] ARM: tegra: Don't apply CPU erratas in insecure mode Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 6/8] ARM: tegra: Always boot CPU in ARM-mode Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 7/8] ARM: tegra: Support L2 cache maintenance done via firmware Dmitry Osipenko
2019-02-18 0:17 ` [PATCH v4 8/8] ARM: tegra: Add firmware calls required for suspend-resume Dmitry Osipenko
2019-02-18 8:51 ` Thierry Reding [this message]
2019-02-20 13:30 ` [PATCH v4 0/8] Support Trusted Foundations firmware on Tegra30 Dmitry Osipenko
2019-02-20 16:36 ` Michał Mirosław
2019-02-20 17:01 ` Dmitry Osipenko
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=20190218085114.GC19363@ulmo \
--to=thierry.reding@gmail.com \
--cc=decatf@gmail.com \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mirq-linux@rere.qmqm.pl \
/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).