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 7F48FC433EF for ; Fri, 17 Jun 2022 07:22:10 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1380525AbiFQHWI (ORCPT ); Fri, 17 Jun 2022 03:22:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34106 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233816AbiFQHWH (ORCPT ); Fri, 17 Jun 2022 03:22:07 -0400 Received: from mx07-00178001.pphosted.com (mx08-00178001.pphosted.com [91.207.212.93]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8E509CD; Fri, 17 Jun 2022 00:22:04 -0700 (PDT) Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 25H6R3Qk027749; Fri, 17 Jun 2022 09:21:42 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=selector1; bh=p1qmrfCOoCbbUibM0+WEnfsxFHthpkh+3u0jey7B2CQ=; b=Y1Yv1mxUyz99/KsdD+GqnRfdiGxjIC+9iqzRTZCxmISgn5dmu54MvQ90UuP4T3s0zmz/ VMy5WzAjMy9jmb7XttGerKsRbuEjYxhoPVzgUl6PevqlGKIWy90MkfVvVpEwhzvjHclV qe2enatExrY214PhAbI+1YA1UWdn8Bo9DkThHjoj10mXV1ctlz5wRCuV3WybsG/a6cZD mqk1kRFKNAj9Kz4ZgL9k1V/yUqH7J4RHKF32iZ+2cN0P5Wkz5W9QgxZy8vdvirNKhOiB cTB1mHuHN0n3K4Mbz/xuux+N0jVBxeahb82uT1DEijuZJ1NULio/GVjx+J8GRCkaP4DS dQ== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com (PPS) with ESMTPS id 3grmbw0adk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 17 Jun 2022 09:21:42 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 1858710002A; Fri, 17 Jun 2022 09:21:41 +0200 (CEST) Received: from Webmail-eu.st.com (shfdag1node1.st.com [10.75.129.69]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 8C08A21683B; Fri, 17 Jun 2022 09:21:41 +0200 (CEST) Received: from [10.201.21.93] (10.75.127.119) by SHFDAG1NODE1.st.com (10.75.129.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.20; Fri, 17 Jun 2022 09:21:41 +0200 Message-ID: Date: Fri, 17 Jun 2022 09:21:40 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13 Content-Language: en-US To: Rob Herring CC: Krzysztof Kozlowski , , , , References: <20220613093815.18334-1-alexandre.torgue@foss.st.com> <20220616175531.GA3716982-robh@kernel.org> From: Alexandre TORGUE In-Reply-To: <20220616175531.GA3716982-robh@kernel.org> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.75.127.119] X-ClientProxiedBy: GPXDAG2NODE5.st.com (10.75.127.69) To SHFDAG1NODE1.st.com (10.75.129.69) X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.64.514 definitions=2022-06-17_06,2022-06-16_01,2022-02-23_01 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Rob On 6/16/22 19:55, Rob Herring wrote: > On Mon, Jun 13, 2022 at 11:38:15AM +0200, Alexandre Torgue wrote: >> Like for stm32mp15, when stm32 RCC node is used to interact with a secure > > 'st,stm32mp1' is stm32mp15? Yes "st,stm32mp1-rcc" is for the STM32MP15. > >> context (using clock SCMI protocol), a different path has to be used for >> yaml verification. >> >> Signed-off-by: Alexandre Torgue >> >> --- >> >> Hi Rob, Krzysztof, >> >> If you agree with this patch, I'll apply it directly in my STM32 tree. >> >> Thanks >> Alex >> >> diff --git a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml >> index f8c474227807..242fe922b035 100644 >> --- a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml >> +++ b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml >> @@ -78,6 +78,7 @@ if: >> contains: >> enum: >> - st,stm32mp1-rcc-secure >> + - st,stm32mp13-rcc > > You don't need '-secure' because it's always secure? Yes. Compare to STM32MP15, the STM32MP13 is by default "secure". In our case it is "mapped" to OPTEE, using SCMI protocols. regards Alex > >> then: >> properties: >> clocks: >> -- >> 2.17.1 >> >> 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id F0BDBC433EF for ; Fri, 17 Jun 2022 07:35:57 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: Content-Transfer-Encoding:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:From:References:CC:To:Subject: MIME-Version:Date:Message-ID:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=8ISHs2EJ4246zoSxQDpcMMGssvPpyJu75XKvkna6rn4=; b=a3ygNa7Ndpl5KW /uCvizg0SOZrDejR2XIg75dXfNLuKTHFJLNq3wgXP2Y7gHnEU7hT9GJ1/os/D1iByxAgrn9LgL47r hfizosbZF7AdXKYSI9iVgsMexf1mHmIrqQZLepjLnjFrrx+wbJaY8ObOJHXszIPDBndAZ+wRmrLpJ cLmj1kPb5dMRWFz44vQrtb2krMqF12sWLioqntDHr58GLjkBXS/lfb0xstKY3SfWt2X/zJbO7pNaJ NyMs+Rm7wScF3x/hs17XI1R6gT+zzRFkxH7cJ6BItrrt6XJIb7AS73RTxBRXBicYkwfx6VgL/f/kn lU9FtQp1f0gMVypCiKaw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1o26VA-005zdz-6U; Fri, 17 Jun 2022 07:34:45 +0000 Received: from mx08-00178001.pphosted.com ([91.207.212.93] helo=mx07-00178001.pphosted.com) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1o26Ip-005vMS-Kw for linux-arm-kernel@lists.infradead.org; Fri, 17 Jun 2022 07:22:02 +0000 Received: from pps.filterd (m0046661.ppops.net [127.0.0.1]) by mx07-00178001.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 25H6R3Qk027749; Fri, 17 Jun 2022 09:21:42 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foss.st.com; h=message-id : date : mime-version : subject : to : cc : references : from : in-reply-to : content-type : content-transfer-encoding; s=selector1; bh=p1qmrfCOoCbbUibM0+WEnfsxFHthpkh+3u0jey7B2CQ=; b=Y1Yv1mxUyz99/KsdD+GqnRfdiGxjIC+9iqzRTZCxmISgn5dmu54MvQ90UuP4T3s0zmz/ VMy5WzAjMy9jmb7XttGerKsRbuEjYxhoPVzgUl6PevqlGKIWy90MkfVvVpEwhzvjHclV qe2enatExrY214PhAbI+1YA1UWdn8Bo9DkThHjoj10mXV1ctlz5wRCuV3WybsG/a6cZD mqk1kRFKNAj9Kz4ZgL9k1V/yUqH7J4RHKF32iZ+2cN0P5Wkz5W9QgxZy8vdvirNKhOiB cTB1mHuHN0n3K4Mbz/xuux+N0jVBxeahb82uT1DEijuZJ1NULio/GVjx+J8GRCkaP4DS dQ== Received: from beta.dmz-eu.st.com (beta.dmz-eu.st.com [164.129.1.35]) by mx07-00178001.pphosted.com (PPS) with ESMTPS id 3grmbw0adk-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 17 Jun 2022 09:21:42 +0200 Received: from euls16034.sgp.st.com (euls16034.sgp.st.com [10.75.44.20]) by beta.dmz-eu.st.com (STMicroelectronics) with ESMTP id 1858710002A; Fri, 17 Jun 2022 09:21:41 +0200 (CEST) Received: from Webmail-eu.st.com (shfdag1node1.st.com [10.75.129.69]) by euls16034.sgp.st.com (STMicroelectronics) with ESMTP id 8C08A21683B; Fri, 17 Jun 2022 09:21:41 +0200 (CEST) Received: from [10.201.21.93] (10.75.127.119) by SHFDAG1NODE1.st.com (10.75.129.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2308.20; Fri, 17 Jun 2022 09:21:41 +0200 Message-ID: Date: Fri, 17 Jun 2022 09:21:40 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.1 Subject: Re: [PATCH] dt-bindings: rcc: stm32: select the "secure" path for stm32mp13 Content-Language: en-US To: Rob Herring CC: Krzysztof Kozlowski , , , , References: <20220613093815.18334-1-alexandre.torgue@foss.st.com> <20220616175531.GA3716982-robh@kernel.org> From: Alexandre TORGUE In-Reply-To: <20220616175531.GA3716982-robh@kernel.org> X-Originating-IP: [10.75.127.119] X-ClientProxiedBy: GPXDAG2NODE5.st.com (10.75.127.69) To SHFDAG1NODE1.st.com (10.75.129.69) X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.64.514 definitions=2022-06-17_06,2022-06-16_01,2022-02-23_01 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220617_002200_753335_EA637F20 X-CRM114-Status: GOOD ( 15.58 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Rob On 6/16/22 19:55, Rob Herring wrote: > On Mon, Jun 13, 2022 at 11:38:15AM +0200, Alexandre Torgue wrote: >> Like for stm32mp15, when stm32 RCC node is used to interact with a secure > > 'st,stm32mp1' is stm32mp15? Yes "st,stm32mp1-rcc" is for the STM32MP15. > >> context (using clock SCMI protocol), a different path has to be used for >> yaml verification. >> >> Signed-off-by: Alexandre Torgue >> >> --- >> >> Hi Rob, Krzysztof, >> >> If you agree with this patch, I'll apply it directly in my STM32 tree. >> >> Thanks >> Alex >> >> diff --git a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml >> index f8c474227807..242fe922b035 100644 >> --- a/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml >> +++ b/Documentation/devicetree/bindings/clock/st,stm32mp1-rcc.yaml >> @@ -78,6 +78,7 @@ if: >> contains: >> enum: >> - st,stm32mp1-rcc-secure >> + - st,stm32mp13-rcc > > You don't need '-secure' because it's always secure? Yes. Compare to STM32MP15, the STM32MP13 is by default "secure". In our case it is "mapped" to OPTEE, using SCMI protocols. regards Alex > >> then: >> properties: >> clocks: >> -- >> 2.17.1 >> >> _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel