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 6/7] firmware: arm_ffa: Setup in-kernel users of FFA partitions
Date: Thu, 18 Mar 2021 14:08:37 +0100 [thread overview]
Message-ID: <CAHUa44Fuq3MoS+r60rfG4Fgh_gQ-_8R6qfTx0TUmUvVQYpXOMQ@mail.gmail.com> (raw)
In-Reply-To: <20210212154614.38604-7-sudeep.holla@arm.com>
On Fri, Feb 12, 2021 at 4:46 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
>
> Parse the FFA nodes from the device-tree and register all the partitions
> whose services will be used in the kernel.
>
> In order to also enable in-kernel users of FFA interface, let us add
> simple set of operations for such devices.
>
> The in-kernel users are registered without the character device interface.
>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> drivers/firmware/arm_ffa/common.h | 2 +
> drivers/firmware/arm_ffa/driver.c | 188 ++++++++++++++++++++++++++++++
> include/linux/arm_ffa.h | 38 +++++-
> 3 files changed, 227 insertions(+), 1 deletion(-)
>
Reviewed-by: Jens Wiklander <jens.wiklander@linaro.org>
Thanks,
Jens
_______________________________________________
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:[~2021-03-18 13:12 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 [this message]
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
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=CAHUa44Fuq3MoS+r60rfG4Fgh_gQ-_8R6qfTx0TUmUvVQYpXOMQ@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).