Hi Gustavo, > > > It is important that the monitor interface gets notified about > > > a new device before its power on procedure has been started. > > > > > > For some reason that is no longer working as expected and the power > > > on procedure runs first. It is safe to just notify about device > > > registration and trigger the power on procedure afterwards. > > > > > > Signed-off-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> > > > --- > > > net/bluetooth/hci_core.c | 4 ++-- > > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > Patch has been applied to bluetooth-next. Thanks. > > I guess you mean bluetooth.git? (that's where the patch is right now - > not bluetooth-next). Also, I don't think the Cc: stable addition was > necessary since this scheduling behavior seems to be something only > introduced for 3.7 (not 100% sure about this though). I did not send this to stable, because I think it is 3.7-rc only behavior. Feel free to test it. With the help of btmon it is really easy to see if the New Index event arrives before the first HCI command or not. Remember that this only applies for newly attached devices and btmon already running. Regards Marcel -- 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
