Received: by 2002:a05:6a10:a841:0:0:0:0 with SMTP id d1csp3872738pxy; Mon, 26 Apr 2021 11:47:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwrNTQlLpEuOrNiFe6aMFivwmcwAbqXyBXsEczwFNEy9XXtVfyyCZZNvRnlHGn8NHe14rVO X-Received: by 2002:a50:ee0b:: with SMTP id g11mr116436eds.218.1619462841122; Mon, 26 Apr 2021 11:47:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1619462841; cv=none; d=google.com; s=arc-20160816; b=zxeH9ta64VDtecKVq1D1MkoQns3c7AWMpyKPhN3Vo/BgxC5s/zk9ihJ+xf5gg6agI0 fp11i4jxzUVMYEWgMG0IFhbz81g6fyi+8T5zCZhM4k/gZ7NlWEi8T2mtJ9C8QiXrfvf2 Sr/qU2Atympti185qTd4sfvd+NhlJXXPQ3zwa/7LcjL5Ql25WzGvZSTVIBWuNhAMZd3N 7+zt3k7XLow1vHrWGk0ubkjCO2e43CK1+bQAICCW+pgBU2f8Jr4j9ncZYIdkRD2/f4Lq PH3y0JmwHYHEuCnD8TX5P20AIKQEvcGUIv3BXH/RiRvKnsE19ttPIY0eTGzOH4JxszQz ljOw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=vpl+KXiHDK1EJ+33Ee24302pVNahtFcpm54ZwUGrx7A=; b=lNv8h1HLrRCgscluw8kKTkbr1akeSYVXw5Ie3RaUK8S3Qj8EifgjRTQrHlUQOyCYWu V3gEFKS+mhNuu2jZPZLQ2IIeY6dhJldzUMaGp+uBBWHmZ9mXF85PQuy8Pc9Q0tMs6bjD BEoIcXAkc2rZnsPUj/mSX7VaFogVAYDD4RRMyQ2uWjwnMPgklYcimYP3C3KKIQEjJ7Y6 JvaDEUEh4T45EsPVlFuQEl2DXgs5xt/5Ue5JlaoyUpxCTgsPu7OynkmJefTyjfp3uZL2 AuTZJmgxA9xfXi8bVMrYNJuBq4/YWNCXiwD09MzodoK46ZRuCXtbGwDx2Q0BRArEGgVi ZXXw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=DMwYROtg; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id nd1si13274492ejc.187.2021.04.26.11.46.56; Mon, 26 Apr 2021 11:47:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=DMwYROtg; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238608AbhDZSpt (ORCPT + 99 others); Mon, 26 Apr 2021 14:45:49 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:46666 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238542AbhDZSn7 (ORCPT ); Mon, 26 Apr 2021 14:43:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1619462595; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vpl+KXiHDK1EJ+33Ee24302pVNahtFcpm54ZwUGrx7A=; b=DMwYROtgLrNyWbyyP/6EvjyxTfgiG0AzsatNtZEywOqaBYeoY/oNIIW++ck8R4m1xSeF7b 4Zqh9erDg9LM4Sz4XhL4+BQLqAFOxBtE9iPH+m4t4xeLD88brJb4E5QyW1lt5CsCfrWaC4 GSrC+jq1f+nO4sbuBXzWYCsCJKN5irI= Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-184-f6xasQm8OiaecvKLglEQqQ-1; Mon, 26 Apr 2021 14:43:12 -0400 X-MC-Unique: f6xasQm8OiaecvKLglEQqQ-1 Received: by mail-ed1-f70.google.com with SMTP id bf25-20020a0564021a59b0290385169cebf8so16202955edb.8 for ; Mon, 26 Apr 2021 11:43:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=vpl+KXiHDK1EJ+33Ee24302pVNahtFcpm54ZwUGrx7A=; b=JvlkG8uOeslTTcmyr/ZtoYwOkKz9k3viQ6KiH9GNFL6u7P9WBLfIcf1YZPeaPZrmGO ZzxA2PF+l5o3Bjm5J9OH39dAL892g1ikNnZh96bwoKHKSek5QxaYojp4e24hKiRcThhG xc6qLlDoSsY1dSLAYUHOwBJIW28h13jPusLh6cK23kr7d2chd/ECysNMOoPGEUsNHkNG ME7XRVduwdm+ET8JO55IyEdyIqKOTy5ni4bN2Tf7rtN3sPow3bVED0JXVGKqi2+8EXBu /xI+6fCI5sT36ZYyMf6IrDom/5wt7vNilj2URSl97WW90D184wU1/uLwOcLSiD1zgRHV dMuw== X-Gm-Message-State: AOAM530H7Xucj6UkdOivVbop4v8FGuNwkG4xSTAdzugyMxt403y6dsZ4 0+FyJrKjtNecuo0wNTmm60IftY5Af0IiUjeHr81IeJsdKyC1vHp+Qqzwmy+EiUXS5uldis3V+W0 QCXRRjtq1jmHYoOcDkg6cBgwm6yE= X-Received: by 2002:a17:906:9342:: with SMTP id p2mr12932872ejw.311.1619462591218; Mon, 26 Apr 2021 11:43:11 -0700 (PDT) X-Received: by 2002:a17:906:9342:: with SMTP id p2mr12932866ejw.311.1619462591082; Mon, 26 Apr 2021 11:43:11 -0700 (PDT) Received: from x1.localdomain (2001-1c00-0c1e-bf00-1054-9d19-e0f0-8214.cable.dynamic.v6.ziggo.nl. [2001:1c00:c1e:bf00:1054:9d19:e0f0:8214]) by smtp.gmail.com with ESMTPSA id bu8sm485055edb.77.2021.04.26.11.43.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 26 Apr 2021 11:43:10 -0700 (PDT) Subject: Re: [PATCH 1/1] staging: rtl8723bs: Move wiphy setup to after reading the regulatory settings from the chip To: youling257 Cc: gregkh@linuxfoundation.org, johannes.berg@intel.com, linux-wireless@vger.kernel.org, ross.schm.dev@gmail.com References: <20210201152956.370186-2-hdegoede@redhat.com> <20210426183406.13055-1-youling257@gmail.com> From: Hans de Goede Message-ID: <6dd2cb8b-5540-a410-92d8-f329be98327b@redhat.com> Date: Mon, 26 Apr 2021 20:43:10 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 MIME-Version: 1.0 In-Reply-To: <20210426183406.13055-1-youling257@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Hi Youling, On 4/26/21 8:34 PM, youling257 wrote: > Hello, "cfg80211: Save the regulatory domain when setting custom > regulatory" "cfg80211: Save the regulatory domain with a lock" cause > rtl8723bs not work problem. > I see upstream rtl8723bs driver "staging: rtl8723bs: Move wiphy setup > to after reading the regulatory" "staging: rtl8723bs: fix wireless > regulatory API misuse" fix problem. > > I use rtl8723bs v5.2.17.1_26955.20180307_COEX20180201-6f52 driver, no > the "rtw_wdev_alloc(padapter, dvobj_to_dev(dvobj));" > > https://github.com/youling257/rockchip_wlan/blob/v5.2.17.1/rtl8723bs/os_dep/linux/ioctl_cfg80211.h#L234 > int rtw_wdev_alloc(_adapter *padapter, struct wiphy *wiphy); > > https://github.com/torvalds/linux/blob/master/drivers/staging/rtl8723bs/include/ioctl_cfg80211.h#L91 > int rtw_wdev_alloc(struct adapter *padapter, struct device *dev); > > https://github.com/torvalds/linux/blob/master/drivers/staging/rtl8723bs/os_dep/sdio_intf.c#L333 > https://github.com/youling257/rockchip_wlan/blob/v5.2.17.1/rtl8723bs/os_dep/linux/sdio_intf.c#L645 > > I want to fix rtl8723bs v5.2.17 not work problem, can you help me? I'm not sure what your problem exactly is. If your kernel contains the 51d62f2f2c50 ("cfg80211: Save the regulatory domain with a lock") Commit then you also need to backport (in the listed order): 81f153faacd0 ("staging: rtl8723bs: fix wireless regulatory API misuse") 50af06d43eab ("taging: rtl8723bs: Move wiphy setup to after reading the regulatory settings from the chip") Which you seem to have already figured out ? To keep the rtk8723bs driver working your kernel should either contain all 3 mentioned commits, or it should contain none of them. Regards, Hans