Firefly wifi mainline patches

Hi

I have managed to let my wifi working using mainline but I have problem on clocking. Right now I can not rise the clock more the 5Mhz even it's suppose to work up to 50Mhz. Anyone is working on it right now?

Michael

Hi

Quoted 7 lines · Michael Trimarchi

Hi

I have managed to let my wifi working using mainline but I have problem on clocking. Right now I can not rise the clock more the 5Mhz even it's suppose to work up to 50Mhz. Anyone is working on it right now?

I put in attach two patches that I need on my version. Another problem is that execute_tuning is not defined in the dw_mmc-rockchip so ENOSYS is returned. I think that we have two way:

1) put a stub
2) define 0 as default error

Michael

Quoted 1 line

Michael

_______________________________________________
Linux-rockchip mailing list [email protected]
http://lists.infradead.org/mailman/listinfo/linux-rockchip

Hi Michael,

You can ask and discuss about wifi here, but could you re-send you patches as described in [1] please ?

Short version:
1. git format-patch HEAD~2 # extract your two commits
2. scripts/get_maintainer.pl -f <changed_files> # list maintainers
3. git send-email --to --cc <emails listed by get_maintainer.pl> *.patch

From 661979de16b3d0d010659a2e601209aa894d55f4 Mon Sep 17 00:00:00 2001

From 4d68f996e28aa135a331e67ccd95874632276606 Mon Sep 17 00:00:00 2001

Thanks in advance,
Have a nice day,
Romain

1. https://www.kernel.org/doc/Documentation/SubmittingPatches

2015-07-22 7:58 GMT+02:00 Michael Trimarchi <[email protected]>:

Quoted 29 lines

Hi

Quoted 7 lines · Michael Trimarchi

Hi

I have managed to let my wifi working using mainline but I have problem on clocking. Right now I can not rise the clock more the 5Mhz even it's suppose to work up to 50Mhz. Anyone is working on it right now?

I put in attach two patches that I need on my version. Another problem is that execute_tuning is not defined in the dw_mmc-rockchip so ENOSYS is returned. I think that we have two way:

1) put a stub
2) define 0 as default error

Michael

Quoted 1 line

Michael

_______________________________________________
Linux-rockchip mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-rockchip

Hi

Quoted 7 lines · Michael Trimarchi

Hi

I have managed to let my wifi working using mainline but I have problem on clocking. Right now I can not rise the clock more the 5Mhz even it's suppose to work up to 50Mhz. Anyone is working on it right now?

I put in attach two patches that I need on my version. Another problem is that execute_tuning is not defined in the dw_mmc-rockchip so ENOSYS is returned. I think that we have two way:

1) put a stub
2) define 0 as default error

Hi,

Quoted 13 lines · Michael Trimarchi

Hi

Quoted 7 lines · Michael Trimarchi

Hi

I have managed to let my wifi working using mainline but I have problem on clocking. Right now I can not rise the clock more the 5Mhz even it's suppose to work up to 50Mhz. Anyone is working on it right now?

Quoted 6 lines

I put in attach two patches that I need on my version. Another problem is that execute_tuning is not defined in the dw_mmc-rockchip so ENOSYS is returned. I think that we have two way:

1) put a stub
2) define 0 as default error

I don't think you should be trying to tune until the tuning patches are landed. Alexandru sent them up a while ago but they need to be respun. I seem to remember Alexandru saying that it decided your controller was UHS capable if you didn't specify any capabilities, so maybe that's it.

Try adding this to your SDIO port in the dts:

cap-sd-highspeed;

Hi

Quoted 33 lines · Doug Anderson

Hi,

Quoted 13 lines · Michael Trimarchi

Hi

Quoted 7 lines · Michael Trimarchi

Hi

I have managed to let my wifi working using mainline but I have problem on clocking. Right now I can not rise the clock more the 5Mhz even it's suppose to work up to 50Mhz. Anyone is working on it right now?

