From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f173.google.com (mail-pg1-f173.google.com [209.85.215.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 5462932197 for ; Fri, 5 Jan 2024 17:28:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=baylibre.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=baylibre.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=baylibre-com.20230601.gappssmtp.com header.i=@baylibre-com.20230601.gappssmtp.com header.b="DKU9Mesv" Received: by mail-pg1-f173.google.com with SMTP id 41be03b00d2f7-5cdbc4334edso1111770a12.3 for ; Fri, 05 Jan 2024 09:28:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20230601.gappssmtp.com; s=20230601; t=1704475729; x=1705080529; darn=vger.kernel.org; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:from:to:cc:subject:date:message-id:reply-to; bh=7MvMmIGG1OTvVGECDwkCBOvxHZpT09eejRG7w2yah/U=; b=DKU9MesvWUkllpmmd9HKqy+pBHXz2rmu50KCSN6VFS/KHFXS/z6LFRzKwI9aSNiSfU /T9dzElDk2owcXjMnlRFEuM5+ywubGSlSn0h+wsyVUHlPC3FnL2JwJIsJqScojx/TYck qoTEHMkHc1FbHqU80V+vcnMfDNb5VSEi0KCOVpXsR1NXvVLZHBWswAg1yDVgDMPN68F7 5WubSXiLmeZs5xGx9RbXhEE0FdgSSnY5UvHUfs/nPGe5jok86qcXHLsLgquOxg2LG2Hy 4PY9sYtfFJAzXUSVrV6vve7HvG7A0QBjnEOyxANftGKGtyJWDTkWBtr/bi8E9/Jyws58 1dfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704475729; x=1705080529; h=mime-version:message-id:date:references:in-reply-to:subject:cc:to :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=7MvMmIGG1OTvVGECDwkCBOvxHZpT09eejRG7w2yah/U=; b=myP28Cp/t/T0sOfwhI+oAaviqKJntpDcJgH7/FU7O2SZZZyWJyNYCj2moDQfy1cyCJ xO+JqPAELlWz2ryr5UPBwQ1YdyGgGqmrnYRHBcnQfbDuMnQu1WlEvShMrN8bklEYEXAF Tuyw0tYR3G+hXaVuvk8+nHC1pdziNRhYajoZ4XeHjSltjqj0etebAQLYqhPKXL3w6r+0 ZZg2dFwWDHR92+4KPDyG9Si6sxWBIte2k+gW4fOG/TJM6aNINqTfE0nN6Qtv+ucrZ9ap khZ4SGfBiYXRYQHLkf2G14C/rd//yy4KO/UnWClQ08kbdXJ0/ybcR6ou7kb8dJxuYBx9 C9Fg== X-Gm-Message-State: AOJu0Yypi6PO4RGO503MxifDUxmP8gqWnnfV0H8Xg7ad3WUx+oH4dsZi nDSKt4b8098G7W+68TeLwE9BNVLPqQHOMA== X-Google-Smtp-Source: AGHT+IHuOnm7hs+MIF/YDJktAeTmGWj9vojY0HSziqVUOflzq8jI2uyPNPQQRJu+YUAC/BW/uA1VRg== X-Received: by 2002:a05:6a21:6da6:b0:199:4e21:f71d with SMTP id wl38-20020a056a216da600b001994e21f71dmr690529pzb.87.1704475729519; Fri, 05 Jan 2024 09:28:49 -0800 (PST) Received: from localhost (75-172-121-199.tukw.qwest.net. [75.172.121.199]) by smtp.gmail.com with ESMTPSA id fi39-20020a056a0039a700b006dab0d09ef0sm1622087pfb.45.2024.01.05.09.28.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 05 Jan 2024 09:28:48 -0800 (PST) From: Kevin Hilman To: Kevin Xie , Minda Chen , Conor Dooley , Krzysztof =?utf-8?Q?Wilczy=C5=84ski?= , Rob Herring , Bjorn Helgaas , Lorenzo Pieralisi , Daire McNamara , Emil Renner Berthing , Krzysztof Kozlowski Cc: "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-riscv@lists.infradead.org" , "linux-pci@vger.kernel.org" , Paul Walmsley , Palmer Dabbelt , Albert Ou , Philipp Zabel , Mason Huo , Leyfoon Tan , Minda Chen Subject: Re: =?utf-8?B?5Zue5aSNOg==?= [PATCH v13 0/21] Refactoring Microchip PCIe driver and add StarFive PCIe In-Reply-To: References: <20231214072839.2367-1-minda.chen@starfivetech.com> <7hfrzeavmj.fsf@baylibre.com> Date: Fri, 05 Jan 2024 09:28:48 -0800 Message-ID: <7h34vbbsfj.fsf@baylibre.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain Kevin Xie writes: >> Minda Chen writes: >> >> > This patchset final purpose is add PCIe driver for StarFive JH7110 SoC. >> > JH7110 using PLDA XpressRICH PCIe IP. Microchip PolarFire Using the >> > same IP and have commit their codes, which are mixed with PLDA >> > controller codes and Microchip platform codes. >> >> Thank you for this series. >> >> I tested this on a VisionFive v2 board, and it seems to probe and find my >> M.2 NVMe SSD, but then gets timeouts when trying to use the NVMe (e.g. >> 'blkid' command) >> > > Hi, Kevin: > Could you please provide the manufacturer and model of the M.2 NVMe SSD > you tested? I have a 256 Gb Silicon Power P34A60 M.2 NVMe SSD (part number: sp256gbp34a60m28) Also for reference, I tested the same SSD on another arm platform (Khadas VIM3) and it works fine. Kevin