Hi Marcel,
On Thu, Apr 19, 2012, Marcel Holtmann wrote:
> > > >> --- a/src/rfkill.c
> > > >> +++ b/src/rfkill.c
> > > >> @@ -128,11 +128,18 @@ static gboolean rfkill_event(GIOChannel *chan,
> > > >> if (id < 0)
> > > >> return TRUE;
> > > >>
> > > >> + DBG("RFKILL unblock for hci%d", id);
> > > >> +
> > > >> adapter = manager_find_adapter_by_id(id);
> > > >> - if (!adapter)
> > > >> + if (!adapter) {
> > > >> + /*
> > > >> + * If device is rfkilled, the initialize operation
> > > >> + * may failed and adapter is not created, then we
> > > >> + * need to set the device powered directly.
> > > >> + */
> > > >> + adapter_ops_set_powered(id, TRUE);
> > > >> return TRUE;
> > > >> -
> > > >> - DBG("RFKILL unblock for hci%d", id);
> > > >> + }
> > > >>
> > > >> btd_adapter_restore_powered(adapter);
> > > >
> > > >This looks more like a workaround to another issue: if the kernel is
> > > >aware of the adapter but user space isn't it means that something has
> > > >gone wrong during the initialization process and *that* should be
> > > >fixed instead of blindly attempting to power on the adapter id
> > > >anyway.
> > >
> > > Kernel works well and can detect the adapter, Bluetooth initialize failed
> > > due to when we init HCI device, we try to start the device, however the
> > > device is hardware/software rfkilled. From the code, we only init the
> > > adapter when the device is up, this result in the current code in rfkill.c
> > > can't bring up the device because adapter is NULL. Also only the kernel
> > > detected the device we can get the rfkill event, the code in rfkill.c also
> > > checked the device, then it is safe to power on the device in rfkill.c
> >
> > Ok, now I understand the issue better. Unfortunately your approach wont
> > work with the management interface since the HCI index is invalid until
> > the kernel has been able to send the first basic HCI commands. The
> > expectation there is also that the first mgmt command to be sent for a
> > new index is read_info.
> >
> > I had a brief chat with Marcel and one potential solution would be to
> > have a kernel side timer for rfkilled devices to let the basic HCI
> > commands be sent before bringing the adapter down. This would allow user
> > space to have a properly initialized adapter object and your patches
> > wouldn't be needed.
>
> I actually meant to have the pending RFKILL events to be handled in
> userspace.
>
> But sure for the RFKILL switches that are tight to a Bluetooth
> controller and are part of hci_dev, we could be even smarter inside the
> kernel.
I assumed you meant kernel side since that's where the rfkill enabling
is handled right now (user space only takes action for unrfkilling
adapters). I.e. I'd add some extra logic to hci_rfkill_set_block
(hci_core.c) to check if the adapter has been fully initialized and if
not set a timer instead of directly calling hci_dev_do_close. And if
hci_rfkill_set_block gets called again with blocked == 0 then the timer
would be removed.
Johan
--
To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
