From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Tony Lindgren <tony@atomide.com>
Subject: [GIT PULL 2/4] soc changes for omap smc for v5.6
Date: Thu, 16 Jan 2020 10:48:11 -0800 [thread overview]
Message-ID: <pull-1579200367-372444@atomide.com-2> (raw)
In-Reply-To: <pull-1579200367-372444@atomide.com>
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 4601832f40501efc3c2fd264a5a69bd1ac17d520:
ARM: OMAP2+: use separate IOMMU pdata to fix DRA7 IPU1 boot (2019-12-17 09:57:09 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.6/soc-smc-signed
for you to fetch changes up to 8ab871f8bdfcca627802b6992e556fba5722a268:
ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers (2020-01-13 10:06:46 -0800)
----------------------------------------------------------------
SMC related changes for omaps for v5.6 merge window
A series of changes to use optee SMC calls if optee is initialized by
the bootloader. Based on the discussions on LAKML in mailing list thread
"arm_smccc_smc as generic smc interface?" we don't want to add more quirk
handling to arm_smccc_smc() and want to handle it locally instead.
----------------------------------------------------------------
Andrew F. Davis (4):
ARM: OMAP2+: Add omap_secure_init callback hook for secure initialization
ARM: OMAP2+: Introduce check for OP-TEE in omap_secure_init()
ARM: OMAP2+: Use ARM SMC Calling Convention when OP-TEE is available
ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers
arch/arm/mach-omap2/common.h | 2 +-
arch/arm/mach-omap2/io.c | 11 +++++++++
arch/arm/mach-omap2/omap-secure.c | 50 +++++++++++++++++++++++++++++++++++++++
arch/arm/mach-omap2/omap-secure.h | 10 ++++++++
arch/arm/mach-omap2/omap-smc.S | 6 ++---
arch/arm/mach-omap2/pm33xx-core.c | 24 +++++++++++++++++++
6 files changed, 99 insertions(+), 4 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: soc@kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org, arm@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] soc changes for omap smc for v5.6
Date: Thu, 16 Jan 2020 10:48:11 -0800 [thread overview]
Message-ID: <pull-1579200367-372444@atomide.com-2> (raw)
In-Reply-To: <pull-1579200367-372444@atomide.com>
From: "Tony Lindgren" <tony@atomide.com>
The following changes since commit 4601832f40501efc3c2fd264a5a69bd1ac17d520:
ARM: OMAP2+: use separate IOMMU pdata to fix DRA7 IPU1 boot (2019-12-17 09:57:09 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap tags/omap-for-v5.6/soc-smc-signed
for you to fetch changes up to 8ab871f8bdfcca627802b6992e556fba5722a268:
ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers (2020-01-13 10:06:46 -0800)
----------------------------------------------------------------
SMC related changes for omaps for v5.6 merge window
A series of changes to use optee SMC calls if optee is initialized by
the bootloader. Based on the discussions on LAKML in mailing list thread
"arm_smccc_smc as generic smc interface?" we don't want to add more quirk
handling to arm_smccc_smc() and want to handle it locally instead.
----------------------------------------------------------------
Andrew F. Davis (4):
ARM: OMAP2+: Add omap_secure_init callback hook for secure initialization
ARM: OMAP2+: Introduce check for OP-TEE in omap_secure_init()
ARM: OMAP2+: Use ARM SMC Calling Convention when OP-TEE is available
ARM: OMAP2+: sleep43xx: Call secure suspend/resume handlers
arch/arm/mach-omap2/common.h | 2 +-
arch/arm/mach-omap2/io.c | 11 +++++++++
arch/arm/mach-omap2/omap-secure.c | 50 +++++++++++++++++++++++++++++++++++++++
arch/arm/mach-omap2/omap-secure.h | 10 ++++++++
arch/arm/mach-omap2/omap-smc.S | 6 ++---
arch/arm/mach-omap2/pm33xx-core.c | 24 +++++++++++++++++++
6 files changed, 99 insertions(+), 4 deletions(-)
_______________________________________________
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:[~2020-01-16 18:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 18:48 [GIT PULL 1/4] fix for omap sdma changes for v5.6 Tony Lindgren
2020-01-16 18:48 ` Tony Lindgren
2020-01-16 18:48 ` Tony Lindgren [this message]
2020-01-16 18:48 ` [GIT PULL 2/4] soc changes for omap smc " Tony Lindgren
2020-01-16 18:48 ` [GIT PULL 3/4] ti-sysc driver changes for omaps " Tony Lindgren
2020-01-16 18:48 ` Tony Lindgren
2020-01-16 18:48 ` [GIT PULL 4/4] Tony Lindgren
2020-01-16 18:48 ` Tony Lindgren
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=pull-1579200367-372444@atomide.com-2 \
--to=tony@atomide.com \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=soc@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.