From: Sudeep Holla <sudeep.holla@arm.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Matt Mackall <mpm@selenic.com>, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Ron Rindjunsky <ronrindj@amazon.com>,
Ali Saidi <alisaidi@amazon.com>,
Catalin Marinas <catalin.marinas@arm.com>,
David Woodhouse <dwmw@amazon.co.uk>,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH 2/3] arm64: export acpi_psci_use_hvc
Date: Wed, 5 Jun 2019 12:02:32 +0100 [thread overview]
Message-ID: <20190605110232.GB20813@e107155-lin> (raw)
In-Reply-To: <20190605103840.GA30925@lakrids.cambridge.arm.com>
On Wed, Jun 05, 2019 at 11:38:40AM +0100, Mark Rutland wrote:
> On Wed, Jun 05, 2019 at 10:40:31AM +0100, Sudeep Holla wrote:
> > On Tue, Jun 04, 2019 at 08:30:59PM +0000, Ali Saidi wrote:
> > > Allow a module that wants to make SMC calls to detect if it should be
> > > using smc or hvc.
> > >
> > > Signed-off-by: Ali Saidi <alisaidi@amazon.com>
> > > ---
> > > arch/arm64/kernel/acpi.c | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c
> > > index 803f0494dd3e..ea41c6541d3c 100644
> > > --- a/arch/arm64/kernel/acpi.c
> > > +++ b/arch/arm64/kernel/acpi.c
> > > @@ -119,6 +119,7 @@ bool acpi_psci_use_hvc(void)
> > > {
> > > return acpi_gbl_FADT.arm_boot_flags & ACPI_FADT_PSCI_USE_HVC;
> > > }
> > > +EXPORT_SYMBOL_GPL(acpi_psci_use_hvc);
> > >
> >
> > I would rather have this in drivers/firmware/psci/psci.c checking the
> > value of psci_ops.conduit so that it's not just ACPI specific and can
> > be used on DT platforms too if required.
>
> I'd also like this to not hook into PSCI internals. This code cares
> about SMCCC, not PSCI. We also really shouldn't need to spread the
> conduit management everywhere, too.
I agree. I remember suggesting the same to Xilinx a while ago but I
didn't see your patches in the mainline.
--
Regards,
Sudeep
_______________________________________________
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-06-05 11:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 20:30 [PATCH 0/3] Add support for Graviton TRNG Ali Saidi
2019-06-04 20:30 ` [PATCH 1/3] arm/arm64: Add smccc hypervisor service identifiers Ali Saidi
2019-06-04 20:30 ` [PATCH 2/3] arm64: export acpi_psci_use_hvc Ali Saidi
2019-06-05 9:40 ` Sudeep Holla
2019-06-05 10:38 ` Mark Rutland
2019-06-05 11:02 ` Sudeep Holla [this message]
2019-06-05 16:07 ` Saidi, Ali
2019-06-04 20:31 ` [PATCH 3/3] hwrng: Add support for AWS Graviton TRNG Ali Saidi
2019-06-05 12:20 ` [PATCH 0/3] Add support for " Will Deacon
2019-06-07 12:58 ` Saidi, Ali
2019-06-28 18:05 ` Saidi, Ali
2019-07-01 8:28 ` Will Deacon
2019-07-01 17:02 ` Will Deacon
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=20190605110232.GB20813@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=alisaidi@amazon.com \
--cc=arnd@arndb.de \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mpm@selenic.com \
--cc=ronrindj@amazon.com \
--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