linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Tony Lindgren <tony@atomide.com>
Cc: Sebastian Reichel <sre@kernel.org>,
	"Arthur D." <spinal.by@gmail.com>,
	Bluez mailing list <linux-bluetooth@vger.kernel.org>,
	linux-omap@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: Droid 4 WiFi firmware loading error
Date: Fri, 14 Feb 2020 19:23:12 +0100	[thread overview]
Message-ID: <3D50CC42-1201-4067-ACDE-E9B9F0DC5653@holtmann.org> (raw)
In-Reply-To: <20200214174548.GC64767@atomide.com>

Hi Tony,

>> WTF :(
>> 
>> Right now the BT driver and the WiFi driver are no aware of
>> each other. Actually the kernel is not even aware, that both
>> drivers are using the same chip. Unfortunately this will be
>> tricky to solve properly. Since a system may have two WiLink
>> devices, the only solution coming to my mind would be adding
>> a link from the BT device to the WiFi device in device tree.
>> Additionally we would need something in the WiLink driver to
>> check if driver has been initialized properly for a given DT
>> node.
> 
> Yeah exactly.. I think the best way would be to export something
> like wlcore_register_bt/wlcore_unregister_bt.. And then have
> wlcore_register_bt return -EAGAIN until wlcore is up.

actually NO.

We have rejected this many times for all hardware manufacturers. Please fix the firmware instead.

Regards

Marcel


  reply	other threads:[~2020-02-14 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <op.0fudjzcyhxa7s4@supervisor.net28>
     [not found] ` <20200211214705.GD16391@atomide.com>
     [not found]   ` <op.0fuie5cdhxa7s4@supervisor.net28>
     [not found]     ` <20200211232425.GE16391@atomide.com>
     [not found]       ` <op.0fu85owhhxa7s4@supervisor.net28>
     [not found]         ` <20200212150722.GF16391@atomide.com>
     [not found]           ` <20200212162131.GI16391@atomide.com>
     [not found]             ` <op.0fwkyxvihxa7s4@supervisor.net28>
     [not found]               ` <20200213041112.GL16391@atomide.com>
     [not found]                 ` <op.0fw0oas5hxa7s4@supervisor.net28>
     [not found]                   ` <20200213161157.GN16391@atomide.com>
2020-02-13 21:54                     ` Droid 4 WiFi firmware loading error Arthur D.
2020-02-14 16:11                       ` Sebastian Reichel
2020-02-14 17:45                         ` Tony Lindgren
2020-02-14 18:23                           ` Marcel Holtmann [this message]
2020-02-18 15:38                             ` Merlijn Wajer

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=3D50CC42-1201-4067-ACDE-E9B9F0DC5653@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=spinal.by@gmail.com \
    --cc=sre@kernel.org \
    --cc=tony@atomide.com \
    /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;
as well as URLs for NNTP newsgroup(s).