Received: by 2002:a05:6a10:413:0:0:0:0 with SMTP id 19csp676005pxp; Wed, 16 Mar 2022 14:11:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwOS5dq9IN12L3qXqnKm7fKVwe8b2CQTAx2Np+/hCtnGDWNU6NqmhA2veUa6jETmdMg+GsU X-Received: by 2002:a17:907:2cc2:b0:6df:7d01:3400 with SMTP id hg2-20020a1709072cc200b006df7d013400mr1522408ejc.309.1647465065650; Wed, 16 Mar 2022 14:11:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1647465065; cv=none; d=google.com; s=arc-20160816; b=NWVo5Ih/IsMj68y6UidRZQonGdrf3kmwBbykLzJWjfVVsZ98hVi1sWBtxYcFR/Z726 FWHVSc6n1msT4eSd2cqds+kL3VQvGouHXGwGV+NpFzXNtG+D2G7E2jOqnH8nVNQSB/Aj uL1p7C/atszOh51U45LfflP95FtPJkk6eB/gGbaeLwWdWNY4KA4WkG8/yqDSgi1vuaWQ BzCL314G/R3oxIlIfZrOZLQ8++A1yjjkqUph6Bvedchbo4UMePBIdk0hBAoBqzMAVMzi LhAYKhuGyMrj9kIuz0x+CLgf6VB/Bwu6BvlxEzFErM6jtmRkVqqcjjeTfnQiWgEOivU3 re5A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:from :references:to:content-language:subject:user-agent:mime-version:date :message-id; bh=N1rg/aobwFlgmcxFnuBknpDDW2cvGZpdCQSafidFUGo=; b=q8f2++tpx8/JlEz3bi6H76VyHYRm11kCiUqw9HCKW5RLYATMpoci4cADlAoFbl//v6 1flzTpJtz9E811cLcULyupn2Vyx/OyejGKOONL+etPWBmp+xN4cWDhCtfBwPq3Vu3QAT DjkwwqdoaAyfLVTkkwVp4Brr7gdwQ+AbpzsQfB1W61n18TOxdQydjanW9j/UMwJQhcwK pqykfzlZLqxijM9+xqohznR7W+MZW8a5e/89r62+1/empecD260+q8Yq8jMLmkQNyOa5 8oaUbpy8nB2qDAYH1zOuyJofjy4WrwQMxpgf8FQwwYq54ydk2FbeZb20lcGT/TiH1W5M bJmg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c25-20020a50f619000000b00418c2b5bf5esi160218edn.576.2022.03.16.14.10.40; Wed, 16 Mar 2022 14:11:05 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1355276AbiCPLSd (ORCPT + 99 others); Wed, 16 Mar 2022 07:18:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:54006 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1355272AbiCPLSb (ORCPT ); Wed, 16 Mar 2022 07:18:31 -0400 Received: from metis.ext.pengutronix.de (metis.ext.pengutronix.de [IPv6:2001:67c:670:201:290:27ff:fe1d:cc33]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9465D65787 for ; Wed, 16 Mar 2022 04:17:16 -0700 (PDT) Received: from gallifrey.ext.pengutronix.de ([2001:67c:670:201:5054:ff:fe8d:eefb] helo=[127.0.0.1]) by metis.ext.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1nUReM-0003ml-JI; Wed, 16 Mar 2022 12:17:06 +0100 Message-ID: Date: Wed, 16 Mar 2022 12:17:03 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Subject: Re: [Linux-stm32] [PATCH v2 12/13] ARM: dts: stm32: enable optee firmware and SCMI support on STM32MP13 Content-Language: en-US To: Etienne Carriere , Gabriel FERNANDEZ , Michael Turquette , Stephen Boyd , Rob Herring , Krzysztof Kozlowski , Maxime Coquelin , Alexandre Torgue , Philipp Zabel , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" , linux-stm32@st-md-mailman.stormreply.com, Pengutronix Kernel Team References: From: Ahmad Fatoum In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:201:5054:ff:fe8d:eefb X-SA-Exim-Mail-From: a.fatoum@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hello Etienne, On 16.03.22 12:01, Etienne Carriere wrote: > Hi Ahmad, > >> Helo Gabriel, >> >> On 03.03.22 14:09, Gabriel FERNANDEZ wrote: >>> >>> On 2/25/22 16:13, Ahmad Fatoum wrote: >>>> Hello Gabriel, >>>> >>>> On 25.02.22 14:31, gabriel.fernandez@foss.st.com wrote: >>>>> From: Gabriel Fernandez >>>>> + firmware { >>>>> + optee { >>>>> + method = "smc"; >>>>> + compatible = "linaro,optee-tz"; >>>>> + }; >>>>> + >>>>> + scmi: scmi { >>>>> + compatible = "linaro,scmi-optee"; >>>> This compatible doesn't seem to be documented upstream. I am looking at v5.17-rc5. >>>> Do you have a reference detailing the difference between this conduit and >>>> plain arm,scmi-smc (as used with TF-A on the STM32MP151). >>>> >>>> Cheers, >>>> Ahmad >>> >>> Hi >>> >>> Ahmad, >>> >>> it's on going. >>> >>> https://lore.kernel.org/linux-arm-kernel/20211029102118.GG6526@e120937-lin/T/#mf46c83f0aadce3061ee93fa22159405f38d881a0 >> >> I've found that thread in the meantime and got some clarification on why a new >> transport for OP-TEE was added. One question I still have though is why make >> this transport the default for STM32MP13x instead of using SCMI over SMC like >> you do for STM32MP15x. OP-TEE could still be made to service SCMI over SMC >> and it would allow people employing TF-A as SCMI provider an easier migration >> to the newer SoC. >> > > Just to rephrase a bit what's being said in the referred mail thread: > On STM32MP13x, there are SCMI messages that must be processed inside a > thread execution context in the SCMI server. There is no standard SMC > function ID defined that the SCMI/SMC transport could use for that > purpose. OP-TEE provides such a threaded context. Therefore STM32MP13x > explicitly expects SCMI services based on SCMI/OP-TEE transport, not > SCMI/SMC transport. I see. Users can still override it as they see fit and I understand that ST would prefer to have the "fully-featured" boot chain be the default for the new SoC. So no concerns from my side. Thanks a lot for the clarification! Cheers, Ahmad > > Best regards, > etienne > >> Cheers, >> Ahmad > >> >>> >>>> + #address-cells = <1>; >>>> + #size-cells = <0>; >>>> + linaro,optee-channel-id = <0>; >>>> + shmem = <&scmi_shm>; >>>> + >>>> + scmi_clk: protocol@14 { >>>> + reg = <0x14>; >>>> + #clock-cells = <1>; >>>> + }; >>>> + >>>> + scmi_reset: protocol@16 { >>>> + reg = <0x16>; >>>> + #reset-cells = <1>; >>>> + }; >>>> + }; >>>> + }; >>>> clocks { >>>> clk_axi: clk-axi { >>>> #clock-cells = <0>; >>> >> > > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |