[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAC=S1niCc5usY4SJ7wqtKAfcUqyTBf3fhRmkk4Sdnr3x2zsuVA@mail.gmail.com>
Date: Wed, 2 Oct 2024 11:35:38 +0800
From: Fei Shao <fshao@...omium.org>
To: Bjorn Helgaas <helgaas@...nel.org>
Cc: AngeloGioacchino Del Regno <angelogioacchino.delregno@...labora.com>,
Bjorn Helgaas <bhelgaas@...gle.com>, Conor Dooley <conor+dt@...nel.org>,
Jianjun Wang <jianjun.wang@...iatek.com>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Krzysztof Wilczyński <kw@...ux.com>,
Lorenzo Bianconi <lorenzo@...nel.org>, Lorenzo Pieralisi <lpieralisi@...nel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Matthias Brugger <matthias.bgg@...il.com>, Rob Herring <robh@...nel.org>,
Ryder Lee <ryder.lee@...iatek.com>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-mediatek@...ts.infradead.org, linux-pci@...r.kernel.org
Subject: Re: [PATCH 2/6] dt-bindings: PCI: mediatek-gen3: Allow exact number
of clocks only
On Wed, Oct 2, 2024 at 3:53 AM Bjorn Helgaas <helgaas@...nel.org> wrote:
>
> On Wed, Sep 25, 2024 at 06:57:46PM +0800, Fei Shao wrote:
> > In MediaTek PCIe gen3 bindings, "clocks" accepts a range of 1-6 clocks
> > across all SoCs. But in practice, each SoC requires a particular number
> > of clocks as defined in "clock-names", and the length of "clocks" and
> > "clock-names" can be inconsistent with current bindings.
> >
> > For example:
> > - MT8188, MT8192 and MT8195 all require 6 clocks, while the bindings
> > accept 4-6 clocks.
> > - MT7986 requires 4 clocks, while the bindings accept 4-6 clocks.
> >
> > Update minItems and maxItems properties for individual SoCs as needed to
> > only accept the correct number of clocks.
> >
> > Fixes: c6abd0eadec6 ("dt-bindings: PCI: mediatek-gen3: Add support for Airoha EN7581")
> > Signed-off-by: Fei Shao <fshao@...omium.org>
>
> It looks like most changes to this file have been merged via the PCI
> tree. I don't see dependencies on this in the rest of the series, so
> I'm happy to take this via PCI if it makes sense. Or if you prefer
> that this be merged with the rest of the series, that's fine and you
> can add my:
>
> Acked-by: Bjorn Helgaas <bhelgaas@...gle.com>
>
> Let me know if I should pick this one up.
>
Yes please, thank you!
Regards,
Fei
> > ---
> >
> > .../devicetree/bindings/pci/mediatek-pcie-gen3.yaml | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml b/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml
> > index 898c1be2d6a4..f05aab2b1add 100644
> > --- a/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml
> > +++ b/Documentation/devicetree/bindings/pci/mediatek-pcie-gen3.yaml
> > @@ -149,7 +149,7 @@ allOf:
> > then:
> > properties:
> > clocks:
> > - minItems: 4
> > + minItems: 6
> >
> > clock-names:
> > items:
> > @@ -178,7 +178,7 @@ allOf:
> > then:
> > properties:
> > clocks:
> > - minItems: 4
> > + minItems: 6
> >
> > clock-names:
> > items:
> > @@ -207,6 +207,7 @@ allOf:
> > properties:
> > clocks:
> > minItems: 4
> > + maxItems: 4
> >
> > clock-names:
> > items:
> > --
> > 2.46.0.792.g87dc391469-goog
> >
Powered by blists - more mailing lists