linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	 Devicetree List <devicetree@vger.kernel.org>,
	Trilok Soni <tsoni@codeaurora.org>,
	arve@android.com,  Andrew Walbran <qwandor@google.com>,
	David Hartley <dhh@qti.qualcomm.com>,
	 Achin Gupta <Achin.Gupta@arm.com>,
	Arunachalam Ganapathy <arunachalam.ganapathy@arm.com>,
	 Marc Bonnici <marc.bonnici@arm.com>
Subject: Re: [PATCH v4 0/7] firmware: Add initial support for Arm FF-A
Date: Thu, 18 Mar 2021 15:09:46 +0100	[thread overview]
Message-ID: <CAHUa44HdHdN7tES60vcBqRo=afUtxNHx1vnYx5JmX-UocV5PRA@mail.gmail.com> (raw)
In-Reply-To: <20210316143429.tdyyulkml4ypdixy@bogus>

Hi Sudeep,

On Tue, Mar 16, 2021 at 3:34 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> Hi Jens,
>
> On Fri, Feb 12, 2021 at 03:46:07PM +0000, Sudeep Holla wrote:
> > Hi all,
> >
> > This is very basic implementation for in-kernel support for Arm FF-A
> > specification.
> >
> > Arm Firmware Framework for Armv8-A specification[1] describes a software
> > architecture that provides mechanism to utilise the virtualization
> > extension to isolate software images and describes interfaces that
> > standardize communication between the various software images. This
> > includes communication between images in the Secure and Normal world.
> >
> > The main idea here is to create FFA device to establish any communication
> > with a secure partition. This is currently tested with OPTEE(with changes
> > to OPTEE driver adding FFA as transport)
> >
>
> Since you reviewed the last version, it would be helpful if you provide
> Reviewed-by or Tested-by if you happy with this version. I would like to
> get this initial version merged for v5.13

I've tested this in a few of my setups and everything looks over all
fine, so please apply:
Tested-by: Jens Wiklander <jens.wiklander@linaro.org>

I'm also double checking the details of the patches for some further
feedback. Stay tuned.

Thanks,
Jens

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

  reply	other threads:[~2021-03-18 14:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-12 15:46 [PATCH v4 0/7] firmware: Add initial support for Arm FF-A Sudeep Holla
2021-02-12 15:46 ` [PATCH v4 1/7] dt-bindings: Arm: Add Firmware Framework for Armv8-A (FF-A) binding Sudeep Holla
2021-03-05 20:38   ` Rob Herring
2021-02-12 15:46 ` [PATCH v4 2/7] arm64: smccc: Add support for SMCCCv1.2 input/output registers Sudeep Holla
2021-03-17  7:17   ` Jens Wiklander
2021-03-23  9:56     ` Sudeep Holla
2021-02-12 15:46 ` [PATCH v4 3/7] firmware: arm_ffa: Add initial FFA bus support for device enumeration Sudeep Holla
2021-02-12 15:46 ` [PATCH v4 4/7] firmware: arm_ffa: Add initial Arm FFA driver support Sudeep Holla
2021-03-19  7:25   ` Jens Wiklander
2021-03-23  9:53     ` Sudeep Holla
2021-02-12 15:46 ` [PATCH v4 5/7] firmware: arm_ffa: Add support for SMCCC as transport to FFA driver Sudeep Holla
2021-03-19  7:02   ` Jens Wiklander
2021-02-12 15:46 ` [PATCH v4 6/7] firmware: arm_ffa: Setup in-kernel users of FFA partitions Sudeep Holla
2021-03-18 13:08   ` Jens Wiklander
2021-02-12 15:46 ` [PATCH v4 7/7] firmware: arm_ffa: Add support for MEM_* interfaces Sudeep Holla
2021-03-18 14:02   ` Jens Wiklander
2021-03-16 14:34 ` [PATCH v4 0/7] firmware: Add initial support for Arm FF-A Sudeep Holla
2021-03-18 14:09   ` Jens Wiklander [this message]
2021-03-19  7:56     ` Jens Wiklander
2021-03-23  9:50       ` Sudeep Holla
2021-03-23  9:49     ` Sudeep Holla

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='CAHUa44HdHdN7tES60vcBqRo=afUtxNHx1vnYx5JmX-UocV5PRA@mail.gmail.com' \
    --to=jens.wiklander@linaro.org \
    --cc=Achin.Gupta@arm.com \
    --cc=arunachalam.ganapathy@arm.com \
    --cc=arve@android.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dhh@qti.qualcomm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.bonnici@arm.com \
    --cc=qwandor@google.com \
    --cc=sudeep.holla@arm.com \
    --cc=tsoni@codeaurora.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).