From: Kalle Valo <kvalo@codeaurora.org>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Arend van Spriel <arend@broadcom.com>,
Ivaylo Dimitrov <ivo.g.dimitrov.75@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
David Gnedt <david.gnedt@davizone.at>
Subject: Re: [PATCH v2] wl1251: add sysfs interface for bluetooth coexistence mode configuration
Date: Fri, 22 Jan 2016 13:55:44 +0200 [thread overview]
Message-ID: <87wpr1x1z3.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20160122092935.GL7192@pali> ("Pali Rohár"'s message of "Fri, 22 Jan 2016 10:29:35 +0100")
Pali Rohár <pali.rohar@gmail.com> writes:
>> >> > Right, bt-coex is not for debugging purpose, but for normal usage, when
>> >> > user want to use together bluetooth and wifi or just one of those.
>> >>
>> >> I think most of other drivers have a debugfs interface for btcoex, I
>> >> guess mostly for testing purposes. But this really should be added to
>> >> cfg80211.
>> >
>> > All other TI wireless drivers have "bt_coex_state" sysfs node.
>>
>> Then that's a mistake, they shouldn't have that.
>
> But it is there, wl1251 is also TI wireless driver and for last two
> years there is no interface to deal with this problem...
>
> So as other drivers do, I'm proposing solution which fix bt coex also
> for wl1251 driver need on Nokia N900.
Even if the wlcore sysfs interface fell through the cracks it's no
excuse to add more private interfaces to wireless drivers. We have
cfg80211 and all generic interfaces, like btcoex control, should go
through that subsystem. That way all drivers can share a common
interface and everyone are happy.
What I suggest is that you add this yourself to cfg80211 and mac80211.
It's not that hard and I think you could use NL80211_CMD_SET_POWER_SAVE
as an example.
--
Kalle Valo
next prev parent reply other threads:[~2016-01-22 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-26 11:45 [PATCH v2] wl1251: add sysfs interface for bluetooth coexistence mode configuration Pali Rohár
2016-01-09 20:33 ` Pali Rohár
2016-01-13 12:16 ` Pali Rohár
2016-01-13 12:57 ` Kalle Valo
2016-01-13 14:40 ` Pali Rohár
2016-01-13 22:32 ` Arend van Spriel
2016-01-13 22:39 ` Pali Rohár
2016-01-14 9:16 ` Pavel Machek
2016-01-21 8:53 ` Pali Rohár
2016-01-21 13:48 ` Kalle Valo
2016-01-21 13:51 ` Pali Rohár
2016-01-21 14:44 ` Kalle Valo
2016-01-22 9:29 ` Pali Rohár
2016-01-22 11:55 ` Kalle Valo [this message]
2016-01-21 13:44 ` Kalle Valo
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=87wpr1x1z3.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=arend@broadcom.com \
--cc=david.gnedt@davizone.at \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.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