[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<TYZPR03MB70012C66B789B09195FCD92580CD2@TYZPR03MB7001.apcprd03.prod.outlook.com>
Date: Mon, 17 Jun 2024 10:57:56 +0000
From: Jacobe Zang <jacobe.zang@...ion.com>
To: Alexey Charkov <alchark@...il.com>, "robh@...nel.org" <robh@...nel.org>,
"krzk+dt@...nel.org" <krzk+dt@...nel.org>, "conor+dt@...nel.org"
<conor+dt@...nel.org>, "heiko@...ech.de" <heiko@...ech.de>
CC: Nick Xie <nick@...das.com>, "efectn@...tonmail.com"
<efectn@...tonmail.com>, "jagan@...eble.ai" <jagan@...eble.ai>,
"dsimic@...jaro.org" <dsimic@...jaro.org>, "devicetree@...r.kernel.org"
<devicetree@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-rockchip@...ts.infradead.org"
<linux-rockchip@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 4/5] arm64: dts: rockchip: Add AP6275P wireless support
to Khadas Edge 2
>I'm also wondering why would adding a DT node for a PCI device be needed
>in the first place, given that PCI supports device discovery?
In fact, I learn that PCIe bus devices do not need compatible to probe just now... Before sending this patch, I committed the code that added "pci14e4,449d" to vendor-prefix.yaml and net/wireless/brcm,brcm4329-fmac.yaml. Now I know the reason why my addition was rejected. By the way, except for the compatible binding, is there any other binding that I should remove??
---
Best Regards
Jacobe
Powered by blists - more mailing lists