[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2b5eb6f3-8e48-4248-bf26-4ebd358217ff@kernel.org>
Date: Mon, 3 Nov 2025 12:26:46 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Manivannan Sadhasivam <mani@...nel.org>
Cc: zhangsenchuan@...incomputing.com, bhelgaas@...gle.com,
krzk+dt@...nel.org, conor+dt@...nel.org, lpieralisi@...nel.org,
kwilczynski@...nel.org, robh@...nel.org, p.zabel@...gutronix.de,
jingoohan1@...il.com, gustavo.pimentel@...opsys.com,
linux-pci@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, christian.bruel@...s.st.com,
mayank.rana@....qualcomm.com, shradha.t@...sung.com,
krishna.chundru@....qualcomm.com, thippeswamy.havalige@....com,
inochiama@...il.com, ningyu@...incomputing.com, linmin@...incomputing.com,
pinkesh.vaghela@...fochips.com, ouyanghui@...incomputing.com
Subject: Re: [PATCH v4 1/2] dt-bindings: PCI: EIC7700: Add Eswin PCIe host
controller
On 03/11/2025 10:02, Manivannan Sadhasivam wrote:
>>> + interrupt-names:
>>> + items:
>>> + - const: msi
>>> + - const: inta
>>> + - const: intb
>>> + - const: intc
>>> + - const: intd
>>
>> Thse are legacy signals. Why are you using legacy?
>>
>
> Why not? These INTx signals are still supported by many host platforms/devices.
> These are not individual out-of-band signals, but just in-band messages. It is
> perfectly fine for a host controller to support them.
Considering how many other legacy things were used in this binding, I
just have doubts that choice of entries was correct.
Best regards,
Krzysztof
Powered by blists - more mailing lists