From: Stuart Menefy <stuart.menefy@mathembedded.com>
To: Russell King <linux@armlinux.org.uk>,
Arnd Bergmann <arnd@arndb.de>, Will Deacon <will.deacon@arm.com>,
Nicolas Pitre <nico@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH] ARM: MCPM: Add provision for platform specific wfi alternative
Date: Mon, 11 Feb 2019 13:53:14 +0000 [thread overview]
Message-ID: <CAPoDyq6vzXuR+Z=t9eyJytuOGZknyY1nOY7v_ir86VTZM3DH5g@mail.gmail.com> (raw)
In-Reply-To: <20190210231212.20470-1-stuart.menefy@mathembedded.com>
Folks
On Sun, 10 Feb 2019 at 23:12, Stuart Menefy
<stuart.menefy@mathembedded.com> wrote:
>
> On some platforms (in particular the Exynos5260) the wfi is not
> executed directly by the operating system but by trapping into the
> secure monitor. This allows us to replicate the behaviour of the
> vendor supplied kernel using the MCPM framework.
>
> Signed-off-by: Stuart Menefy <stuart.menefy@mathembedded.com>
I forgot to add, this is a part of a series of patches which updates
the Exynos 5260
support, allowing use of the kernel on secure parts and adding suspend
functionality,
Version 1 of the patches has been posted to the samsung-soc mailing list:
https://www.spinics.net/lists/linux-samsung-soc/#65035
and I'm just about to post version 2. However as this is the only patch which
touches generic ARM files I though I'd better check the approach is acceptable
to a wider audience.
Stuart
_______________________________________________
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-11 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-10 23:12 [PATCH] ARM: MCPM: Add provision for platform specific wfi alternative Stuart Menefy
2019-02-11 13:53 ` Stuart Menefy [this message]
2019-02-11 14:12 ` Russell King - ARM Linux admin
2019-02-11 15:57 ` Nicolas Pitre
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='CAPoDyq6vzXuR+Z=t9eyJytuOGZknyY1nOY7v_ir86VTZM3DH5g@mail.gmail.com' \
--to=stuart.menefy@mathembedded.com \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nico@linaro.org \
--cc=will.deacon@arm.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).