Received: by 2002:a05:6358:489b:b0:bb:da1:e618 with SMTP id x27csp4906823rwn; Mon, 12 Sep 2022 00:45:38 -0700 (PDT) X-Google-Smtp-Source: AA6agR6pPgnW36WYTIHYyecEW4+yenZ2nl7dA+pGMwcTV3xzarHANLdxXNk3OwIP6yTvWHQN/ixO X-Received: by 2002:a17:903:509:b0:176:8db1:5ac8 with SMTP id jn9-20020a170903050900b001768db15ac8mr25356619plb.54.1662968738460; Mon, 12 Sep 2022 00:45:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1662968738; cv=none; d=google.com; s=arc-20160816; b=EQJx4TFUj6WLo3b6ZcitHKQ9bt5QBJBiua1n96DtdHY56YSRdI4U+9UhFBW0HPnOqa 2uDxxjLfVQqjVG0Uen2bO9bFlywtsvJ6xRynaZwSlTsL0RQgzC/HodkiI36k+tHoAMhr EsPlg4pdzxoHhx60UrF3ad94rCTWF7lXT79CWvwieZm9hf3affRQQw5zFEYZ4zc6AdPt FPnRapDizVbECVhHC2NWk/5OEg4l5knU+NjFKV9p2aogwXoOb3QTAo3fQQFpI4JzLOkz d6pnSVGnModzLEo4UPrw/LShFpUeMLgDBVQc5d8A6toum9hvVk/fnRUBaMSsLzqZ8tx6 c4Zw== 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:dkim-signature; bh=Kf+FkOZAH6AiTAa/Q5l98MlMhVQ6qbmRpLywVY10mCk=; b=BLB3coDc/5ecWC5XYLmN6LAGWEESX7VQ+osQvM9u5q9afZxsZhs13gOj53Yu69JrPR 7RisnruzlzV66osnIB4wIL8U3DGFOB/QTy8pq3lBZ1StQ/MgvE8SE/X1zCjsNipo6RtC LaC9357Kdj5RySdr6IqR4Tap5Gii0sktoaxzmOVivcosDfx18XM1r6YjEV6Cl0vYicZF HdV/Fas1mwG3GRubzNf7HfgWwcnRsb7u7ShLbL87CYjUwGYyDpvXNg0oQjby1jSoQE5c AFchMLwn1wXlR1SLL/GhqGpkcdCv2FdWpW87UT6td4Kf4Ab6noHzzqPSOSNBbyAJpfSY yZXA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lixom-net.20210112.gappssmtp.com header.s=20210112 header.b=PT7Vu5cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id c34-20020a631c22000000b00430841271dcsi8414538pgc.265.2022.09.12.00.45.25; Mon, 12 Sep 2022 00:45:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@lixom-net.20210112.gappssmtp.com header.s=20210112 header.b=PT7Vu5cz; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229572AbiILHF2 (ORCPT + 99 others); Mon, 12 Sep 2022 03:05:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43222 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229562AbiILHFZ (ORCPT ); Mon, 12 Sep 2022 03:05:25 -0400 Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 779211CFF4 for ; Mon, 12 Sep 2022 00:05:24 -0700 (PDT) Received: by mail-ej1-x633.google.com with SMTP id v16so17905306ejr.10 for ; Mon, 12 Sep 2022 00:05:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lixom-net.20210112.gappssmtp.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=Kf+FkOZAH6AiTAa/Q5l98MlMhVQ6qbmRpLywVY10mCk=; b=PT7Vu5cz2P1peiG8JmLn2GwcbupWOSdW6QG2r2oxPQ66p/B3g9Xe5GZHDdeDDIKCC3 YUtV5XVdg/9N9GyN1gByyrJMERlxwo4VaUzUHAHbTvGYF1SANtCLm6FV9aemWBjHcr6U 4hfPm+2zW71DtHZ0i7l1Ip7jS8pLrLdia/E9I8QQCI5IC1Ww3HprBOt04cw5IGcXnH0F 3+nZ8CHDL1DWyvIPsap+GGjA9uCmcmoomUtQnnmhIJIPK74LBOYGUr3VSWMaLeKGdn8Y H0erMsBLzYk3vt4vbZMflE1rtGXWnvfvj6SYRQOidg60Sg1jwtv4bd46i7Nf42J4APau /JWg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=Kf+FkOZAH6AiTAa/Q5l98MlMhVQ6qbmRpLywVY10mCk=; b=XWEQM2cnsHcyA8nBzGjQJJsy1jo3bZSeTjAPXreykhFJk8yGaFt9NGVgXBj+Zq/Sme JtFVCntyuCu61L3xnHQoZbm4PZPl5ZfpfoLR/QuojYxomQHYI8XGHXihmhi6IPGBVwpa tQ8/2xwaDiFRmoUIVdRl6jw1Qvl+apl4UlbBTwweRz93GCkHAvZSmiqcgJIQX9P48tB8 EfZYAP3j/6vhAHvMx8Of4AiqGxfvdLpzSKxTr1XxUFeCX2hrPgK35Pg26l9VQNlQmOz1 AO4/CLg7tFW61jK763xNL71UMH6X8RtYqkblTfELrHV6QDMC/ELbmG03BSOsvl5NvO9k NMkA== X-Gm-Message-State: ACgBeo2gjHlX8MB45HRUduQ1sqD4fhN14JYvnlaA5+YvAQOI7d8rspMi +4b+qbNEV6upa3IZCpLbYCCjvx252enOnlJKEKjF3w== X-Received: by 2002:a17:907:1690:b0:77c:37be:2345 with SMTP id hc16-20020a170907169000b0077c37be2345mr4714757ejc.359.1662966322965; Mon, 12 Sep 2022 00:05:22 -0700 (PDT) MIME-Version: 1.0 References: <20220817202538.21493-1-leoyang.li@nxp.com> <20220817202538.21493-2-leoyang.li@nxp.com> In-Reply-To: <20220817202538.21493-2-leoyang.li@nxp.com> From: Olof Johansson Date: Mon, 12 Sep 2022 00:05:11 -0700 Message-ID: Subject: Re: [PATCH v4 1/2] arm64: dts: lx2160a: update PCIe nodes to match rev2 silicon To: Li Yang Cc: shawnguo@kernel.org, devicetree@vger.kernel.org, robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Hou Zhiqiang Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, Aug 17, 2022 at 1:26 PM Li Yang wrote: > > The original dts was created based on the non-production rev1 silicon > which was only used for evaluation. Update the PCIe nodes to align with > the different controller used in production rev2 silicon. How can I confirm what version of silicon I have on a system? My non-evaluation commercially purchased system (HoneyComb LX2K) has: # cat /sys/bus/soc/devices/soc0/revision 1.0 And I will be really grumpy if this system stops working. It's what I use to do all my maintainer work, even if that's been fairly dormant this year. It's overall setting off red flags to update an in-place devicetree to a "new revision" of silicon instead of adding a new DT for said revision. 2160A has been on the market for several years, so it just seems odd to all of the sudden retroactively make things non-backwards-compatible. -Olof -Olof