On Friday, January 17, 2014 2:54:45 AM UTC-5, Puneet B wrote:
>
> Hi,
>
> While tracing problem i found below issue.
>
> i am getting error in log as:
>
> [    4.780261] [dhd_module_init] get wl_host_wake gpio failed
>
> The code is from here:./
>
> vim linux-sunxi/drivers/net/wireless/bcmdhd/dhd_linux.c +4396
>
>         if (gpio_request(WL_HOST_WAKE_DEF_GPIO, "wl_host_wake")) {
>                 pr_warning("[%s] get wl_host_wake gpio failed\n", 
> __FUNCTION__);
>                 wl_host_wake = -1;
>                 return -1;
>         }
>
> Which means  some gpio error:
>
> In script for wifi:
> ap6xxx_wl_regon      = port:PH09<1><default><default><0>
> ap6xxx_wl_host_wake  = port:PH10<0><default><default><0>
> ap6xxx_bt_regon      = port:PB05<1><default><default><0>
> ap6xxx_bt_wake       = port:PI20<1><default><default><0>
> ap6xxx_bt_host_wake  = port:PI21<0><default><default><0>
> ap6xxx_lpo          = port:PI12<4><default><default><default>
>
>
> For ap6xxx_wl_host_wake  , i check by making high and low but error is 
> same.
>
> Can any one tell why that error is, Is it  because of some gpio pins or 
> something else went wrong?
>
> Regards
> Punith
>
> The problem is that the stock bcmdhd driver doesn't know how to toggle the 
allwinner gpios to turn on the chip.  Cubietech made some changes for that 
to  drivers/net/wireless/bcmdhd/dhd_custom_gpio.c, which is meant by 
Broadcom to be customized to different boards (thus the "custom" in the 
name).  It could all be abstracted pretty easily in the 3.4 linux-sunxi 
kernel, except for a few new calls to sunximmc_rescan_card made after power 
off and power on (probably not needed after the power off).

The mainline kernel abstracts this stuff much better than 3.4, so 
backporting might not be so easy.

Pat

-- 
You received this message because you are subscribed to the Google Groups 
"linux-sunxi" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to linux-sunxi+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to