Received: by 2002:a05:6358:9144:b0:117:f937:c515 with SMTP id r4csp1187539rwr; Fri, 5 May 2023 10:15:13 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ52dDtY1A6eBs1XgRaSLvyiMUhgG57x26H73oVe9pBfLgSJeKog4lHktqsrjLVmjhHeEXZy X-Received: by 2002:a05:6a00:b8f:b0:637:3234:4e22 with SMTP id g15-20020a056a000b8f00b0063732344e22mr3253281pfj.23.1683306913421; Fri, 05 May 2023 10:15:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1683306913; cv=none; d=google.com; s=arc-20160816; b=jvniEtaQSrR3FcuWNtcJW2SEyg2nc84kPNN9NIwNuiyB3FNgIG3Zlk0c0b+1hBQrGs c42zp8JhEJSqKhoMGEPO3Kl6JDDjij4R3mW7/8fCr5vKjY/mLIt/dllAza/Zrw+SqlZ0 S4jgTzIgl36Q1kCAmVGoW9Oy9PGKjettM2yps9QnpFksYhAhqZhFgNtl/kz3AnDUzQy+ 9LcMbH0O1l4swe1Hy0C4gjnJWTeUxNfI2hp9hNeU6UKpplaJuGdZyUJhiTcbsOiK2hBP D9f+untZpuHCbTKBDTd57Rld5Sb9F8ySPtexk7QKXDvs89W9omt68qvBJ83nxwOxPlnF 5v7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=JMDVesgAKasFsor4GeKqlCagXQ7DH3+AoXUlf3OElm8=; b=iIw59WeS13E2pCnyUpuQI9zKuA7yso4DV/CX5OyRshFTcumImRAj5d9GkgM94kFJ7W 2YIgfcy8AaSatdQ6D+iW7QQxa+bBX9Ezz2OAWpB9hzm0al0Ia5DZcKUqjqswEQ1YiPVR v7maH72N+AD38cJXQqxrN0he3kZQkRlDW6ZAquovQ0Tkqq5um9YYLH0eCRwCEdqr+AtF 4rVA6P2OgXkDr/oNgd4aI5xkkbKzusu6G4bJHfPv3oe9uHng2V4wEI3Y+CaOTZzudSLW 4a4Os+kFbQ0PQZAnYzjCP/xmv7/EsUbKILDpsqXoaeKdjYnCNTRg0FjEs92fdRJRwEoS gEyQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=bR6gi0lc; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id g24-20020a633758000000b0051eff07b9f5si2429053pgn.84.2023.05.05.10.14.59; Fri, 05 May 2023 10:15:13 -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; dkim=pass header.i=@linaro.org header.s=google header.b=bR6gi0lc; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231784AbjEEREC (ORCPT + 99 others); Fri, 5 May 2023 13:04:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47118 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231611AbjEEREA (ORCPT ); Fri, 5 May 2023 13:04:00 -0400 Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6C7A8150FC for ; Fri, 5 May 2023 10:03:58 -0700 (PDT) Received: by mail-pl1-x635.google.com with SMTP id d9443c01a7336-1ab1ce53ca6so14552805ad.0 for ; Fri, 05 May 2023 10:03:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1683306238; x=1685898238; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=JMDVesgAKasFsor4GeKqlCagXQ7DH3+AoXUlf3OElm8=; b=bR6gi0lcTDkNWyn7wz8u78OloJBPQ6KfsiLCSKJtSrf/mwTyj4RnLq3ZZsQz1dPnbt YK9sctpzPhvjPa52msOKNb71MrX9QuGHxcjpZuU8MGICBCkBa6eWB9EHqDkaXzxExAeW FPSm1Tea8e42GTKd966cAYYcdLDWPu6xE/hQeQUEo8fWlHBrOmBhtHxUicyfTT6TJWZj gdLsXFigde8hbfEGXnwwZxx8j5oUZBhL4nJhOrzEA9MpP5f51RJbStN4VgCurhtsSYua lGPxMvVeQXhWZLel1UYlHTqXLmtDeCWCBZJiBnr6VZn0Ox3VVAsNLkc8agKkEFCtkjTl ZLCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683306238; x=1685898238; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=JMDVesgAKasFsor4GeKqlCagXQ7DH3+AoXUlf3OElm8=; b=NGdeCXxQCpGbhfN5U5OAu9noHznJWzQt2bla7Og8aQe8fDjjs4X5XRRDg1HsPJu0Az oS1dZnXWrcXqRW6chO/VPLrWR4Qi8lCMtdEMchr/IZjmWj3eeHp1jXcf5Pi4XfoqGEk7 M3QrXBXQGEhPhYkPOzqk6raJaFIyb6pittwQWsCWhnkmjxpRDgwZdNvr6cNM+wsKOxDa pxdYjz1UXX0VGpHk4nImwCkhf45ofhQbOXBTUbIEb8koOB+EDNSZZoEFidBETvtHIHSu x6POzpbo/pjs5mqcrOf1qoK3wqF22WkShpRKhsSjk7OwN07LhzskEAniJYKAfAI6yzDZ mokQ== X-Gm-Message-State: AC+VfDwYJJsspMcMEsJ3q+E+5xN9wgaLSMTAPVMWkE5goGH14XeGfvYQ OPPLolgSW4YRd32ricyNfjcpAQ== X-Received: by 2002:a17:902:6901:b0:1a1:956e:5417 with SMTP id j1-20020a170902690100b001a1956e5417mr1763516plk.22.1683306237785; Fri, 05 May 2023 10:03:57 -0700 (PDT) Received: from p14s ([2604:3d09:148c:c800:fd16:b4b6:ee7c:e4e5]) by smtp.gmail.com with ESMTPSA id c13-20020a170902d48d00b001994fc55998sm2013388plg.217.2023.05.05.10.03.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 05 May 2023 10:03:57 -0700 (PDT) Date: Fri, 5 May 2023 11:03:54 -0600 From: Mathieu Poirier To: Arnaud Pouliquen Cc: Rob Herring , Krzysztof Kozlowski , Bjorn Andersson , Alexandre Torgue , devicetree@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 2/4] remoteproc: stm32: Allow hold boot management by the SCMI reset controller Message-ID: References: <20230504094641.870378-1-arnaud.pouliquen@foss.st.com> <20230504094641.870378-3-arnaud.pouliquen@foss.st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230504094641.870378-3-arnaud.pouliquen@foss.st.com> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 Hi Arnaud, On Thu, May 04, 2023 at 11:46:39AM +0200, Arnaud Pouliquen wrote: > The hold boot can be managed by the SCMI controller as a reset. > If the "hold_boot" reset is defined in the device tree, use it. > Else use the syscon controller directly to access to the register. > The support of the SMC call is deprecated but kept for legacy support. > > Signed-off-by: Arnaud Pouliquen > --- > Updates vs previous version > - keep support of the "st,syscfg-tz" property for legacy compatibility > - rename secured_soc in hold_boot_smc for readability > - add comments to explain hold boot management. > - update commit message > --- > drivers/remoteproc/stm32_rproc.c | 78 +++++++++++++++++++++++--------- > 1 file changed, 57 insertions(+), 21 deletions(-) > > diff --git a/drivers/remoteproc/stm32_rproc.c b/drivers/remoteproc/stm32_rproc.c > index 7d782ed9e589..e9cf24274345 100644 > --- a/drivers/remoteproc/stm32_rproc.c > +++ b/drivers/remoteproc/stm32_rproc.c > @@ -79,6 +79,7 @@ struct stm32_mbox { > > struct stm32_rproc { > struct reset_control *rst; > + struct reset_control *hold_boot_rst; > struct stm32_syscon hold_boot; > struct stm32_syscon pdds; > struct stm32_syscon m4_state; > @@ -88,7 +89,7 @@ struct stm32_rproc { > struct stm32_rproc_mem *rmems; > struct stm32_mbox mb[MBOX_NB_MBX]; > struct workqueue_struct *workqueue; > - bool secured_soc; > + bool hold_boot_smc; > void __iomem *rsc_va; > }; > > @@ -401,13 +402,28 @@ static int stm32_rproc_set_hold_boot(struct rproc *rproc, bool hold) > struct arm_smccc_res smc_res; > int val, err; > > + /* > + * Three ways to manage the hold boot > + * - using SCMI: the hold boot is managed as a reset, > + * - using Linux(no SCMI): the hold boot is managed as a syscon register > + * - using SMC call (deprecated): use SMC reset interface > + */ > + > val = hold ? HOLD_BOOT : RELEASE_BOOT; > > - if (IS_ENABLED(CONFIG_HAVE_ARM_SMCCC) && ddata->secured_soc) { > + if (ddata->hold_boot_rst) { > + /* Use the SCMI reset controller */ > + if (!hold) > + err = reset_control_deassert(ddata->hold_boot_rst); > + else > + err = reset_control_assert(ddata->hold_boot_rst); > + } else if (IS_ENABLED(CONFIG_HAVE_ARM_SMCCC) && ddata->hold_boot_smc) { > + /* Use the SMC call */ > arm_smccc_smc(STM32_SMC_RCC, STM32_SMC_REG_WRITE, > hold_boot.reg, val, 0, 0, 0, 0, &smc_res); > err = smc_res.a0; > } else { > + /* Use syscon */ > err = regmap_update_bits(hold_boot.map, hold_boot.reg, > hold_boot.mask, val); > } > @@ -705,34 +721,54 @@ static int stm32_rproc_parse_dt(struct platform_device *pdev, > dev_info(dev, "wdg irq registered\n"); > } > > - ddata->rst = devm_reset_control_get_by_index(dev, 0); > + ddata->rst = devm_reset_control_get_optional(dev, "mcu_rst"); > + if (!ddata->rst) { > + /* Try legacy fallback method: get it by index */ > + ddata->rst = devm_reset_control_get_by_index(dev, 0); > + } > if (IS_ERR(ddata->rst)) > return dev_err_probe(dev, PTR_ERR(ddata->rst), > "failed to get mcu_reset\n"); > > /* > - * if platform is secured the hold boot bit must be written by > - * smc call and read normally. > - * if not secure the hold boot bit could be read/write normally > + * Three ways to manage the hold boot > + * - using SCMI: the hold boot is managed as a reset > + * The DT "reset-mames" property should be defined with 2 items: > + * reset-names = "mcu_rst", "hold_boot"; > + * - using SMC call (deprecated): use SMC reset interface > + * The DT "reset-mames" property is optional, "st,syscfg-tz" is required > + * - default(no SCMI, no SMC): the hold boot is managed as a syscon register > + * The DT "reset-mames" property is optional, "st,syscfg-holdboot" is required > */ > - err = stm32_rproc_get_syscon(np, "st,syscfg-tz", &tz); > - if (err) { > - dev_err(dev, "failed to get tz syscfg\n"); > - return err; > - } > > - err = regmap_read(tz.map, tz.reg, &tzen); > - if (err) { > - dev_err(dev, "failed to read tzen\n"); > - return err; > + ddata->hold_boot_rst = devm_reset_control_get_optional(dev, "hold_boot"); > + if (IS_ERR(ddata->hold_boot_rst)) { > + if (PTR_ERR(ddata->hold_boot_rst) == -EPROBE_DEFER) > + return PTR_ERR(ddata->hold_boot_rst); Here we know that devm_reset_control_get_optional() has returned an error that is not -EPROBE_DEFER and as such, I think we should return that error instead of continuing on with the probing. Calling dev_err_probe() should be just fine. Otherwise I'm good with this set. Many thanks for the enhanced explanation. Mathieu > + ddata->hold_boot_rst = NULL; > + } > + > + if (!ddata->hold_boot_rst && IS_ENABLED(CONFIG_HAVE_ARM_SMCCC)) { > + /* Manage the MCU_BOOT using SMC call */ > + err = stm32_rproc_get_syscon(np, "st,syscfg-tz", &tz); > + if (!err) { > + err = regmap_read(tz.map, tz.reg, &tzen); > + if (err) { > + dev_err(dev, "failed to read tzen\n"); > + return err; > + } > + ddata->hold_boot_smc = tzen & tz.mask; > + } > } > - ddata->secured_soc = tzen & tz.mask; > > - err = stm32_rproc_get_syscon(np, "st,syscfg-holdboot", > - &ddata->hold_boot); > - if (err) { > - dev_err(dev, "failed to get hold boot\n"); > - return err; > + if (!ddata->hold_boot_rst && !ddata->hold_boot_smc) { > + /* Default: hold boot manage it through the syscon controller */ > + err = stm32_rproc_get_syscon(np, "st,syscfg-holdboot", > + &ddata->hold_boot); > + if (err) { > + dev_err(dev, "failed to get hold boot\n"); > + return err; > + } > } > > err = stm32_rproc_get_syscon(np, "st,syscfg-pdds", &ddata->pdds); > -- > 2.25.1 >