lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 23 Sep 2021 22:41:30 +0300
From:   Andy Shevchenko <>
To:     Jonas Dreßler <>
Cc:     Brian Norris <>,
        Amitkumar Karwar <>,
        Ganapathi Bhat <>,
        Xinming Hu <>,
        Kalle Valo <>,
        "David S. Miller" <>,
        Jakub Kicinski <>,
        Tsuchiya Yuto <>,
        linux-wireless <>,,
        Linux Kernel <>,
        linux-pci <>,
        Maximilian Luz <>,
        Andy Shevchenko <>,
        Bjorn Helgaas <>,
        Pali Rohár <>
Subject: Re: [PATCH 1/2] mwifiex: Use non-posted PCI register writes

On Thu, Sep 23, 2021 at 6:28 PM Jonas Dreßler <> wrote:
> On 9/22/21 2:50 PM, Jonas Dreßler wrote:


> - Just calling mwifiex_write_reg() once and then blocking until the card
> wakes up using my delay-loop doesn't fix the issue, it's actually
> writing multiple times that fixes the issue
> These observations sound a lot like writes (and even reads) are actually
> being dropped, don't they?

It sounds like you're writing into a not ready (fully powered on) device.

To check this, try to put a busy loop for reading and check the value
till it gets 0.

Something like

  unsigned int count = 1000;

  do {
    if (mwifiex_read_reg(...) == 0)
  } while (--count);

With Best Regards,
Andy Shevchenko

Powered by blists - more mailing lists