From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pf1-f173.google.com (mail-pf1-f173.google.com [209.85.210.173]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 7AD842C11E6 for ; Mon, 3 Nov 2025 20:55:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.173 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762203351; cv=none; b=f97grfF6RjQiI8nyuOV3HQLIdAuTDovnoZhzVxUatXsbZxkAabZcijHRzNt1QxYXy728SGG5nWecVeq5tgAfQd6scQbgo8Wkq/9SrZssw03IRmZ6k5V21JyiguudDPLdA2BMBlODFdIned2yrDNbcyU8x3vdYuPVJJsy5j+t55A= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1762203351; c=relaxed/simple; bh=MNnc+69lZjEdoLNMNHpdOsL37uDyvF8N6B5j/i2FB1Y=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=rt0HJNevBiOVaHi3R8m4EmAfhdxz0Ua8wnEM1pr+njtNc4a7nlUcpuvOZCckTClaS0AHV7vspIEPKJmcjNVZ4osnU4n65AJBGLvD4aNewwUawo/ynrhUiXKxLXeU1aRb4s6HNDXqY7ahpBWtUn1NzqxeGg/Hyf4hpmYqD2UDjxU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com; spf=pass smtp.mailfrom=gmail.com; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b=l2OcNpEm; arc=none smtp.client-ip=209.85.210.173 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=gmail.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="l2OcNpEm" Received: by mail-pf1-f173.google.com with SMTP id d2e1a72fcca58-76e2ea933b7so4882796b3a.1 for ; Mon, 03 Nov 2025 12:55:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1762203350; x=1762808150; darn=vger.kernel.org; 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=T1FZmM9cdt+xj6V1Hd+gvwGWqSc0g8vu7TF1E04sPkw=; b=l2OcNpEmACr8JWpNNLwqV0fE5/Q8WdPZcCmzr0WtrcU5TNyxUwI2sVvEQzHJx6cJFG wILCbGqQV/B74yFiIk3mW9cPRH/Ous89Gav/EjTFBbL9YI9P8uz+vOslotKEkmX41Wlu Gta4YSeCoe7pme7MYSHRukmx3nGvlBChhmCSGUpFx+p8+StGb7WN77kWW4urxk6O9wlU +wzlPrTymXjjl0ZF3P0k5+atqbnbwhkUij8gpR0LPN39r7oDqw+J0c6c2ZBI4g71aJzm q3Y6IaW2RahFWb4L+UU+RvI/XvcN/0MrMJM0FJMdQJoQ+F/Y4npEsH8myWIUut6iLYoa nl8g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1762203350; x=1762808150; 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=T1FZmM9cdt+xj6V1Hd+gvwGWqSc0g8vu7TF1E04sPkw=; b=mN4JiDB8AJXXvCQBns9UP/zI+8xaW1u7nC/TnzlbglzUdXzVXAI6fTseoQ1PZsty02 zY683MO78/toXOROxQc59aMUHpOZY4yAfIHurMOdc8W1al9c+a3aVv21/rsFX9j8d78Q 1ze/lWj5/4n5AUDcq/yM3aJCdrtDrO7ZQoA5XwAF4HooplpxXhKetqLzJU/5smEtVJ7V zVpfuj5aazaJlR0WyMQDhs7cEfw/Z9zt4qFunEr3MVhUoh6GSPBSdgMALaWthpTIJdqU Mm3ZSTOSaWS1gJK30Lw0hntUrqcTkIYXzilkFy83ZP1WAZShJQojq++h4mEcmohvWwv8 PRVw== X-Forwarded-Encrypted: i=1; AJvYcCXApSs+5/y6nqLi8kNdxLPuu/PYqpn8f3o+UIV1Nu4+WZbCoCFFmFaM/QYGa1Dk6lC4UeEa8FDZEpb6qok=@vger.kernel.org X-Gm-Message-State: AOJu0Yyak6JyPVXTEIRRcq6+WbRzQjD3LB0usxGOkbMdJfjg3gJ43gSN TLDaOnQUpc+FjbYFxV0taJrwYJc+falWwRGwR223K6/9VX6e+g/ILOMO X-Gm-Gg: ASbGncsdEAidO4kppTmveEsmzT3T7sIztkaZSR2qBJ9lX+mW+Gl9GC7IAKQco9dory4 mL4OjWuq2zoV6s/gOzNNO1wkLEEcdi1/ZCHgYlNBhVqowjipL9WbHuCFY8xV9gxZhVumhHegMwt 6zIzXhrTvsT1i6eXvjNXsuAMhp9a619V0Ny34JdqIcnQsDAvOpEGksPCUS0T2x30+L9ywnWP4lq GufCrJmqLNmXOD5IYrRWFvmOP0Yp3yeIro5jNU7Nh3ISN6917QiSUf56hl1/qyUi/BL3Phc10k4 GRV/PZMZqdSdrc8uLslsh2xzHrBIx3of7f9EHbhpo1HK7zi2NPb8Jmp41nr9D3u7NMAP1h+jWa/ U3jmTF0SM/WfUp2vqjaSP9YBBAZdu74l3QfxoJ93w2IX+lVFH3uOQy+PUMVLzUw== X-Google-Smtp-Source: AGHT+IGYDVdNgNWocqi7ihWCrOOfROJ4jnfVXq0iLB5L8b6BF6bhkooF51PIKfTJUsi9RRg9FKFduA== X-Received: by 2002:a05:6a00:468a:b0:7aa:19a9:566a with SMTP id d2e1a72fcca58-7acbbb5a284mr818412b3a.0.1762203349654; Mon, 03 Nov 2025 12:55:49 -0800 (PST) Received: from geday ([2804:7f2:800b:e79::dead:c001]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-7acd623e091sm315775b3a.54.2025.11.03.12.55.45 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 03 Nov 2025 12:55:49 -0800 (PST) Date: Mon, 3 Nov 2025 17:55:38 -0300 From: Geraldo Nascimento To: Bjorn Helgaas Cc: linux-rockchip@lists.infradead.org, Shawn Lin , Lorenzo Pieralisi , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Manivannan Sadhasivam , Rob Herring , Bjorn Helgaas , Heiko Stuebner , linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Krzysztof Kozlowski , Conor Dooley , Johan Jonker Subject: Re: [RFC PATCH 2/2] PCI: rockchip-host: drop wait on PERST# toggle Message-ID: References: <20251103181038.GA1814635@bhelgaas> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20251103181038.GA1814635@bhelgaas> On Mon, Nov 03, 2025 at 12:10:38PM -0600, Bjorn Helgaas wrote: > On Mon, Nov 03, 2025 at 03:27:25AM -0300, Geraldo Nascimento wrote: > > With this change PCIe will complete link-training with a known quirky > > device - Samsung OEM PM981a SSD. This is completely against the PCIe > > spec and yet it works as long as the power regulator for 3v3 PCIe > > power is not defined as always-on or boot-on. > > What is against the spec? In what way is this SSD "known quirky"? Is > there a published erratum for it? Hi Bjorn! My proposed change itself is against the spec. This SSD is known to simply not complete initial link-training with Rockchip-IP PCIe. This is not officialy documented but based on reports across boards (like the Armbian one). I think it's the other way around though, it's the Rockchip-IP PCIe controller that is quirky somehow and doesn't play nice with many, many devices. > > Removing this delay might make this SSD work, but if this delay is > required per PCIe spec, how can we be confident that other devices > will still work? We really can't be sure there will be no side-effects to other devices. > > Reports of devices that still work is not really enough to move this > from the "hack that makes one device work" column to the "safe and > effective for all devices" column. I agree, and I knew from the start I would not get encouragements from the community relative to this change. Still, it seemed selfish not to share the workaround. > > It's easy to see how *lack* of a delay can break something, but much > harder to imagine how *removing* a delay can make something work. > Devices must be able to tolerate pretty much arbitrary delays. That said, the problem of quirky Rockchip-IP PCIe remains. The fact that removing the delay makes it work with devices that previously did not complete initial link training must at least point to a resolution somehow, even if the present change is unacceptable. I'll continue to hack around this, see if I can pinpoint exactly why that delay screws up my initial link training. Thanks, Geraldo Nascimento