Received-SPF: pass (google.com: domain of linux-kernel+bounces-41857-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: Bjorn Andersson <andersson@kernel.org>
To: konrad.dybcio@linaro.org,
	Tao Zhang <quic_taozhan@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	kernel@quicinc.com
Subject: Re: [PATCH] qcom: smem: remove hwspinlock from item get routine
Date: Sun, 28 Jan 2024 11:45:52 -0600
Message-ID: <170646395043.64610.5018917783604688842.b4-ty@kernel.org>
In-Reply-To: <20240102022512.999635-1-quic_taozhan@quicinc.com>
References: <20240102022512.999635-1-quic_taozhan@quicinc.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit


On Tue, 02 Jan 2024 07:55:12 +0530, Tao Zhang wrote:
> During an SSR(Sub-System Restart) process, the remoteproc driver will
> try to read the crash reason from SMEM. The qcom_smem_get() backing such
> operations does however take the hwspinlock (tcsr mutex), which might be
> held by the dying remoteproc.
> 
> The associated timeout on the hwspin_lock_timeout_irqsave() would take
> care of the system not hanging forever, but the get operation will fail,
> unnecessarily delaying the process for the 'HWSPINLOCK_TIMEOUT' duration
> (currently is '1s'), and finally resulting in failure to get crash
> information from SMEM.
> 
> [...]

Applied, thanks!

[1/1] qcom: smem: remove hwspinlock from item get routine
      commit: 27825593c972abac86b9a4453a8c8c9a2c1ec60f

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>