netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Rompf <stefan@loplof.de>
To: "Ivo Van Doorn" <ivdoorn@gmail.com>
Cc: netdev@vger.kernel.org, "Jiri Benc" <jbenc@suse.cz>,
	"Francois Romieu" <romieu@fr.zoreil.com>,
	"Vojtech Pavlik" <vojtech@suse.cz>
Subject: Re: [PATCH RFC]rfkill - Hardware button support for Wireless cards
Date: Tue, 11 Jul 2006 00:34:47 +0200	[thread overview]
Message-ID: <200607110034.47944.stefan@loplof.de> (raw)
In-Reply-To: <a32f33a40607090849h737287a0k9f4d95669aa0ce9c@mail.gmail.com>

Am Sonntag, 9. Juli 2006 17:49 schrieb Ivo Van Doorn:

> I have been quite busy lately, hence the reason for this late continuance
> of the Hardware button support for Wireless cards discussion.
> I have CC'ed the people who discussed this in earlier threads.

no problem. Look good, just one thing I'm missing:

> +	For each registered hardware button an input device will be created.
> +	If this input device has been opened by the user, rfkill will send a
> +	signal to userspace instead of the hardware about the new button
> +	status. This will allow userpace to perform the correct steps
> +	in order to bring down all interfaces.

> +		if (rfkill->input_dev->users) {
> +			input_report_key(rfkill->input_dev,
> +				KEY_RFKILL, new_status);
> +			input_sync(rfkill->input_dev);

Shouldn't there be a continue to avoid calling enable/disable_radio()?

> +		}

Stefan

PS: This rfkill stuff is really caught between two stools. Sending a netlink 
event for the device with an additional TLV for radio button status seems as 
valid as sending an input event...

  reply	other threads:[~2006-07-10 22:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09 15:49 [PATCH RFC]rfkill - Hardware button support for Wireless cards Ivo Van Doorn
2006-07-10 22:34 ` Stefan Rompf [this message]
2006-07-19 11:32   ` Ivo Van Doorn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200607110034.47944.stefan@loplof.de \
    --to=stefan@loplof.de \
    --cc=ivdoorn@gmail.com \
    --cc=jbenc@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=romieu@fr.zoreil.com \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).