Permalink
Browse files

bcm4330: Print an error that early_suspend was blocked

Some firmware bases, such as XXKI3, appear to have a broken DHCP setup
which permanently blocks early_suspend handling - allow this blocking
to show up in the dmesg, so people can figure out why the allow_pm_max
patch is doing nothing

Signed-off-by: Andrew Dodd <atd7@cornell.edu>
  • Loading branch information...
1 parent a7d3384 commit 86b36aa74d642aef455579140801449e089d6f02 @Entropy512 committed Feb 5, 2012
Showing with 2 additions and 0 deletions.
  1. +2 −0 drivers/net/wireless/bcm4330/src/dhd/sys/dhd_linux.c
@@ -712,6 +712,8 @@ static void dhd_suspend_resume_helper(struct dhd_info *dhd, int val)
dhdp->in_suspend = val;
if (!dhdp->suspend_disable_flag)
dhd_set_suspend(val, dhdp);
+ else
+ printk("bcm4330: early_suspend processing disabled, suspend_disable_flag is set by system.\n");
DHD_OS_WAKE_UNLOCK(dhdp);
}

1 comment on commit 86b36aa

@Entropy512
Owner

Whoops, forgot to clean up the commit message for this... It references an allow_pm_max patch which I never released to the wild or pushed to github as it seemed to do nothing but break things.

Please sign in to comment.