ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Herbert <mark.herbert42@gmail.com>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: Can not unload ath11k_pci and load it back
Date: Thu, 7 Oct 2021 11:00:42 +0300	[thread overview]
Message-ID: <c2699c64-44d0-1857-e3b1-21e02e401b86@gmail.com> (raw)
In-Reply-To: <87y275cm2x.fsf@codeaurora.org>

As I mentioned - if I build mhi as a module - card will not even start. 
it works only if mhi is compiled inside the kernel, and in this config I 
can not unload it.

On 07.10.2021 10:48, Kalle Valo wrote:
> Mark Herbert <mark.herbert42@gmail.com> writes:
>
>> I've found similar bug files already - so not to create duplicates
>> simply commented there
>>
>> https://bugzilla.kernel.org/show_bug.cgi?id=214541
>>
>> Exactly - hibernation means saving state on disk and resuming later,
>> it is a very usefull feature when you are running out of battery and
>> want to save your work.
> Got it, thanks. So it seems we have two issues here: ath11k does not
> support hibernation and ath11k module reload failing. Let's handle the
> module reload failing in bug #214541, but can you file another bug about
> the missing support for hibernation? Let's have one issue per bug
> report, it's easier to manage bugzilla that way.
>
>> Also one more point I've found - if MHI is configured in the kernel -
>> the card is starting up on thr first boot and works. But if i
>> configure MHI as a module - it does not. MHI module do load. So do
>> ath11k and ath11k_pci.  But the last ath11k dmesg says :
>>
>> mhi mhi0: Wait for device to enter SBL or Mission mode
>>
>> Exactly as if I  do rmmod/modprobe sequence.
>>
>> I use latest BIOS from Dell (in fact upgrading 3.0.4 to 3.1.0 did not
>> cange anythng) ,  and have tried multiple kernels. Stable 5.14 series
>> and ath11k git tree (next and master-pending). Nothing helps.
>> Sometimes it woks out - I had couple of times successfully
>> rmmod/modprobe ath11k_pci but it s a kind of random and very rare
>> event ( I had it 2 times only).
>>
>> So for me it looks like an issue between MHI and ath11k , but
>> ubfortunately my knowledge is not enough to propose any solution here.
> On my NUC x86 test box I reload ath11k modules several times a day while
> I test ath11k but I always reload the mhi modules at the same time,
> maybe that makes the difference? Or XPS 13 9310 works differently from
> NUC, that's also possible.
>

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2021-10-07  8:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-05 19:32 Can not unload ath11k_pci and load it back Mark Herbert
2021-10-07  6:22 ` Kalle Valo
2021-10-07  7:31   ` Mark Herbert
2021-10-07  7:48     ` Kalle Valo
2021-10-07  8:00       ` Mark Herbert [this message]
2021-10-07  8:51       ` Mark Herbert
2021-10-08 13:28       ` Mark Herbert
2021-10-24  5:22       ` Mark Herbert
2021-10-30 19:23       ` Mark Herbert
2021-10-07  7:35   ` Mark Herbert
  -- strict thread matches above, loose matches on Subject: below --
2021-10-31  7:43 Mark Herbert

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=c2699c64-44d0-1857-e3b1-21e02e401b86@gmail.com \
    --to=mark.herbert42@gmail.com \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@codeaurora.org \
    /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