The dwmmc2 is used on Hikey 970 for WiFi support. The
hi3670.dtsi adds it, but with status="disabled".
For WiFi to work,it needs to be enabled. While here, add
the missing properties:
#address-cells = <0x1>;
#size-cells = <0x0>;
and add
ti,non-removable
To DT properties, as the WiFi support is on a non-removable slot.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts | 5 +++++
1 file changed, 5 insertions(+)
From: Robin Murphy <robin.murphy@arm.com> Date: 2020-08-26 12:42:03
On 2020-08-26 06:57, Mauro Carvalho Chehab wrote:
quoted hunk
The dwmmc2 is used on Hikey 970 for WiFi support. The
hi3670.dtsi adds it, but with status="disabled".
For WiFi to work,it needs to be enabled. While here, add
the missing properties:
#address-cells = <0x1>;
#size-cells = <0x0>;
and add
ti,non-removable
To DT properties, as the WiFi support is on a non-removable slot.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts | 5 +++++
1 file changed, 5 insertions(+)
Why? This property is only defined for OMAP HSMMC controllers, which
this isn't, and you've already got the proper generic property right
there below. Plus in terms of Linux it will have zero effect, since it's
only parsed by the omap_hsmmc driver anyway.
Em Wed, 26 Aug 2020 13:41:49 +0100
Robin Murphy [off-list ref] escreveu:
On 2020-08-26 06:57, Mauro Carvalho Chehab wrote:
quoted
The dwmmc2 is used on Hikey 970 for WiFi support. The
hi3670.dtsi adds it, but with status="disabled".
For WiFi to work,it needs to be enabled. While here, add
the missing properties:
#address-cells = <0x1>;
#size-cells = <0x0>;
and add
ti,non-removable
To DT properties, as the WiFi support is on a non-removable slot.
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
arch/arm64/boot/dts/hisilicon/hi3670-hikey970.dts | 5 +++++
1 file changed, 5 insertions(+)
Why? This property is only defined for OMAP HSMMC controllers, which
this isn't, and you've already got the proper generic property right
there below. Plus in terms of Linux it will have zero effect, since it's
only parsed by the omap_hsmmc driver anyway.