Received: by 2002:a05:7412:98c1:b0:fa:551:50a7 with SMTP id kc1csp177574rdb; Fri, 5 Jan 2024 06:33:43 -0800 (PST) X-Google-Smtp-Source: AGHT+IF9fwgumDNRqcnG/f8t1oJsV6R8aiJ9x8oesFEy22CMv2+AEzyV7kCXUmPTfUJo2H5rrBeu X-Received: by 2002:a17:902:7841:b0:1d4:e254:3548 with SMTP id e1-20020a170902784100b001d4e2543548mr1508428pln.19.1704465223354; Fri, 05 Jan 2024 06:33:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1704465223; cv=none; d=google.com; s=arc-20160816; b=sKxEWgpn415NGg6eLrTHM2Kk+1yptTQJ1/C4NOBvgHzsiS6M+1nBdXyId2pXDD0xfj Sp/GIafPoyUPimWpSQFW/Qjb3gsuBA6ZnGN8qsCAjPnU5+jJwrwvo08sqgaMwwdwr7CO l7Ui7BE1rpXzPfcLRXEHYMtKyy09+Hu8b3UeUs2stRMOmtElz9Xw7tn19jawfWiso1jn AZxMHGKnO32GjuwDIFFjOTNfPR4SRit8huUbUr3Jb9GoGHCWisMgudfwQ78dPRLhJXBC mu+I0uy0mV1CYJhgGCZXC3YbMAcgUy5hu9/2909NeXLBwYMZ+zvROSuind2cSaROR8cm phdw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-disposition:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:references:message-id:subject:cc :to:from:date:dkim-signature; bh=kSDPRl38X1YTU4bihb1dKsapYmqbe5IADh7owQbFqyQ=; fh=wpc1sBZ5IxLekpNzcnr3hCtq+M1wg48AzLrZOQjxmRE=; b=xm99kr8BgcSkTKQ82k2EJO9apId7vgYyWWvNXnDvfV8BSPpz+k1b2Y4EjxEhNWaLjo F2f9vqBrl9ZHOGncyWvZA6rYWfB90dGZAUof+/NRyx5XJDc9AV2DJU3c1SS4vTvsjFF2 4Oq7yZwDANFhaf+xNvl76HFgqSGKhTaKMBIGp3u/9C7yWz4D7kQvPuN3BwGBRNiQGySn tN8BYm2GTBx92N+dpxnCKBZCDXYSSmUllMocr0iZ7L/nChFPssq5RN3oJwFiNYGEASan ljk/bMHfRASo0UUOi5eNE7A9rNIjaHTo9HD3TEk4onxJoj/Mt1P8iw9Yv1VPjXURl/HR YEPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=eutmiK8m; spf=pass (google.com: domain of linux-kernel+bounces-17938-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-17938-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from sy.mirrors.kernel.org (sy.mirrors.kernel.org. [147.75.48.161]) by mx.google.com with ESMTPS id q14-20020a170902788e00b001d4dd652f58si1297691pll.31.2024.01.05.06.33.42 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 05 Jan 2024 06:33:43 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-17938-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=eutmiK8m; spf=pass (google.com: domain of linux-kernel+bounces-17938-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) smtp.mailfrom="linux-kernel+bounces-17938-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sy.mirrors.kernel.org (Postfix) with ESMTPS id 25D0DB20A96 for ; Fri, 5 Jan 2024 14:33:38 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 8E3DC18EB7; Fri, 5 Jan 2024 14:33:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="eutmiK8m" X-Original-To: linux-kernel@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id AD03024B5A; Fri, 5 Jan 2024 14:33:28 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 435F0C433C8; Fri, 5 Jan 2024 14:33:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1704465208; bh=PgXaKGN8DqZgvzqxm7EM/leplkV3k/W5tK0CswY8nxw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=eutmiK8mS7otKfg6XPGuMelGNRsbSuK9AVVvVKyRcSMEKSCGJCcM3oI0VFgUuBExW 3lSEarA0liHmqyg1YBMLz6mDQJ1U8t1uKiVqFSPhB0unRzFwwAfoRw4EPEMSxkYEU+ Z/0d0A6E6W4PNk+kVaGpZ2/FT4ZNrWs5bTR0be8EpZA8PZIdmN//fPUZffx/IZlvWR qSpmzpE6JcSmia1EWxAXjf9BVhKkp2AjRsMOPpi4f6a+Asuw14u2q+2uA+lgvK4gtu 9rry/bIyj+eKO2dpcVWYjXm0tNIheQvePJQeGGrGWb9aOgJ1+bhVpNKFwgsRweBLb2 iA8pe9otNIa3w== Date: Fri, 5 Jan 2024 14:33:21 +0000 From: Mark Brown To: Krzysztof Kozlowski Cc: Sean Anderson , Bjorn Andersson , Konrad Dybcio , Srinivas Kandagatla , Banajit Goswami , Liam Girdwood , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Philipp Zabel , Jaroslav Kysela , Takashi Iwai , linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org, linux-sound@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Bartosz Golaszewski Subject: Re: [PATCH 2/4] reset: add GPIO-based reset controller Message-ID: <758c4fe3-1ea1-4a8c-bb6f-3a3df588da75@sirena.org.uk> References: <20231222150133.732662-1-krzysztof.kozlowski@linaro.org> <20231222150133.732662-3-krzysztof.kozlowski@linaro.org> <530e3473-eb3b-477c-8599-e7aa12779640@seco.com> <88bd6668-7e67-42c7-97b6-d7029f371349@linaro.org> <075990bb-5fdb-4d30-9484-9df6b978e805@seco.com> <2be19fbf-4c73-4594-be42-31587dc7b747@seco.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="vImSMy+icUlzjZXl" Content-Disposition: inline In-Reply-To: X-Cookie: Your step will soil many countries. --vImSMy+icUlzjZXl Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Jan 04, 2024 at 08:08:50PM +0100, Krzysztof Kozlowski wrote: > On 04/01/2024 17:30, Sean Anderson wrote: > > device post-assert delay post-deassert delay > > ====== ================= =================== > > A 500us 1ms > > B 1ms 300us ... > Now, if we are back to realistic cases - use just the longest reset time. Isn't the main concern here that when one device probes we don't yet know the times for the other devices? > > If we leave things up to the drivers, then whoever probes first will get > > to decide the reset sequence. > In current design yes, but it's not a problem to change it. Where is the > limitation? Just read other values and update the reset time. We might have already done a reset by that time and earlier devices might prevent later devices from resetting again. It shouldn't be such an issue for the post delay, but might be one for the pre delay. --vImSMy+icUlzjZXl Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmWYEzAACgkQJNaLcl1U h9AUFQf8DiBunWd33PprmdlKCI899IHnZ7UxbOoI6wrUZN2Sv3Eo8tBt+XXsK2ZV h61S9/tKulQcEi1z6NLrCKslrceGCewQP3dzTMmas5F14hBDSXE4WEfCrHpcLgtZ r6eqUUCKIQSDhBDodrHOPSHFxvizmJqcGoFNlj+UUF6U0Mqxo1S3DY3Q4/6edGqj p35k9Tud8KLEQJ4By0206b90rthRaUicLXQXuEqRYrrkLWQsKLIjjnZSZmrOogEb OmGTeyk5lY67DXPrhGxYnHI0R+XiaDK4SJm07EfQmJoBfD0ShMgMicPBXod/kkG1 UUYU+vv8YIrLd/0AWrfdWORkiyteAA== =xDYl -----END PGP SIGNATURE----- --vImSMy+icUlzjZXl--