Return-Path: Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: btcoex subsystem From: Marcel Holtmann In-Reply-To: <874mr3xjnx.fsf_-_@kamboji.qca.qualcomm.com> Date: Thu, 12 Feb 2015 12:28:46 -0800 Cc: Larry Finger , linux-wireless , Troy Tan , netdev@vger.kernel.org, linux-bluetooth@vger.kernel.org Message-Id: References: <1422304934-9239-1-git-send-email-Larry.Finger@lwfinger.net> <1422304934-9239-6-git-send-email-Larry.Finger@lwfinger.net> <87h9v8zkuh.fsf@kamboji.qca.qualcomm.com> <54CBA0CE.8030800@lwfinger.net> <874mr3xjnx.fsf_-_@kamboji.qca.qualcomm.com> To: Kalle Valo Sender: netdev-owner@vger.kernel.org List-ID: Hi Kalle, >>> I will work on combining the latest BT drivers from Realtek with >>> btusb to see if I can achieve a patch that will both work with the >>> Realtek hardware, and get approval from the reviewers. >>> >>> What would be an approved method of communicating between two kernel >>> modules? Is there some example in the kernel that I could study? >> >> We need a btcoex subsystem that both WiFi and Bluetooth can register >> to and communicate with. > > The need for this seems to periodically come up, I remember needing > something like that back in the Maemo wl1251 days and also ath6kl needed > this. Are there any ideas for this subsystem? How would this btcoex > subsystem work? What kind of information would it provide? > > Is this something we should discuss at Ottawa? sadly something came up and I am not making it to Ottawa. However we should be talking about this at some point since Bluetooth has MWS for its coexistence which could be a good starting point. Something we have to look into for the Bluetooth subsystem at some point. Regards Marcel