From: Johannes Berg <johannes@sipsolutions.net>
To: Pavan Savoy <pavan_savoy@yahoo.co.in>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rfkill: core: add custom rfkill switch
Date: Fri, 26 Mar 2010 10:12:38 -0700 [thread overview]
Message-ID: <1269623558.4342.0.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <911285.11966.qm@web94910.mail.in2.yahoo.com>
On Fri, 2010-03-26 at 21:43 +0530, Pavan Savoy wrote:
> Well, Almost, I don't want to signal the user-space about the counter.
> Have a look @ http://lkml.org/lkml/2010/3/24/303
>
> See the kernel space (bluetooth driver) would register itself, to my line discipline driver, when someone does a 'hciconfig hci0 up' which is essentially BT-On.
>
> So, now from my ldisc driver (which intends to mux BT/FM and GPS over UART), I need to signal a user-space daemon to open the TTY device, set the baud rate and install the ldisc - So I can make use of it.
>
> To notify that user-space daemon, I had planned to use /dev/rfkill.
> However, now with BT application also toggling the rfkill switch by writing to sysfs entry - is causing a bit of confusion to my user-space daemon.
>
> Although I now use hard/soft members of struct rfkill_event now to differentiate the 2 events (1 auto generated, another from BT app) - This patch would make it a bit more proper.
No. The proper way would be to either have your driver manage the UART
instead of userspace, or have your driver have its own userspace
interface. rfkill has nothing to do with it.
johannes
next prev parent reply other threads:[~2010-03-26 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100326065803.GD26602@core.coreip.homeip.net>
2010-03-26 16:13 ` Pavan Savoy
2010-03-26 17:12 ` Johannes Berg [this message]
2010-06-09 10:15 ` rfkill switch state during suspend? Pavan Savoy
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=1269623558.4342.0.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavan_savoy@yahoo.co.in \
/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
Powered by JetHome