From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8B61FC433F5 for ; Wed, 18 May 2022 10:11:30 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234984AbiERKL3 (ORCPT ); Wed, 18 May 2022 06:11:29 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60728 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235110AbiERKLQ (ORCPT ); Wed, 18 May 2022 06:11:16 -0400 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 2C0EA258 for ; Wed, 18 May 2022 03:11:13 -0700 (PDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 26AB523A; Wed, 18 May 2022 03:11:13 -0700 (PDT) Received: from bogus (e103737-lin.cambridge.arm.com [10.1.197.49]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 58E493F718; Wed, 18 May 2022 03:11:12 -0700 (PDT) Date: Wed, 18 May 2022 11:11:09 +0100 From: Sudeep Holla To: Gyorgy Szing Cc: Sumit Garg , "linux-kernel@vger.kernel.org" , "op-tee@lists.trustedfirmware.org" , Sudeep Holla Subject: Re: [PATCH] tee: Add Arm FF-A TEE driver Message-ID: <20220518101109.xdmiuj5gjqg3drhm@bogus> References: <20220408134144.1532704-1-sudeep.holla@arm.com> <20220426144545.6qkn6iwayuwpvi7g@bogus> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, May 17, 2022 at 06:55:47PM +0100, Gyorgy Szing wrote: > Hi Sumit, > > The best way to test the driver is to use the PSA SPs from Trusted Services > similarly as described on the wiki page above. We have merged the TEE driver > enablement patches to integration branch of TS recently, and as a result the > set-up and build instructions above will build an end-to-end config using > the TEE driver. > The TEE driver integration needs to be changed though. Instead of building > the TEE driver as an out of tree module from our fork [2], you might want to > change the config to use the driver posted by Sudeep. If you wish to use the > op-tee build flow, the makefiles in OP-TEE/build repo part of the above > set-up need modification too. Correct I have done something similar when testing as a module. > TS will build multiple test executables targeting the Linux user-space. For > TEE driver testing any of these targeting the "arm-linux" environment will > do, but I suggest using the "ts-service-test". > > AFAIK Sudeep is testing with TS too using a similar set-up. > Indeed. I just made couple of minor changes to the way app checks the presence of the driver and dropped the version check. Ref: ffarpc_caller_check_version in components/rpc/ffarpc/caller/linux/ffarpc_caller.c to make progress. > [2] https://gitlab.arm.com/linux-arm/linux-trusted-services > -- Regards, Sudeep