From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-173.mta0.migadu.com (out-173.mta0.migadu.com [91.218.175.173]) (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 3CA7E241A0F for ; Thu, 16 Jan 2025 22:55:44 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737068145; cv=none; b=Y8hdJo8lUxPLK6jzJoS35eFGzHlLHS7NgicPEk99h+i4cd2nlgraweYoNBNyYwebwsgelixVGPdSD5lJIUou5hR5N/BtwvHgmvDGX2R8ty7vpAizmfF9ElU92hpEf6zQ+dqMQF6c3SeooAcUxqx8Ng/jwS+ivkP/K5/QzCrZHPU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1737068145; c=relaxed/simple; bh=3SrMr/Jpx8XG9K5YUVmcBrgmtmKZBWkBlblLo/AdIhc=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=V+bNxLJCF7lDBQU3OjMKftcm2JmIzrOHehvR94aMegfKk1yO9gCVqATqWq+hjauZl9nRziFqEJsSgjMnUIEa42pZNAt3FoS3XT4r5Yaf7yGyv+cRc47TG5Wti5JK3netMI4vKEv8WN1rf15g3qmUKq26a4pwhGtb8YVf3Yny9qw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=XIkYNUOn; arc=none smtp.client-ip=91.218.175.173 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="XIkYNUOn" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1737068127; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=HpB5lB6azzxlrJkYukifNhmmPqI9KsgkZ1X5toy37xk=; b=XIkYNUOnuOMNraYswo1GWPm8iADUy2F3zZ3ceaUdiQFQiTUudbzNs78J2Qnx3AbJneWydC wQcHTwdtvO36b+cXEwGNCXu3UMTtvD6SSrqkCEAnYQjzvGrmh2Hbfs8SpFeExTraRmlaXX I99lNcLrzt3vJjIDZbK6EdCv9Ze8kSg= From: Sean Anderson To: Mark Brown , Michal Simek , linux-spi@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Jinjie Ruan , linux-arm-kernel@lists.infradead.org, Amit Kumar Mahapatra , Miquel Raynal , Sean Anderson , Conor Dooley , Krzysztof Kozlowski , Rob Herring , devicetree@vger.kernel.org Subject: [PATCH 0/5] spi: zynqmp-gqspi: Improve error recovery by resetting Date: Thu, 16 Jan 2025 17:55:16 -0500 Message-Id: <20250116225521.2688224-1-sean.anderson@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Migadu-Flow: FLOW_OUT This series adds support for resetting the QSPI controller if we have a timeout. I find this greatly improves the stability of the device, which would tend to break after any timeout. Sean Anderson (5): dt-bindings: spi: zynqmp-qspi: Add reset spi: zynqmp-gqspi: Reset device in probe spi: zynqmp-gqspi: Abort operations on timeout spi: zynqmp-gqspi: Allow interrupting operations ARM64: xilinx: zynqmp: Add QSPI reset .../bindings/spi/spi-zynqmp-qspi.yaml | 6 ++ arch/arm64/boot/dts/xilinx/zynqmp.dtsi | 1 + drivers/spi/spi-zynqmp-gqspi.c | 64 +++++++++++++++---- 3 files changed, 59 insertions(+), 12 deletions(-) -- 2.35.1.1320.gc452695387.dirty