linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Charkov <alchark@gmail.com>
To: Jacobe Zang <jacobe.zang@wesion.com>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	heiko@sntech.de
Cc: nick@khadas.com, efectn@protonmail.com, jagan@edgeble.ai,
	dsimic@manjaro.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/5] arm64: dts: rockchip: Add AP6275P wireless support to Khadas Edge 2
Date: Mon, 17 Jun 2024 13:44:54 +0400	[thread overview]
Message-ID: <feeb8dcd-661f-415e-be08-afe175d0102e@gmail.com> (raw)
In-Reply-To: <20240617071112.3133101-5-jacobe.zang@wesion.com>


On 17/06/2024 10:11, Jacobe Zang wrote:
> Khadas Edge2 uses the PCI-e Ampak AP6275P 2T2R Wi-Fi 6 module.
>
> Signed-off-by: Jacobe Zang <jacobe.zang@wesion.com>
> ---
>   .../boot/dts/rockchip/rk3588s-khadas-edge2.dts  | 17 +++++++++++++++++
>   1 file changed, 17 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts b/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts
> index 233bab17bffd2..7d7cc3e76838c 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3588s-khadas-edge2.dts
> @@ -365,6 +365,23 @@ &pcie2x1l2 {
>   	reset-gpios = <&gpio3 RK_PD1 GPIO_ACTIVE_HIGH>;
>   	vpcie3v3-supply = <&vcc3v3_pcie_wl>;
>   	status = "okay";
> +
> +	pcie@0,0 {
> +		reg = <0x400000 0 0 0 0>;
> +		#address-cells = <3>;
> +		#size-cells = <2>;
> +		ranges;
> +		device_type = "pci";
> +		bus-range = <0x40 0x4f>;
> +
> +		wifi: wifi@0,0 {
> +			compatible = "pci14e4,449d";

This doesn't seem to be listed in the bindings, nor is there a mainline 
driver that would match either this compatible or PCI ID 14e4:449d. 
Maybe submit either or both of those first, to make sure they are 
reviewed and acceptable for mainline inclusion, before this change lands 
in DTS and becomes part of the ABI?

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? Does it 
require some sort of boot-time fixup by the bootloader? If so, it might 
be helpful to state that in comments.

Best regards,

Alexey



  reply	other threads:[~2024-06-17  9:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  7:11 [PATCH v2 0/5] arm64: dts: Add board support for Khadas Edge2 Jacobe Zang
2024-06-17  7:11 ` [PATCH v2 1/5] arm64: dts: rockchip: Add USB-C to Khadas Edge 2 Jacobe Zang
2024-06-17  7:11 ` [PATCH v2 2/5] arm64: dts: rockchip: Add bluetooth rfkill to Khadas Edge2 Jacobe Zang
2024-06-17  9:19   ` Alexey Charkov
2024-06-17  9:55     ` Jacobe Zang
2024-06-17 10:20       ` Alexey Charkov
2024-06-17 11:22         ` Jacobe Zang
2024-06-18  0:13           ` Sebastian Reichel
2024-06-18  2:34             ` Jacobe Zang
2024-06-17  7:11 ` [PATCH v2 3/5] arm64: dts: rockchip: Add HDMI & VOP2 to Khadas Edge 2 Jacobe Zang
2024-06-17 20:27   ` Heiko Stübner
2024-06-18  2:46     ` Jacobe Zang
2024-06-17  7:11 ` [PATCH v2 4/5] arm64: dts: rockchip: Add AP6275P wireless support " Jacobe Zang
2024-06-17  9:44   ` Alexey Charkov [this message]
2024-06-17 10:57     ` Jacobe Zang
2024-06-17 11:17       ` Alexey Charkov
2024-06-18  0:10         ` Sebastian Reichel
2024-06-18  3:27         ` Jacobe Zang
2024-06-17  7:11 ` [PATCH v2 5/5] arm64: dts: rockchip: Add cpufreq support to Khadas Edge2 Jacobe Zang
2024-06-17  8:33   ` Heiko Stübner
2024-06-17  9:09     ` Alexey Charkov
2024-06-17  9:41       ` Jacobe Zang

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=feeb8dcd-661f-415e-be08-afe175d0102e@gmail.com \
    --to=alchark@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=efectn@protonmail.com \
    --cc=heiko@sntech.de \
    --cc=jacobe.zang@wesion.com \
    --cc=jagan@edgeble.ai \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=nick@khadas.com \
    --cc=robh@kernel.org \
    /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).