linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>,
	"Robert Yang" <decatf@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Russell King <linux@armlinux.org.uk>,
	Thierry Reding <thierry.reding@gmail.com>,
	linux-tegra@vger.kernel.org,
	Jonathan Hunter <jonathanh@nvidia.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/7] Support Trusted Foundations firmware on Tegra30
Date: Mon, 25 Feb 2019 08:21:55 +0300	[thread overview]
Message-ID: <20190225082155.1163ed85@dimatab> (raw)
In-Reply-To: <20190225040232.GA2242@qmqm.qmqm.pl>

В Mon, 25 Feb 2019 05:02:33 +0100
Michał Mirosław <mirq-linux@rere.qmqm.pl> пишет:

> On Fri, Feb 22, 2019 at 10:34:19PM +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.  
> 
> Hi Dmitry
> 
> I've applied and tested this patchset on my TF300T. Boots and
> suspends/wakes using 'rtcwake -m mem -s 1 -d /dev/rtc1' as the test.
> dmesg attached.
> 
> The exact tree used:
> 	git://rere.qmqm.pl/linux tf300t
> 
> Feel free to add my Tested-by and Signed-off-by on the patches where
> apropriate, and thanks for your work!

Awesome, thank you very much!

Robert, could you please confirm that v6 works for you too?

I'll probably make a v7 with an extra minor clean up and then will add
all the appropriate tags to the patches.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2019-02-25  5:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-22 19:34 [PATCH v6 0/7] Support Trusted Foundations firmware on Tegra30 Dmitry Osipenko
2019-02-22 19:34 ` [PATCH v6 1/7] ARM: trusted_foundations: Implement L2 cache initialization callback Dmitry Osipenko
2019-02-22 19:34 ` [PATCH v6 2/7] ARM: trusted_foundations: Make prepare_idle call to take mode argument Dmitry Osipenko
2019-02-22 19:34 ` [PATCH v6 3/7] ARM: trusted_foundations: Provide information about whether firmware is registered Dmitry Osipenko
2019-02-22 19:34 ` [PATCH v6 4/7] ARM: tegra: Set up L2 cache using Trusted Foundations firmware Dmitry Osipenko
2019-02-22 19:34 ` [PATCH v6 5/7] ARM: tegra: Don't apply CPU erratas in insecure mode Dmitry Osipenko
2019-02-22 19:34 ` [PATCH v6 6/7] ARM: tegra: Always boot CPU in ARM-mode Dmitry Osipenko
2019-02-22 19:34 ` [PATCH v6 7/7] ARM: tegra: Add firmware calls required for suspend-resume on Tegra30 Dmitry Osipenko
     [not found] ` <20190225040232.GA2242@qmqm.qmqm.pl>
2019-02-25  5:21   ` Dmitry Osipenko [this message]
2019-02-25 16:58     ` [PATCH v6 0/7] Support Trusted Foundations firmware " Robert Yang
2019-02-25 17:55       ` 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=20190225082155.1163ed85@dimatab \
    --to=digetx@gmail.com \
    --cc=decatf@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 \
    --cc=thierry.reding@gmail.com \
    /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).