Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3637908pxv; Mon, 26 Jul 2021 08:29:35 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxHhgHtKMM/T3UdMa7mmCcvCD8pmUV8mH+MnNbXcCzvVXpxkdwJKChOa9U+3F9sxHs8g0hN X-Received: by 2002:a05:6402:289b:: with SMTP id eg27mr416719edb.90.1627313375187; Mon, 26 Jul 2021 08:29:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627313375; cv=none; d=google.com; s=arc-20160816; b=TOi9XwGn9F3P0VnH2pAMYQj4Q+dmtY+ssk8eT2MLJUbGRRme/VjbfsqX1RdbPPvNAj 0Vy+8KZ2OlqJlaic6Q2JD/UMDEhvEY4oxa60fM0WsgjmxuLyxHBlN/YV1GTBlBtmdf4K Z4L1fzE0MUQ3RRve4S44GqfH54Wuo7MNJnsl3ehXK1SanOLX3IqQrhKmSuzqb0FuDPR7 Jc9I7HegFANT9/tYz6PB3Em6TMyQ06ZHUXDG/YNa+bnZN3ATRJ7DkUipG5hHcZRV0w3/ Eg2qy1wgUppeB2A7zQjF2qRtCMhVJjuad0oC7iV84LacDaSQZADdSKR4fL++IuXJK01U mX+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=pBVJyA4T0zI+iv2Wp5+oDPu2YIC5yps0Y/fvVSXYEQs=; b=qno0OjsostrUN20ieXF3xuyPpB3Ln8RLBpmYqePMTqHq2+ePv3g/Oth7E+krn8z/fI UwtFWSQ3qk/L3RzkEIPvI9f4hX7+nZkTILv4nJ8x79TDmlKxrK0meLGg35IfEY9nqm5/ 2+23/QVfR+jreYNKZEquexkIGTO8D883Ft4vzActCF8dVqbx6X8hyAQpt5STrHvAuonD Q5BKl+Q1D3mCPzi3+D9URgoDqO9jBccXD8A54dOWOM9574E4txAUKgUTGFrIaJ6coJFG gkzxK23LNYQzDsPA5/BpeKKeFh4PrXFsq1lvkdIqG9MQAxzvCfQlpV3KSfYia+LoOrnH HEOA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=RnK4xS2x; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e8si174506eja.349.2021.07.26.08.29.09; Mon, 26 Jul 2021 08:29:35 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=RnK4xS2x; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235103AbhGZOpO (ORCPT + 99 others); Mon, 26 Jul 2021 10:45:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42296 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234823AbhGZOpM (ORCPT ); Mon, 26 Jul 2021 10:45:12 -0400 Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8D957C061757 for ; Mon, 26 Jul 2021 08:25:35 -0700 (PDT) Received: by mail-wm1-x329.google.com with SMTP id l4-20020a05600c1d04b02902506f89ad2dso182316wms.1 for ; Mon, 26 Jul 2021 08:25:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pBVJyA4T0zI+iv2Wp5+oDPu2YIC5yps0Y/fvVSXYEQs=; b=RnK4xS2xaNXBC1CBiO/oGd1xKxTL0S6WNRwcmow7eXMFeFmdNu33WXk/v6Xep9s9nZ 64v9Ia2csL2/A8FBTKvPZK0DhAK/ThX51MTa7yVO8QS4YA/rXZnQhyY3Zke2jR0X4zAY YLdVxuhgOIubIxCv+mT+bIy6J/CRB7TccUyv5MmdxV2UcmJbCN/7ZB9N7i3Ipn47GvfA C6dt7ZaGJmQRJMdYewc26pR9nPPQfq/RZaZfSKY1A3c7FM36HzFxI28UD289MfQmoWg1 bJ6UzKgKfUlNvYknLeFfgTz1SYuo6t9oocOGm03DbhqxhQowxROkeG9Zv4e4i1xWElgw dTog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pBVJyA4T0zI+iv2Wp5+oDPu2YIC5yps0Y/fvVSXYEQs=; b=a8KPV6/mOGyGNB7afTKGC0xZg9BmiidMMe+H2wkk92nq4pTF1/YAGkAhBJTQY8PFlj 4svoptidbqiRgLPTGLyTPHZ4YZuay8y6LX+bi/w9qIqPzkJshTKueVSwxuNHnKa9bdsK 5Auw5VBr4BuwZfb+OrICmxwvi5Cq5iCZW8kILNAp1pqLGxDLYN8W+MX1ieBKyMmFp72F ieHVc1T29jAovM1/CrmETogwS9hm0yKXoxBeUOujU7kV8svXouPjsQhCQjfR9aVp/Vdi YVk+P8xXdAAaqDhHueWy+u4a9AzJ9qsrSIQYSnJhtbv41+3lpIVNzsCdcnvTtdMdfeQU +iIQ== X-Gm-Message-State: AOAM533gn0elSn04T2NRniKwdCPSycH3NGEav9a0bahizmOyShzntMPa WvF9E0bh5XRESOHhfWEpGHkKQIdDLPHx9bH0JieBAA== X-Received: by 2002:a05:600c:204a:: with SMTP id p10mr17594848wmg.136.1627313134086; Mon, 26 Jul 2021 08:25:34 -0700 (PDT) MIME-Version: 1.0 References: <20210722121757.1944658-1-jens.wiklander@linaro.org> <20210726105400.2li4fj223u3vajly@bogus> In-Reply-To: From: Jens Wiklander Date: Mon, 26 Jul 2021 17:25:23 +0200 Message-ID: Subject: Re: [PATCH v3 0/5] Add FF-A support in OP-TEE driver To: Sumit Garg Cc: Sudeep Holla , Linux Kernel Mailing List , linux-arm-kernel , OP-TEE TrustedFirmware , Marc Bonnici , Jerome Forissier , Sughosh Ganu Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Sumit, On Mon, Jul 26, 2021 at 1:41 PM Sumit Garg wrote: > > On Mon, 26 Jul 2021 at 16:25, Sudeep Holla wrote: > > > > On Mon, Jul 26, 2021 at 03:59:36PM +0530, Sumit Garg wrote: > > > Hi Jens, > > > > > > On Thu, 22 Jul 2021 at 17:48, Jens Wiklander wrote: > > > > > > > > Hi all, > > > > > > > > This adds supports for the OP-TEE driver to communicate with secure world > > > > using FF-A [1] as transport. > > > > > > > > There is one change to the TEE subsystem with "tee: add sec_world_id to > > > > struct tee_shm" to add support for holding globally unique handle assigned > > > > by the FF-A. This is a field that I believe could useful for the AMDTEE > > > > driver too. > > > > > > > > For communication the OP-TEE message protocol is still used, but with a new > > > > type of memory reference, struct optee_msg_param_fmem, to carry the > > > > information needed by FF-A. The OP-TEE driver is refactored internally with > > > > to sets of callbacks, one for the old SMC based communication and another > > > > set with FF-A as transport. The functions relating to the SMC based ABI > > > > are moved to smc_abi.c while the FF-A based ABI is added in a ffa_abi.c. > > > > > > > > There is also a difference in how the drivers are instantiated. With the > > > > SMC based transport we have a platform driver, module_platform_driver(), > > > > today which we're keeping as is for this configuration. In a FF-A system we > > > > have a FF-A driver, module_ffa_driver(), instead. > > > > > > > > The OP-TEE driver can be compiled for both targets at the same time and > > > > it's up to runtime configuration (device tree or ACPI) to decide how it's > > > > initialized. Note that it's only the old SMC based driver instance that > > > > need device tree or ACPI to initialize. The FF-A based driver relies on the > > > > FF-A bus instead. > > > > > > > > This can be tested QEMU > > > > The repo for SPMC at S-EL1 retrieved by > > > > repo init -u https://github.com/jenswi-linaro/manifest.git -m > > > > qemu_v8.xml -b ffav4_spmc > > > > repo sync > > > > # Then checkout the branch optee_ffa_v3 from > > > > # git://git.linaro.org/people/jens.wiklander/linux-tee.git > > > > # in the linux directory > > > > > > > > To build do: > > > > cd build > > > > make toolchains > > > > make all > > > > > > > > To boot: > > > > make run-only > > > > > > > > Test with xtest, perhaps only with the command "xtest 1004" in case you're > > > > not interested in too many tests. > > > > > > Thanks Jens for sharing instructions to test this feature. So I tried > > > to reproduce using following repo versions: > > > > > > linux-tee, branch: optee_ffa_v3 > > > trusted-firmware-a, branch: ffav4_sel1_spmc > > > build, branch: ffav4_spmc > > > > > > and rest of the repos synced to the latest version as per upstream > > > qemu_v8.xml [1] but I don't see OP-TEE driver being probed during boot > > > [2]. Am I missing something? > > > > > > [1] https://github.com/OP-TEE/manifest/blob/master/qemu_v8.xml > > > [2] > > > Welcome to Buildroot, type root or test to login > > > buildroot login: root > > > # dmesg | grep optee > > > > > > > Do you see ARM FF-A driver initialised successfully ? > > You must see "ARM FF-A Version 1.0 found" or something similar based on > > the actual version supported. > > > > If so, can you check if the partitions are correctly populated by > > the driver using the discover API. > > > > $ grep "" /sys/bus/arm_ffa/devices/*/uuid > > > > If uuid reads zeros, then the devices are populated, just the matching > > driver is not found(due to the workaround for v1.0 spec) > > > > It turns out to be an issue with my build environment, I re-built from > scratch and I could see OP-TEE being probed successfully: > > # dmesg | grep FF-A > [ 0.356382] ARM FF-A: Version 1.0 found > # > # cat /sys/bus/arm_ffa/devices/arm-ffa-8001/uuid > 486178e0-e7f8-11e3-bc5e-0002a5d5c51b > # > # dmesg | grep optee > [ 4.991472] optee: revision 3.14 (49dbb9ef) > [ 5.010110] optee: initialized driver > # That's good. > From xtest logs it looks like the pseudo TA interface isn't working for me: > > * regression_1001 Core self tests > - 1001 - skip test, pseudo TA not found > regression_1001 OK > > * regression_1002 PTA parameters > - 1002 - skip test, pseudo TA not found > regression_1002 OK > > * regression_1003 Core internal read/write mutex > - 1003 - skip test, pseudo TA not found > regression_1003 OK The test PTAs are disabled by default. > > Similarly, pseudo TAs acting as TEE bus devices doesn't work as well > as I see following devices directory being empty: > > # ls /sys/bus/tee/devices/ > # > > As otherwise with OP-TEE SMC ABI, we should have at least the default > pseudo TA [1] kernel device there. > > So is pseudo TA functional with this new FF-A interface? Yes, everything is supposed to work. Cheers, Jens