From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6A56C433DF for ; Wed, 20 May 2020 13:01:55 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6A844207D4 for ; Wed, 20 May 2020 13:01:55 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="Kn2sSWpp" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726548AbgETNBy (ORCPT ); Wed, 20 May 2020 09:01:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42556 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726435AbgETNBy (ORCPT ); Wed, 20 May 2020 09:01:54 -0400 Received: from mail-vs1-xe44.google.com (mail-vs1-xe44.google.com [IPv6:2607:f8b0:4864:20::e44]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 46269C061A0E for ; Wed, 20 May 2020 06:01:54 -0700 (PDT) Received: by mail-vs1-xe44.google.com with SMTP id v26so1769752vsa.1 for ; Wed, 20 May 2020 06:01:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=woAnCIhfYEJLipFe8EyZcfmluPA2MaZuO37zxR3vgb4=; b=Kn2sSWppvhHVjhct9KDLJTMw91TD7ZhUf0aMA3bkc7nFiCuylrwPze0UQIIik4DdOJ N8ygw4qG37hZ4LHNY8si5tGH3HklqEHflv2DJvrRkKRCdtpNUzBOwiHIIC825z3XC27w 7xtWGQ+V/TuL/PwTDEN/VYctGxhSFhPcvqHBqAU4cmdRTFHBU9sBFQjDz0+6yPs0WqFT PP30AWltwUF1x6fa41Om76QWWKdFgIkXZkLwHczf2i9haOcLXssXGQ6kQQa1ImVx05kB wpBaCZOoqNg+rV/uxU6KgDv7gS8RRNmiyFtGsBDzK3C8iOiVnjAAqkUYPoESt2ueMqBK ANfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=woAnCIhfYEJLipFe8EyZcfmluPA2MaZuO37zxR3vgb4=; b=WXstQqiBPMxH5hfxO1rkBvyu6hD5k+A7MvAb5vWXy3gLJdO1PBQDUFDL9Vsc1PEdYl Zy+50yDDKEQkXtShrxBvxUg3JvDib0A7IHRhvpBMoylaTp2UiU4RCoxCVSugxl8FX427 rQfaucTVgpoQqH1yPwld6W11WsdTlkP932CoCGkkRUdEqMXI5ScTk+R7mhjfbJX8DqXY 5v8d4FDVGtlk0aRCJ2sP7PmsKTzVihAKQJRUiumfXpNuv4VW3YZKp4hmPVf9XzCKb7TR z/qYa2M85zAht5kAtacr5DZjqc60n0QpN3L/qxNjHTayT5lZGR1om82Mx9TW66T7Tv6a zw5g== X-Gm-Message-State: AOAM530Wv44V10gN/EgoT0L8i2M1bcPfW/qCHvnX0X5l/HU4jelUr2Ez ugmYB2WERC9ZaagSRQbfkjX/3tKuiDBqb+WalCw= X-Google-Smtp-Source: ABdhPJzM3ZY8vwut7M1/Mc1Vzn+Fk4KTxo0f0WuLZt4UD6+dKcBpOhqFbJjxWDWosv1dzsuk/FboXI+w3tieJ8IjTSg= X-Received: by 2002:a67:684a:: with SMTP id d71mr2937165vsc.176.1589979711982; Wed, 20 May 2020 06:01:51 -0700 (PDT) MIME-Version: 1.0 References: <9122588d-683a-936e-1305-c34124e6702c@nextfour.com> In-Reply-To: From: Emmanuel Grumbach Date: Wed, 20 May 2020 16:01:43 +0300 Message-ID: Subject: Re: iwlwifi firmware loading problems, rk3399 To: =?UTF-8?Q?Mika_Penttil=C3=A4?= Cc: Johannes Berg , Emmanuel Grumbach , linux-wireless , linux-rockchip@lists.infradead.org Content-Type: text/plain; charset="UTF-8" Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org > > I guess you need to debug your board :) > > The interrupt is not coming, then.. there isn't much the driver can do. > > Well it does get interrupts, but stops getting them during fw loading at > some point which causes it to fail. I have seen similar posts while > googling and they are happening on x86/ubuntu and popular platforms. So > I'm afraid it is something with iwlwifi or its usage of MSIX or such. > The kernel version is 5.4. You can try to disable msix. In iwl_pcie_set_interrupt_capa, just goto enable_msi. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Emmanuel Grumbach Subject: Re: iwlwifi firmware loading problems, rk3399 Date: Wed, 20 May 2020 16:01:43 +0300 Message-ID: References: <9122588d-683a-936e-1305-c34124e6702c@nextfour.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: linux-wireless-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: =?UTF-8?Q?Mika_Penttil=C3=A4?= Cc: Johannes Berg , Emmanuel Grumbach , linux-wireless , linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-rockchip.vger.kernel.org > > I guess you need to debug your board :) > > The interrupt is not coming, then.. there isn't much the driver can do. > > Well it does get interrupts, but stops getting them during fw loading at > some point which causes it to fail. I have seen similar posts while > googling and they are happening on x86/ubuntu and popular platforms. So > I'm afraid it is something with iwlwifi or its usage of MSIX or such. > The kernel version is 5.4. You can try to disable msix. In iwl_pcie_set_interrupt_capa, just goto enable_msi.