[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240514072502.GA2463@thinkpad>
Date: Tue, 14 May 2024 09:25:02 +0200
From: Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: devi priya <quic_devipriy@...cinc.com>, bhelgaas@...gle.com,
lpieralisi@...nel.org, kw@...ux.com, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, andersson@...nel.org,
konrad.dybcio@...aro.org, mturquette@...libre.com, sboyd@...nel.org,
linux-arm-msm@...r.kernel.org, linux-pci@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-clk@...r.kernel.org
Subject: Re: [PATCH V5 3/6] dt-bindings: PCI: qcom: Document the IPQ9574 PCIe
controller.
On Mon, May 13, 2024 at 08:48:19AM +0200, Krzysztof Kozlowski wrote:
> On 12/05/2024 10:28, devi priya wrote:
>
> >
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + enum:
> > + - qcom,pcie-ipq9574
> > + then:
> > + properties:
> > + clocks:
> > + minItems: 6
> > + maxItems: 6
> > + clock-names:
> > + items:
> > + - const: ahb # AHB clock
> > + - const: aux # Auxiliary clock
> > + - const: axi_m # AXI Master clock
> > + - const: axi_s # AXI Slave clock
> > + - const: axi_bridge # AXI bridge clock
> > + - const: rchng
>
> That's introducing one more order of clocks... Please keep it
> consistent. The only existing case with ahb has it at after axi_m and
> others. Why making things everytime differently?
>
> I also to propose to finally drop the obvious comments, like "AHB
> clock". It cannot be anything else. AXI Master / slave are descriptive,
> so should stay.
>
+1 to drop the names.
- Mani
--
மணிவண்ணன் சதாசிவம்
Powered by blists - more mailing lists