From: Jianjun Wang <jianjun.wang@mediatek.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Ryder Lee <ryder.lee@mediatek.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Rob Herring <robh+dt@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
<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 <Randy.Wu@mediatek.com>, <youlin.pei@mediatek.com>
Subject: Re: [PATCH 1/2] dt-bindings: PCI: mediatek-gen3: Add support for MT8195
Date: Tue, 1 Jun 2021 13:49:54 +0800 [thread overview]
Message-ID: <1622526594.9054.6.camel@mhfsdcap03> (raw)
In-Reply-To: <CAGXv+5G-8+ppafiUnqWm2UeiL+edHJ2zYZvU-S7mz_NdrM3YsA@mail.gmail.com>
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 <jianjun.wang@mediatek.com> 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.
Thanks.
>
>
> Thanks
> ChenYu
>
>
> > Signed-off-by: Jianjun Wang <jianjun.wang@mediatek.com>
> > ---
> > 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
next prev parent reply other threads:[~2021-06-01 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 2:44 [PATCH 0/2] PCI: mediatek-gen3: Add controller support for MT8195 Jianjun Wang
2021-06-01 2:44 ` [PATCH 1/2] dt-bindings: PCI: mediatek-gen3: Add " Jianjun Wang
2021-06-01 3:53 ` Chen-Yu Tsai
2021-06-01 5:49 ` Jianjun Wang [this message]
2021-06-01 6:07 ` Chen-Yu Tsai
2021-06-02 11:33 ` Matthias Brugger
2021-06-22 11:05 ` Lorenzo Pieralisi
2021-06-23 9:02 ` Jianjun Wang
2021-06-01 2:44 ` [PATCH 2/2] PCI: mediatek-gen3: Add controller " Jianjun Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1622526594.9054.6.camel@mhfsdcap03 \
--to=jianjun.wang@mediatek.com \
--cc=Randy.Wu@mediatek.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=ryder.lee@mediatek.com \
--cc=wenst@chromium.org \
--cc=youlin.pei@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).