DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.co.in;
  h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
  b=NGuOpfTexzDaRLKVRQQFlySBWqtOM2Kc6stWd/81LdG0SuQvsXkhFkDs4ZYdkAMaPQBlbW3EW1qE8z9NZ4A5QfB4kNRLVCdcoluik71nMl82zBiBEsxGlHIwNcTYmwxOZ+WG0GdwqG2UP186af4Ofmd+MwtD+hhLmx1uqPNzLws=;
Message-ID: <899595.96336.qm@web94915.mail.in2.yahoo.com>
Date: Wed, 9 Jun 2010 15:45:23 +0530 (IST)
From: Pavan Savoy <pavan_savoy@yahoo.co.in>
Subject: rfkill switch state during suspend?
To: Johannes Berg <johannes@sipsolutions.net>,
       Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20100326065803.GD26602@core.coreip.homeip.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1762
Lines: 57

Hi,

I remember in 2.6.29, the rfkill switch state during suspend was set to SOFT_BLOCKED by calling the toggle_radio of rfkill drivers.

What happens now ? 2.6.32+ ... ?

This previously posed a problems to drivers which mapped their chip enable GPIOs to the rfkill entries, because on suspend, the gpio was pulled low because of the SOFT_BLOCKED state.

A couple of lines regarding same in Documentation/rfkill.txt would be ideal too.

Thanks in advance.
Pavan Savoy.


--- On Fri, 26/3/10, Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:

> From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Subject: Re: [PATCH] rfkill: core: add custom rfkill switch
> To: "Johannes Berg" <johannes@sipsolutions.net>
> Cc: "Pavan Savoy" <pavan_savoy@yahoo.co.in>
> Date: Friday, 26 March, 2010, 12:28 PM
> On Thu, Mar 25, 2010 at 11:39:10PM
> -0700, Johannes Berg wrote:
> > On Thu, 2010-03-25 at 23:23 -0700, Dmitry Torokhov
> wrote:
> > 
> > > > I do have an actual driver it's just that
> all 3 cores are controlled
> > > > by 1 chip_enable and individual cores are
> powered up down by s/w
> > > > commands.
> > > > 
> > > 
> > > Hmm, so the main portion of the driver needs to
> count the number of
> > > active users across rfkill interfaces?
> before powering down the chip. I
> > > do not quite understand what the issue is
> here...
> > 
> > He also wants to (ab)use rfkill to signal to userspace
> what the value of
> > that counter is ...
> > 
> 
> Well, this one is easy - just say 'No' ;)
> 
> -- 
> Dmitry
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/