All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
	Russell King <rmk+kernel@armlinux.org.uk>,
	Will Deacon <will@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Sumit Garg <sumit.garg@linaro.org>, Arnd Bergmann <arnd@arndb.de>,
	Volodymyr Babchuk <vlad.babchuk@gmail.com>,
	Marc Zyngier <maz@kernel.org>, "Andrew F. Davis" <afd@ti.com>,
	Olof Johansson <olof@lixom.net>,
	Andy Gross <andy.gross@linaro.org>,
	Colin Ian King <colin.king@canonical.com>,
	Jens Wiklander <jens.wiklander@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: arm_smccc_smc as generic smc interface?
Date: Mon, 9 Dec 2019 10:07:52 -0800	[thread overview]
Message-ID: <20191209180752.GJ35479@atomide.com> (raw)

Hi all,

So it seems that we could make arm_smccc_smc() into a generic kernel
smc interface instead of being limited to optee usage. That is
assuming optee and legacy calls are never be enabled the same time
on a booted system :)

I know arm_smccc_smc() currently assumes a specific register usage
for the optee case, but AFAIK those limitations do not exist for
non-optee cases.

Does anybody see some other issues with making arm_smccc_smc() into
a generic smc call interface?

If there are some more optee specific considerations with making
arm_smccc_smc() into a generic interface, we could just set up
something generic that also arm_smccc_smc() can then call.

The use case I'm familiar with are the old TI smc calls that need
register specific quirks enabled only for the non-optee case,
while with optee enabled, quirks are not needed. There are
probably similar issues with other SoCs too.

Regards,

Tony

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

             reply	other threads:[~2019-12-09 18:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 18:07 Tony Lindgren [this message]
2019-12-10  8:09 ` arm_smccc_smc as generic smc interface? Jens Wiklander
2019-12-10 15:38   ` Tony Lindgren
2019-12-12 14:23     ` Mark Rutland
2019-12-12 15:23       ` Andrew F. Davis
2019-12-12 15:58         ` Mark Rutland
2019-12-12 17:12           ` Will Deacon
2019-12-12 17:47             ` Andrew F. Davis
2019-12-12 18:56               ` Mark Rutland

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=20191209180752.GJ35479@atomide.com \
    --to=tony@atomide.com \
    --cc=afd@ti.com \
    --cc=andy.gross@linaro.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=colin.king@canonical.com \
    --cc=jens.wiklander@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=olof@lixom.net \
    --cc=rmk+kernel@armlinux.org.uk \
    --cc=sumit.garg@linaro.org \
    --cc=vlad.babchuk@gmail.com \
    --cc=will@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.