soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: arm@kernel.org, soc@kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	op-tee@lists.trustedfirmware.org,
	Rui Miguel Silva <rui.silva@linaro.org>
Subject: [GIT PULL] OP-TEE driver for v5.11
Date: Wed, 25 Nov 2020 13:01:34 +0100	[thread overview]
Message-ID: <20201125120134.GA1642471@jade> (raw)

Hello arm-soc maintainers,

Please pull this small patch which allows the OP-TEE driver to work with
ARMv7 based single CPU systems.

Thanks,
Jens

The following changes since commit 3cea11cd5e3b00d91caf0b4730194039b45c5891:

  Linux 5.10-rc2 (2020-11-01 14:43:51 -0800)

are available in the Git repository at:

  git://git.linaro.org/people/jens.wiklander/linux-tee.git tags/optee-valid-memory-type-for-v5.11

for you to fetch changes up to 853735e404244f5496cdb6188c5ed9a0f9627ee6:

  optee: add writeback to valid memory type (2020-11-25 12:51:52 +0100)

----------------------------------------------------------------
Add writeback to valid OP-TEE shared memory types

Allows OP-TEE to work with ARMv7 based single CPU systems by allowing
writeback cache policy for shared memory.

----------------------------------------------------------------
Rui Miguel Silva (1):
      optee: add writeback to valid memory type

 drivers/tee/optee/call.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

             reply	other threads:[~2020-11-25 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 12:01 Jens Wiklander [this message]
2020-11-26 21:00 ` [GIT PULL] OP-TEE driver for v5.11 Arnd Bergmann
2020-11-27  7:14   ` Jens Wiklander
2020-11-27  7:14     ` Jens Wiklander
2020-11-27 17:10 ` patchwork-bot+linux-soc
2020-11-27 17:10 ` patchwork-bot+linux-soc

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=20201125120134.GA1642471@jade \
    --to=jens.wiklander@linaro.org \
    --cc=arm@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=rui.silva@linaro.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 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).