Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp2519590pxb; Mon, 18 Jan 2021 22:02:28 -0800 (PST) X-Google-Smtp-Source: ABdhPJzkBSaxFKGov1Dsh6bIOtE8U5Af1zkmUh4WUQIl7WqrGJDIyoqtB44xkZtE+gL7+UddDJQo X-Received: by 2002:a17:906:e106:: with SMTP id gj6mr1847198ejb.337.1611036148222; Mon, 18 Jan 2021 22:02:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1611036148; cv=none; d=google.com; s=arc-20160816; b=Hac1MpDiTVsDrBhinwst81LQAwmEw715ra05lCwPUfkYrZ8n94aVtW3tsWvNWIY1pR 9NDezFSzMAHnlHjNJ8c0XsuPodXGf1r5cDNAGFWAsOvFA34/ArGRz1Jsoyey3nuicurL 4PEIq8NerRCAk88t8uZdqlyDvP9Z+UDXceU/M2a+VVA9Yiz2UfSdGewvV1SbjD0VUb/1 JMXULXqcbZLmEbWO4m9/uBl/RMuTbMNOUEJ5GjKAW8Fo6/D3B4Bbqo+FdwYvFIq7BKQW D+8+rM9D42+vjsjG6DsLNREhAJ8a3p2O1g9rbvASbcNnpOeyPZSsdeaWZw7trlU5zxgV YwEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=6N+mtJnAllpPqS59taAIm6aHXmVEI3uucSUB9g2qkoQ=; b=NPSJQV6nM6vfvxtpDlRbEPciDJNJ2lkPp9N7NI3QypEjDKsnY+5xWmn7szphZiJOAI hNpX9gu4unfMv+k/CV3idT5D44N0n4ojUX4l/smJAWm1YqTS3CQcnXM48VxkOBw8Grpq yyyQCcqNfAJlK/7V/HfCj9aLLvlUtE6Z32ijxSBLg9I7D/QW2PMT5Fz9FF0oeIRGT/7g 7/CgSj9tBrkilFmjXX29GesI2o25SZDs/kuDBgCTIa9rSUy6v3+GP9XqTI70jTIo47qW vxZJdsTKCo4hEMhBjvRUH+nZFN4mCLy/sWj3a/jvx5suRVqEjOFY9r/7uDgr9qqLuf+j dUtg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d92si8782212edd.33.2021.01.18.22.02.05; Mon, 18 Jan 2021 22:02:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730061AbhASEh3 (ORCPT + 99 others); Mon, 18 Jan 2021 23:37:29 -0500 Received: from mail-lf1-f50.google.com ([209.85.167.50]:40048 "EHLO mail-lf1-f50.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728481AbhASEdl (ORCPT ); Mon, 18 Jan 2021 23:33:41 -0500 Received: by mail-lf1-f50.google.com with SMTP id v24so20577847lfr.7; Mon, 18 Jan 2021 20:33:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6N+mtJnAllpPqS59taAIm6aHXmVEI3uucSUB9g2qkoQ=; b=VIPWjiecJyU8Lw2ZPDoI5NjzdbI72osiUVxaFoEadamdVx1uvG4KozptDDYE37pDQX /JJ6ugdGuGIgS6RnQEJZaYe+AXNjh9Ytk5/NSs6uUmABgqgyoBA2QKx0Qm04iHz88TeL OFWGwJRHR12PJhsVFkMygzsz2NXnZlmW+Da7EZXDEN7oSpw9xvEJXy28QtO950wKSSJl ea/vqVgOKLsTmP0telCJIfpJr5cmw3pD1TlNtplSa6150eX+r64oAEWnRHDFEiZRhZIo 305ediMKx3wWKwBuswRqeoLJ7qhyOmCMCVZYNjmmHPeEXAdhDwmpcHeNECg8sUXPxW/1 1DiA== X-Gm-Message-State: AOAM532zhopB3UiffNqKimlr1cRxcQAJ07cUf6QbJo0nNfxkEEDDgR6D Eb1m9Bj7tcYJkgxsjAvQiB0r2sU8gOU39Q== X-Received: by 2002:a19:991:: with SMTP id 139mr1042089lfj.637.1611030777529; Mon, 18 Jan 2021 20:32:57 -0800 (PST) Received: from mail-lf1-f50.google.com (mail-lf1-f50.google.com. [209.85.167.50]) by smtp.gmail.com with ESMTPSA id h1sm2147623lfc.121.2021.01.18.20.32.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Jan 2021 20:32:57 -0800 (PST) Received: by mail-lf1-f50.google.com with SMTP id v24so20577782lfr.7; Mon, 18 Jan 2021 20:32:56 -0800 (PST) X-Received: by 2002:ac2:4d44:: with SMTP id 4mr1116418lfp.296.1611030776537; Mon, 18 Jan 2021 20:32:56 -0800 (PST) MIME-Version: 1.0 References: <20210106134617.391-1-wens@kernel.org> In-Reply-To: <20210106134617.391-1-wens@kernel.org> From: Chen-Yu Tsai Date: Tue, 19 Jan 2021 12:32:45 +0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v3 0/4] arm64: rockchip: Fix PCIe ep-gpios requirement and Add Nanopi M4B To: Lorenzo Pieralisi , Shawn Lin , Heiko Stuebner , Bjorn Helgaas Cc: Chen-Yu Tsai , Rob Herring , Robin Murphy , Johan Jonker , PCI , "open list:ARM/Rockchip SoC..." , linux-arm-kernel , linux-kernel , devicetree Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, Jan 6, 2021 at 9:46 PM Chen-Yu Tsai wrote: > > From: Chen-Yu Tsai > > Hi everyone, > > This is v3 of my Nanopi M4B series. Changes since v2 include: > > - Replaced dev_err() with dev_err_probe() for gpiod_get_optional() error > - Added Reviewed-by tag from Robin Murphy for patch 3 > > Changes since v1 include: > > - Rewrite subject of patch 1 to match existing convention and reference > 'ep-gpios' DT property instead of the 'ep_gpio' field > > This series mainly adds support for the new Nanopi M4B, which is a newer > variant of the Nanopi M4. > > The differences against the original Nanopi M4 that are common with the > other M4V2 revision include: > > - microphone header removed > - power button added > - recovery button added > > Additional changes specific to the M4B: > > - USB 3.0 hub removed; board now has 2x USB 3.0 type-A ports and 2x > USB 2.0 ports > - ADB toggle switch added; this changes the top USB 3.0 host port to > a peripheral port > - Type-C port no longer supports data or PD > - WiFi/Bluetooth combo chip switched to AP6256, which supports BT 5.0 > but only 1T1R (down from 2T2R) for WiFi > > While working on this, I found that for the M4 family, the PCIe reset > pin (from the M.2 expansion board) was not wired to the SoC. Only the > NanoPC T4 has this wired. This ended up in patches 1 and 3. > > Patch 1 makes ep_gpio in the Rockchip PCIe driver optional. This property > is optional in the DT binding, so this just makes the driver adhere to > the binding. > > Patch 2 adds a new compatible string for the new board. > > Patch 3 moves the ep-gpios property of the pcie controller from the > common nanopi4.dtsi file to the nanopc-t4.dts file. > > Patch 4 adds a new device tree file for the new board. It includes the > original device tree for the M4, and then lists the differences. > > Given that patch 3 would make PCIe unusable without patch 1, I suggest > merging patch 1 through the PCI tree as a fix for 5.10, and the rest > for 5.11 through the Rockchip tree. Gentle ping. I would really like to get the PCIe controller fix merged before -rc6 (cut-off for arm-soc -next) and be able to get the new board into 5.12. Or we could have all of them merged for 5.12, though depending on the order the PRs are sent and merged by Linus there would be a possible window where PCIe doesn't work for the Nanopi M4's. Thanks ChenYu > Please have a look. The changes are mostly trivial. > > > Regards > ChenYu > > Chen-Yu Tsai (4): > PCI: rockchip: Make 'ep-gpios' DT property optional > dt-bindings: arm: rockchip: Add FriendlyARM NanoPi M4B > arm64: dts: rockchip: nanopi4: Move ep-gpios property to nanopc-t4 > arm64: dts: rockchip: rk3399: Add NanoPi M4B > > .../devicetree/bindings/arm/rockchip.yaml | 1 + > arch/arm64/boot/dts/rockchip/Makefile | 1 + > .../boot/dts/rockchip/rk3399-nanopc-t4.dts | 1 + > .../boot/dts/rockchip/rk3399-nanopi-m4b.dts | 52 +++++++++++++++++++ > .../boot/dts/rockchip/rk3399-nanopi4.dtsi | 1 - > drivers/pci/controller/pcie-rockchip.c | 5 +- > 6 files changed, 58 insertions(+), 3 deletions(-) > create mode 100644 arch/arm64/boot/dts/rockchip/rk3399-nanopi-m4b.dts > > -- > 2.29.2 >