All of lore.kernel.org
 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>
Subject: Re: [PATCH v3 6/7] firmware: arm_ffa: Setup in-kernel users of FFA partitions
Date: Wed, 13 Jan 2021 08:10:08 +0100	[thread overview]
Message-ID: <20210113071008.GA3643006@jade> (raw)
In-Reply-To: <20210112180414.ejcuhdf563hraqzx@bogus>

On Tue, Jan 12, 2021 at 06:04:14PM +0000, Sudeep Holla wrote:
> (sorry for late reply)
> 
> On Fri, Dec 11, 2020 at 11:45:08AM +0100, Jens Wiklander wrote:
> > On Fri, Dec 4, 2020 at 1:11 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
> 
> [...]
> 
> Agreed on all the comments, so have just removed those context.
> 
> > We may need a way to indicate if we're to use the 32bit or 64bit
> > calling convention. OP-TEE depends on being able to use 32bit calls
> > here.
> 
> I assume it would be OP-TEE indicating it would like to use 32-bit.
> I am thinking of API from the driver would be like:
> 
> int (*32bit_mode_only_set)(struct ffa_device *dev);
> 
> Let me know if that works for you. FF-A driver has no other way to evaluate
> that and I really don't like that in DT 😉 

That should work for OP-TEE.

Thanks,
Jens

WARNING: multiple messages have this Message-ID (diff)
From: Jens Wiklander <jens.wiklander@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Trilok Soni <tsoni@codeaurora.org>,
	Devicetree List <devicetree@vger.kernel.org>,
	David Hartley <dhh@qti.qualcomm.com>,
	Andrew Walbran <qwandor@google.com>,
	Achin Gupta <Achin.Gupta@arm.com>,
	arve@android.com,
	Arunachalam Ganapathy <arunachalam.ganapathy@arm.com>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 6/7] firmware: arm_ffa: Setup in-kernel users of FFA partitions
Date: Wed, 13 Jan 2021 08:10:08 +0100	[thread overview]
Message-ID: <20210113071008.GA3643006@jade> (raw)
In-Reply-To: <20210112180414.ejcuhdf563hraqzx@bogus>

On Tue, Jan 12, 2021 at 06:04:14PM +0000, Sudeep Holla wrote:
> (sorry for late reply)
> 
> On Fri, Dec 11, 2020 at 11:45:08AM +0100, Jens Wiklander wrote:
> > On Fri, Dec 4, 2020 at 1:11 PM Sudeep Holla <sudeep.holla@arm.com> wrote:
> 
> [...]
> 
> Agreed on all the comments, so have just removed those context.
> 
> > We may need a way to indicate if we're to use the 32bit or 64bit
> > calling convention. OP-TEE depends on being able to use 32bit calls
> > here.
> 
> I assume it would be OP-TEE indicating it would like to use 32-bit.
> I am thinking of API from the driver would be like:
> 
> int (*32bit_mode_only_set)(struct ffa_device *dev);
> 
> Let me know if that works for you. FF-A driver has no other way to evaluate
> that and I really don't like that in DT 😉 

That should work for OP-TEE.

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-01-13  7:10 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 12:11 [PATCH v3 0/7] firmware: Add initial support for Arm FF-A Sudeep Holla
2020-12-04 12:11 ` Sudeep Holla
2020-12-04 12:11 ` [PATCH v3 1/7] dt-bindings: Arm: Add Firmware Framework for Armv8-A (FF-A) binding Sudeep Holla
2020-12-04 12:11   ` Sudeep Holla
2020-12-14 22:01   ` Rob Herring
2020-12-14 22:01     ` Rob Herring
2020-12-16 12:24     ` Sudeep Holla
2020-12-16 12:24       ` Sudeep Holla
2020-12-16 13:46       ` Jens Wiklander
2020-12-16 13:46         ` Jens Wiklander
2021-01-13 10:00       ` Sudeep Holla
2021-01-13 10:00         ` Sudeep Holla
2020-12-04 12:11 ` [PATCH v3 2/7] arm64: smccc: Add support for SMCCCv1.2 input/output registers Sudeep Holla
2020-12-04 12:11   ` Sudeep Holla
2020-12-04 12:11 ` [PATCH v3 3/7] firmware: arm_ffa: Add initial FFA bus support for device enumeration Sudeep Holla
2020-12-04 12:11   ` Sudeep Holla
2020-12-04 12:11 ` [PATCH v3 4/7] firmware: arm_ffa: Add initial Arm FFA driver support Sudeep Holla
2020-12-04 12:11   ` Sudeep Holla
2020-12-04 12:11 ` [PATCH v3 5/7] firmware: arm_ffa: Add support for SMCCC as transport to FFA driver Sudeep Holla
2020-12-04 12:11   ` Sudeep Holla
2020-12-04 12:11 ` [PATCH v3 6/7] firmware: arm_ffa: Setup in-kernel users of FFA partitions Sudeep Holla
2020-12-04 12:11   ` Sudeep Holla
2020-12-07 12:30   ` Jens Wiklander
2020-12-07 12:30     ` Jens Wiklander
2021-01-13  9:22     ` Sudeep Holla
2021-01-13  9:22       ` Sudeep Holla
2020-12-11 10:45   ` Jens Wiklander
2020-12-11 10:45     ` Jens Wiklander
2020-12-11 10:59     ` Jens Wiklander
2020-12-11 10:59       ` Jens Wiklander
2021-01-13  9:44       ` Sudeep Holla
2021-01-13  9:44         ` Sudeep Holla
2021-01-13 12:30         ` Jens Wiklander
2021-01-13 12:30           ` Jens Wiklander
2021-01-13 13:58           ` Achin Gupta
2021-01-13 13:58             ` Achin Gupta
2021-01-13 17:20             ` Sudeep Holla
2021-01-13 17:20               ` Sudeep Holla
2021-01-14  6:48               ` Jens Wiklander
2021-01-14  6:48                 ` Jens Wiklander
2021-01-12 18:04     ` Sudeep Holla
2021-01-12 18:04       ` Sudeep Holla
2021-01-13  7:10       ` Jens Wiklander [this message]
2021-01-13  7:10         ` Jens Wiklander
2020-12-04 12:11 ` [PATCH v3 7/7] firmware: arm_ffa: Add support for MEM_* interfaces Sudeep Holla
2020-12-04 12:11   ` Sudeep Holla
2020-12-11 10:54   ` Jens Wiklander
2020-12-11 10:54     ` Jens Wiklander

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=20210113071008.GA3643006@jade \
    --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=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 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.