Quoted 6 lines

I put in attach two patches that I need on my version. Another problem is that execute_tuning is not defined in the dw_mmc-rockchip so ENOSYS is returned. I think that we have two way:

1) put a stub
2) define 0 as default error

I don't think you should be trying to tune until the tuning patches are landed. Alexandru sent them up a while ago but they need to be respun. I seem to remember Alexandru saying that it decided your controller was UHS capable if you didn't specify any capabilities, so maybe that's it.

Try adding this to your SDIO port in the dts:

cap-sd-highspeed;

I have rebase on https://github.com/mmind/linux-rockchip
mainline/devel/upstream. Need to do some more test here and not yet ready for mainline

From f076b38f6056404cea11b1c5f4595dfe5b7e5aef Mon Sep 17 00:00:00 2001
From: Michael Trimarchi <michael-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>
Date: Thu, 23 Jul 2015 21:39:44 +0200
Subject: [PATCH] ARM: dts: rockchip: add wifi support to firefly board

This patch add the wifi support to firefly. In order to use the user need the ap6535 specific wifi firmware. vcc_wifi regulator is set to 2V in order to workaround the fact that the card answer to not support 1.8V power.

Signed-off-by Michael Trimarchi <michael-dyjBcgdgk7Pe9wHmmfpqLFaTQe2KTcn/@public.gmane.org>

---
 arch/arm/boot/dts/rk3288-firefly.dtsi | 35 +++++++++++++++++++++++++++++++++--
 1 file changed, 33 insertions(+), 2 deletions(-)

arch/arm/boot/dts/rk3288-firefly.dtsi +33 -3

index 20fa0ef..2958cd2 100644
@@ -117,6 +117,21 @@
                vin-supply = <&vcc_io>;
        };
 
+       vcc_wifi: wifi-regulator {
+               compatible = "regulator-fixed";
+               enable-active-high;
+               gpio = <&gpio4 28 GPIO_ACTIVE_HIGH>;
+               pinctrl-names = "default";
+               pinctrl-0 = <&sdio0_pwr>;
+               regulator-name = "vcc_wifi";
+               regulator-min-microvolt = <2000000>;
+               regulator-max-microvolt = <2000000>;
+               startup-delay-us = <100000>;
+               regulator-always-on;
+               vin-supply = <&vcc_io>;
+       };
+
+
        vcc_flash: flash-regulator {
                compatible = "regulator-fixed";
                regulator-name = "vcc_flash";

@@ -440,13 +455,29 @@
 &sdio0 {
        broken-cd;
        bus-width = <4>;
+       clock-freq-min-max = <400000 20000000>;
        disable-wp;
        non-removable;
+       cap-sd-highspeed;
        num-slots = <1>;
        pinctrl-names = "default";
-       pinctrl-0 = <&sdio0_bus4>, <&sdio0_cmd>, <&sdio0_clk>;
-       vmmc-supply = <&vcc_18>;
+       pinctrl-0 = <&sdio0_bus4>, <&sdio0_cmd>, <&sdio0_clk>, <&sdio0_int>;
+
+       sd-uhs-sdr12;
+       sd-uhs-sdr25;
+       cap-sdio-irq;
+
+       vmmc-supply = <&vcc_wifi>;
        status = "okay";
+
+       brcmf: bcrmf@1 {
+               compatible = "brcm,bcm4329-fmac";
+               interrupt-parent = <&gpio4>;
+               reg = <0>;
+               interrupts = <30 IRQ_TYPE_EDGE_FALLING>;
+               interrupt-names = "host-wake";
+               status = "okay";
+       };
 };
 
 &sdmmc {
--

1.9.1

--

| Michael Nazzareno Trimarchi                     Amarula Solutions BV |
| COO  -  Founder                                      Cruquiuskade 47 |
| +31(0)851119172                                 Amsterdam 1018 AM NL |
|                  [`as] http://www.amarulasolutions.com               |