Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3193271pxj; Mon, 31 May 2021 23:11:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyPCXKwurqHXIeWtWQ0hBOaGCobOQ4Mxrc0TWNCpz9EHtawP9gLzK0ziasugURq6ecajXAH X-Received: by 2002:a17:906:ff01:: with SMTP id zn1mr27728693ejb.119.1622527866236; Mon, 31 May 2021 23:11:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1622527866; cv=none; d=google.com; s=arc-20160816; b=Yjd4nVzOYQ8l6S8a+eUEZkfnkKn9jZ9EeQGttFxZyEJtFAHmWga9y6MTGpmkYre0d+ lJjtzNuR+vvr/SODAhh/PcBHtat93xl1kFr87C0e7YuVlHexkHThxPUDtCcFmx5PknAl 5kK11GImqowJO6uqeGT5HYKSmbnSX271SontDLWRndSoadqnjdyy0IZBkAxLiUDsWeSC MgCLJoypHyL5M4F+GhV8+h9bMAgAeCFNf0n7uSpiwHiEsf/S85s0pOJU6bba76Svpd0H aAvs8hKy8ZvA2TDiYfWcNV+wyz2mqOQarQl7wR61JD+VvyI1oG7whlWoyEb8dMIshxv+ Efqw== 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=h+RBOKgFnHiqXpmMdbi5LttMi0EzDR2w4eBfSKrv8y8=; b=pRJYtrRCs/9jDwtEeSooYECSFMZ4xT7eRsMhpFNKrzetMKDuU7RsdJklrPJbc4/nF+ B9yWXqkNTSgxDm9hW25t3uyCbbay8ST9TyUgaIwl8W5UQkCLyrBnU6MdcRm+WG0iG1Nc RujEPkvWzu4Szg5t2a38d46vsmry/XHDcQTuVoJ/NOkYtlZMWVMJHyTxI4iS8dP+PZL7 TAV1i46vfv6Kxh7eirjyzodFcMV3g7QPzWeP8kNSXXsjpiCq+PGzhoJ0f7LYA0Cua3OM EvMbE+TyX0nIzOTjOM07WNh57deYzFtVc/N4CkjWjCY1japa4G3kTeEjbb5/o3IWq7Hz HLCw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=SSwG5kX9; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i19si14843802edc.501.2021.05.31.23.10.43; Mon, 31 May 2021 23:11:06 -0700 (PDT) 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; dkim=pass header.i=@chromium.org header.s=google header.b=SSwG5kX9; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232934AbhFAGJw (ORCPT + 99 others); Tue, 1 Jun 2021 02:09:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53104 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231139AbhFAGJw (ORCPT ); Tue, 1 Jun 2021 02:09:52 -0400 Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8F352C061574 for ; Mon, 31 May 2021 23:08:11 -0700 (PDT) Received: by mail-lj1-x235.google.com with SMTP id w15so17628576ljo.10 for ; Mon, 31 May 2021 23:08:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=h+RBOKgFnHiqXpmMdbi5LttMi0EzDR2w4eBfSKrv8y8=; b=SSwG5kX9a/nZQ9+jle/gxa5cH3fac2/SAeuL8qINJ7JVa65PDXIGvQnqzPNvEzMlWl MRF2k/IQtRD/uROXpHtWpAxQ8cdA0fiNevDJT1lMFbidcMjCdqPcNFWUEeuVk6RZtuvJ NyaB9pANmXh6vNrXka9tRgd2Vh5Sevelfqj9s= 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=h+RBOKgFnHiqXpmMdbi5LttMi0EzDR2w4eBfSKrv8y8=; b=r8cRfVsmUPahS/pYgBX1zdlQ9sbinmPQaz00xFipHhhNV3aPAEHHi+kq9ZAURseIu4 /1gMc9344/lj0McJb9+6A8AQ4duDFjJ/3cLZ1eM5jBd5L/YhA2pLfOydycHU0/Fy6jAp SqXP5SXSc/3jQ2Z+dGI3ryOU1B0P0MT2t2iRnu5BrZwf8iBY/jKGho51drB9PS5xxUyV 9rf3LR33TnLcQ4H0lBZXwE1hiaBM1IjL6+NN4fxcbYX2iZpLCcVT14sjmExyhn/axQhK oL4xJ0DFNvdP1WJLmDWG10P+Gp7uzeMdZXvYdHUXDFFlA/hlLLa6h/FEag0oEmitrRt8 uBxQ== X-Gm-Message-State: AOAM530auZpDGFPlxu/UrVrtoumVsiLbsmNTES5a9ru+gCcq+VW0kImU 2PYYk4Pcj+wwzx1y1XaznZW3uicMmwzsiZSgcpAdkA== X-Received: by 2002:a2e:a554:: with SMTP id e20mr19052884ljn.23.1622527689964; Mon, 31 May 2021 23:08:09 -0700 (PDT) MIME-Version: 1.0 References: <20210601024408.24485-1-jianjun.wang@mediatek.com> <20210601024408.24485-2-jianjun.wang@mediatek.com> <1622526594.9054.6.camel@mhfsdcap03> In-Reply-To: <1622526594.9054.6.camel@mhfsdcap03> From: Chen-Yu Tsai Date: Tue, 1 Jun 2021 14:07:58 +0800 Message-ID: Subject: Re: [PATCH 1/2] dt-bindings: PCI: mediatek-gen3: Add support for MT8195 To: Jianjun Wang Cc: Ryder Lee , Bjorn Helgaas , Rob Herring , Lorenzo Pieralisi , Matthias Brugger , linux-pci@vger.kernel.org, linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Randy Wu , youlin.pei@mediatek.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Tue, Jun 1, 2021 at 1:50 PM Jianjun Wang wrote: > > On Tue, 2021-06-01 at 11:53 +0800, Chen-Yu Tsai wrote: > > Hi, > > > > On Tue, Jun 1, 2021 at 10:50 AM Jianjun Wang wrote: > > > > > > MT8195 is an ARM platform SoC which has the same PCIe IP with MT8192. > > > > Based on what I'm seeing internally, there seems to be some inconsistency > > across the MediaTek platform on whether new compatible strings should be > > introduced for "fully compatible" IP blocks. > > > > If this hardware block in MT8195 is "the same" as the one in MT8192, do we > > really need the new compatible string? Are there any concerns? > > Hi Chen-Yu, > > It's ok to reuse the compatible string with MT8192, but I think this > will be easier to find which platforms this driver is compatible with, > especially when we have more and more platforms in the future. If it's just for informational purposes, then having the MT8192 compatible as a fallback would work, and we wouldn't need to make changes to the driver. This works better especially if we have to support multiple operating systems that use device tree. So we would want "mediatek,mt8195-pcie", "mediatek,mt8192-pcie" and "mediatek,mt8192-pcie" be the valid options. Personally I'm not seeing enough value to justify adding the compatible string just for informational purposes though. One could easily discern which hardware is used by looking at the device tree. Regards ChenYu > Thanks. > > > > > > Thanks > > ChenYu > > > > > > > Signed-off-by: Jianjun Wang > > > --- > > > Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml | 4 +++- > > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > > > diff --git a/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml b/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml > > > index e7b1f9892da4..d5e4a3e63d97 100644 > > > --- a/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml > > > +++ b/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml > > > @@ -48,7 +48,9 @@ allOf: > > > > > > properties: > > > compatible: > > > - const: mediatek,mt8192-pcie > > > + oneOf: > > > + - const: mediatek,mt8192-pcie > > > + - const: mediatek,mt8195-pcie > > > > > > reg: > > > maxItems: 1 > > > -- > > > 2.18.0 > > > _______________________________________________ > > > Linux-mediatek mailing list > > > Linux-mediatek@lists.infradead.org > > > http://lists.infradead.org/mailman/listinfo/linux-mediatek >