Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp659198iog; Thu, 30 Jun 2022 07:52:27 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tib9hTH1j1G0eud54AgWUtervEYtC8bCpS90FlW+zRlp24/L0G9D5DR00trnuu7ZY2urYD X-Received: by 2002:a17:906:8461:b0:72a:8262:b066 with SMTP id hx1-20020a170906846100b0072a8262b066mr17480ejc.706.1656600747631; Thu, 30 Jun 2022 07:52:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656600747; cv=none; d=google.com; s=arc-20160816; b=suPuWndsUEUMc6E+QPrpPqwF9r4cSr+0tT+RzDthVqXeXkXc8h8ITZhsU2IajBNlAh inHHA1jDGGnXmXhXLs2999NwgPTtTzqi1CiMHZQImyt7jqayoZZYp32TJMnBGRFYF8jB R9qnDURaZRPRDCBnLuvTeNNd4PItCq2qPJ/P01okG/ic2F0SsG0U0f7uJC9ulrV9q/tx C4y3tKRUHnh+CqVx2acvDRbffGfO0oTIB7o0JQqXX01UhZj0Q4H1M/2ohuTcTrVQIVVM 1SWlYZjjaerfOPZ6lGX3Bs98tQi92Mi1GI+onwYlpVXpr/jRlIdWWLye704kf9d4sHoC +UWQ== 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-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=9Vy0Q0yOTMgozrHr/k/yV5yONhH9Zbt0a1EaEatVf+M=; b=JG6r1NBFkS+3lq2m8uP1F7mKDR6XrGbBXvrkOrC7ZD3v16JkmQkD5Gu9mGb20abagf HHOxF6NFtsxoi2qmirtFMS/+fEcxgzOxDX2O20p2AGM26rOunFCk3zx30DFxeBOwA+8d qnqfD6l4emp95nESGYi10dfsSPdAjgKA60H2OxH+Ikv8RyjKnf9lmcZzVFBeaMniaCY1 FL1aYTZB/IWTMSDyhkPiANzF/y4TUwblgIBtWABnEfp74yexA2QOZ73LVHreF5xdbNlh AGG2AGmXbDlWPnxEZNEIVdKGw4EnHhtGYiDndXoIbj7cSGTck8XMCFGrX0g5bfukNzJh CVrQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=r4J30h3b; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-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 cr11-20020a170906d54b00b00711c9d7c469si3222920ejc.1006.2022.06.30.07.52.00; Thu, 30 Jun 2022 07:52:27 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-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=@baylibre-com.20210112.gappssmtp.com header.s=20210112 header.b=r4J30h3b; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235513AbiF3Ovx (ORCPT + 99 others); Thu, 30 Jun 2022 10:51:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57850 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229966AbiF3Ovw (ORCPT ); Thu, 30 Jun 2022 10:51:52 -0400 Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 690741CFE7 for ; Thu, 30 Jun 2022 07:51:51 -0700 (PDT) Received: by mail-wr1-x42d.google.com with SMTP id s1so27676442wra.9 for ; Thu, 30 Jun 2022 07:51:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to; bh=9Vy0Q0yOTMgozrHr/k/yV5yONhH9Zbt0a1EaEatVf+M=; b=r4J30h3bEqLpGViZoCt3O4Hu1A5Wj8yEoXJyszGfn/2GIs+kmRDBHulPLdUyC4Ipgf 511lhEjeX6IjV6aAfF4VgBZrNrJgHftDLZbVV7kyp+6VJtKdZ/CQfMINKKgXtPTKNGZt 5L2uSoPR4Ll1ZcvuB0Pp5zfWhANJGiUi77pZuSpTenN24NJaiedqX+Ma26654YC4zDcg +hbWPRjgQObK+W99vRfGDLVj3QX/o1hqIR+2AYQhIKXLEOV2e98MCtRtla8lQgWG9uDV BCYikfSKz9/5Et7f0xcWox2UNv/tFKLx+pSXweXdeRvtvKiRMe0thmxCDXTmS1TYJ6OK Pvaw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to; bh=9Vy0Q0yOTMgozrHr/k/yV5yONhH9Zbt0a1EaEatVf+M=; b=dAhWqoJbDVXK98rArBjjwBrBHBE5OwZmbyG8nbxPG2+L3u1DqdBJCLIzcbx7OgkvOR QLC1hx6lCQG6qOX9foYMJSEJ/LOZWjJxrmYpxiCBZTaGzenF9qjApCbEsR0hC48XDICE 7Owiee6ypnEjytg4kQJE3YdsUr6+Xm8+qoEaEXn9VAaWlRGcmaogh6CIp7DqJLN4oMm3 iXXmU/v889Wi9/6BfCIFiIcljakUbmJe3vVQKUu/PbNBTJ0ZRYsLegeUZc93O4POgNfT +TcvwmFmlpPtF5cCpg19MWdqWcG0dIqjVGpX+r2N8lwsTRBmGXP3SEDOdbv9Axx/LE4i Tl5w== X-Gm-Message-State: AJIora/QUw6C/RVJSaUflk00ptsAUWFjXsSFK6+zxeOkuTgGKgrPEikp NC11NaGzy3KM9+s1IhxdAAz4FQ== X-Received: by 2002:a5d:47a1:0:b0:21d:1723:94f3 with SMTP id 1-20020a5d47a1000000b0021d172394f3mr8540807wrb.580.1656600710016; Thu, 30 Jun 2022 07:51:50 -0700 (PDT) Received: from Red ([2a01:cb1d:3d5:a100:264b:feff:fe03:2806]) by smtp.googlemail.com with ESMTPSA id r16-20020a05600c35d000b003a0375c4f73sm7209219wmq.44.2022.06.30.07.51.49 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Jun 2022 07:51:49 -0700 (PDT) Date: Thu, 30 Jun 2022 16:51:47 +0200 From: LABBE Corentin To: John Keeping Cc: heiko@sntech.de, ardb@kernel.org, herbert@gondor.apana.org.au, krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org Subject: Re: [PATCH v7 14/33] crypto: rockchip: handle reset also in PM Message-ID: References: <20220508185957.3629088-1-clabbe@baylibre.com> <20220508185957.3629088-15-clabbe@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,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-crypto@vger.kernel.org Le Tue, Jun 21, 2022 at 02:37:35PM +0100, John Keeping a ?crit : > On Tue, Jun 21, 2022 at 10:05:54AM +0200, LABBE Corentin wrote: > > Le Mon, Jun 20, 2022 at 12:04:24PM +0100, John Keeping a ?crit : > > > On Sun, May 08, 2022 at 06:59:38PM +0000, Corentin Labbe wrote: > > > > reset could be handled by PM functions. > > > > > > Is there any further rationale for this? > > > > > > After this change there is no longer a guaranteed reset pulse on probe > > > since the reset control may already be de-asserted. This is normally > > > the most important case for a reset as it's the only time when the state > > > of the hardware is unknown. > > > > > > The original use of devm_add_action_or_reset() seems a bit weird already > > > since there doesn't seem to be any need to assert reset when the driver > > > is unloaded. > > > > > > > I am not an hw engineer, so my knowledge on reset is low. > > So why not having a reset pulse on probe is a problem ? > > The point of the reset is to bring the hardware back to a known state. > Since we don't know what state the hardware will be in following the > bootloader or previous OS, I think the reset in probe is the only place > that it is important. > > If this patch isn't fixing anything, I suggest just dropping it. Thanks for the explanation, I will re-add the reset at probe.