From: Sudeep Holla <sudeep.holla@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com,
kernel-team@android.com, Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <maz@kernel.org>, Mark Brown <broonie@kernel.org>,
Sudeep Holla <sudeep.holla@arm.com>,
Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH v2] arm64: smccc: Add support for SMCCCv1.2 extended input/output registers
Date: Wed, 26 May 2021 18:15:44 +0100 [thread overview]
Message-ID: <20210526171544.5lb5jj25zmo6pl26@bogus> (raw)
In-Reply-To: <20210526170556.GA19831@willie-the-truck>
On Wed, May 26, 2021 at 06:05:56PM +0100, Will Deacon wrote:
> On Wed, May 26, 2021 at 11:34:36AM +0100, Sudeep Holla wrote:
> > On Tue, May 25, 2021 at 07:58:50PM +0100, Will Deacon wrote:
> > > On Tue, 18 May 2021 17:36:18 +0100, Sudeep Holla wrote:
> > > > SMCCC v1.2 allows x8-x17 to be used as parameter registers and x4—x17
> > > > to be used as result registers in SMC64/HVC64. Arm Firmware Framework
> > > > for Armv8-A specification makes use of x0-x7 as parameter and result
> > > > registers. There are other users like Hyper-V who intend to use beyond
> > > > x0-x7 as well.
> > > >
> > > > Current SMCCC interface in the kernel just use x0-x7 as parameter and
> > > > x0-x3 as result registers as required by SMCCCv1.0. Let us add new
> > > > interface to support this extended set of input/output registers namely
> > > > x0-x17 as both parameter and result registers.
> > >
> > > Applied to arm64 (for-next/smccc), thanks!
> > >
> > > [1/1] arm64: smccc: Add support for SMCCCv1.2 extended input/output registers
> > > https://git.kernel.org/arm64/c/8ebe486de71a
> > >
> >
> > I see this is based on v5.13-rc3. As I mentioned earlier, I need to base
> > FF-A driver on this and arm-soc team always expects to send pull request
> > based on -rc1. Is it possible to have this based on -rc1 instead so that
> > I can base FF-A driver based on that ?
>
> Sorry, I forgot about that requirement. I've pushed a new branch
> (for-next/ffa) for you to use instead.
>
No worries, thanks for the branch.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-05-26 18:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 16:36 [PATCH v2] arm64: smccc: Add support for SMCCCv1.2 extended input/output registers Sudeep Holla
2021-05-18 18:58 ` Mark Brown
2021-05-25 18:58 ` Will Deacon
2021-05-26 10:34 ` Sudeep Holla
2021-05-26 17:05 ` Will Deacon
2021-05-26 17:15 ` Sudeep Holla [this message]
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=20210526171544.5lb5jj25zmo6pl26@bogus \
--to=sudeep.holla@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mikelley@microsoft.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 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).