From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: eeepc-laptop rfkill, stupid question #4 Date: Mon, 3 Nov 2008 14:55:43 +0000 Message-ID: <20081103145543.GA496@srcf.ucam.org> References: <20081031171126.GA17313@srcf.ucam.org> <490B4014.4040009@tuffmail.co.uk> <490B70A3.8010108@tuffmail.co.uk> <20081102040008.GB29606@khazad-dum.debian.net> <490D8C4E.3010201@tuffmail.co.uk> <20081102130655.GA12766@srcf.ucam.org> <20081103141628.GB31078@khazad-dum.debian.net> <20081103141836.GA31894@srcf.ucam.org> <490F0ACC.4000808@tuffmail.co.uk> <20081103145145.GD31078@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:43804 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755816AbYKCOzr (ORCPT ); Mon, 3 Nov 2008 09:55:47 -0500 Content-Disposition: inline In-Reply-To: <20081103145145.GD31078@khazad-dum.debian.net> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Henrique de Moraes Holschuh Cc: Alan Jenkins , linux-kernel , linux acpi On Mon, Nov 03, 2008 at 12:51:45PM -0200, Henrique de Moraes Holschuh wrote: > Not if you can enter or exit HARD_BLOCK, you're not. If you cannot it is > fine. But if you can, you really need to rfkill_force_state() on resume, The state can always be overridden by software, so I think we're fine there. > And the rfkill core seems to be buggy when you call force_state() on resume, > which you guys didn't hit because you're not doing it yet. See my other > email... Just to make sure: in the case where we *don't* support hard blocking, there's no need to do anything special in the driver on resume and rfkill should (but currently doesn't) do the right thing itself? -- Matthew Garrett | mjg59@srcf.ucam.org