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=-5.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham 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 AB0A8C76188 for ; Tue, 23 Jul 2019 05:11:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 8669D2238C for ; Tue, 23 Jul 2019 05:11:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726546AbfGWFL5 (ORCPT ); Tue, 23 Jul 2019 01:11:57 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:47000 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725907AbfGWFL5 (ORCPT ); Tue, 23 Jul 2019 01:11:57 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hpn5e-0006Pe-23; Tue, 23 Jul 2019 07:11:54 +0200 Message-ID: Subject: Re: TI wlcore wifi not loading w/ v5.3-rc1 From: Johannes Berg To: John Stultz , Kalle Valo , Tony Lindgren Cc: "linux-wireless@vger.kernel.org" Date: Tue, 23 Jul 2019 07:11:53 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Mon, 2019-07-22 at 22:20 +0000, John Stultz wrote: > Hey folks, > > Testing on my HiKey960, I'm seeing: > [ 8.894909] wlcore: wl18xx HW: 183x or 180x, PG 2.2 (ROM 0x11) > [ 8.902017] ------------[ cut here ]------------ > [ 8.906832] WARNING: CPU: 0 PID: 5 at net/wireless/core.c:868 > wiphy_register+0x8b4/0xc08 [...] > It seems like from the commit message, the wlcore driver isn't > providing the policy values the network core expects? I'm not sure > what the right fix would be, but wanted to raise the issue. There's a fix on the way, unfortunately I forgot to send the pull request before the merge window. I sent it out a couple of days ago and narrowly missed -rc1, but it'll be in rc2: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=91046d6364afde646734c7ead1f649d253c386e9 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1667e4f9bcfb6785362a300ac4486df0854a72aa johannes