Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp882961rwb; Wed, 14 Dec 2022 04:10:29 -0800 (PST) X-Google-Smtp-Source: AA0mqf5hgyMcL4c7mBmsWg146oojZUkePRdFJSMFuw1rGI8HngBcV8hh6d3AwZSNsukGSu4VJj3V X-Received: by 2002:a05:6a21:328a:b0:9d:efbe:e5f6 with SMTP id yt10-20020a056a21328a00b0009defbee5f6mr36755839pzb.18.1671019828957; Wed, 14 Dec 2022 04:10:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671019828; cv=none; d=google.com; s=arc-20160816; b=BYBdUX2vpBBCceKnLabCFb5wM4A4zzO2lwvnuk1qfHjJr7L7MKyTFselmF3kWOLtDN SXtrz76/JlYhAcv7k8hK6htEW2Ez0jQavTXDX5vD2a+8VezGGiqbKdKYJk/TjAfj2Gaz mixk9fDkGsEqEJvXxCojqiDb54T4J+PReQYK7jOI0Tm4IVlz8Wy24H4GE6WqRmUz0ken O37/dwLdlegUZKLAhH6Vs54ShWoFxnPqRKCPVqeU04psGSzuxPq6nbD4atmcm9k+TQKe ZA+7bZuCXQqJbZ8onDO06V4jFGVFLQG+M2cPvy2M4dFUhZwJl5xwuELGTcPz6t4GCDFY VmsA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=peaw+2jBoexT/V/OL/klaMSfRkpK0w1QubB8hlHtjKU=; b=M+KuNomXrnQQ4w/jR99orizaY785sq4mENdCm4gZD+HZh2aNIBgllWj2bStRRBYG5N r3bGvbWi+corZU8RzNKLL3YYq3U4gMPTI5D1MEAmU2FMgr5tDN6O7y9qNcbD9uJ8/CpS h9ORmN3fOHeWEjeqyUggR86HJOxRWfDleKSP8ID9HLELbuYhinpaeRFfBRqc3NAOYjDX vxQl8f6p40GY7HQHkxsUnqh8fP1yma8J8n0BUOrXQpdVLpQI2Qn5zHIg0KYmDVtvlQ31 zbnMuiDmwOc2p9jwLaULrBUptm5/tp8OQvvJ4sclrHy4aqmhiA/twY2h1k595LWWh4uU qnRA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sartura.hr header.s=sartura header.b=IffZpvmo; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=NONE dis=NONE) header.from=sartura.hr Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id mq11-20020a17090b380b00b001f31f339134si1985128pjb.152.2022.12.14.04.10.20; Wed, 14 Dec 2022 04:10:28 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sartura.hr header.s=sartura header.b=IffZpvmo; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=NONE dis=NONE) header.from=sartura.hr Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238200AbiLNMEx (ORCPT + 66 others); Wed, 14 Dec 2022 07:04:53 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38214 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238406AbiLNME1 (ORCPT ); Wed, 14 Dec 2022 07:04:27 -0500 Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A109427CF6 for ; Wed, 14 Dec 2022 04:02:54 -0800 (PST) Received: by mail-pf1-x432.google.com with SMTP id a14so4290048pfa.1 for ; Wed, 14 Dec 2022 04:02:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sartura.hr; s=sartura; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=peaw+2jBoexT/V/OL/klaMSfRkpK0w1QubB8hlHtjKU=; b=IffZpvmos6IFA8F2Mu7UX03vFoZdzSvAl4wArexI2TJ+mCg8LYPObJ0caqqBk6KELc 7e96IX0TGhm3EbfxrnJUHspRY4C5kzZjXA8RPZhE2bOdCe6tjVnt+Z3CF0kf/nY0nL+5 zhLxH/gVF/oPszrMxuCbjkfNqT6s3OZYE50HYnrLZ7oMjvbFnJ2FU0kVIkcZhH46wiwl wLPAdUYt+VKJPhUoSBgt566qcUxTJYhAUxZrXrKHxPKFY8264tYoNHL+XtQdD6DjNdwK dtgAPPBovln+d78d738YPXAKKoU4rCSJQNQzmoESEN0DTVhkyEgeq7ajtPDj3m1qgn+h UaHw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=peaw+2jBoexT/V/OL/klaMSfRkpK0w1QubB8hlHtjKU=; b=RoqbBwAQNX+VSgn950QmhtOOZv1P23tKoVOGsKUDUKlvLzy1UACUaDKqsEY42qpvl7 wW+4Cp4pMEw7NOMJKb3OFeWzeuioL/erKx9cXD+CZp+5CpEbt91m2eE75uxOjmuMICL+ Pwag70jZj88r1xx8EWWk9coN7K6GK/vFUUkjzqMWT9db/voG9Wt3Pi5+uZSOxjZqumPU FjVJ0mmEHfoS1DO2Tl3eRJLtwfhErbdKz2ia7Qbg+3pPkq+9qShCc44bM/fdNWGX6Bcm Ug+6EsqmN9RoPhqxk+gxA83WPn8y3gM9HphbiB7U/ds6oFp5bq9nsfpp97h+8AZwwJbo Tnlw== X-Gm-Message-State: ANoB5plqDdUd8PfVXbB7MlHjNlNZcuy7falqMWNVXI0u9K78ydv/jlw2 GBbp1onYfi2K9swxDWtVgUPJDeCpMnSAg+2kIMHb8A== X-Received: by 2002:a62:8409:0:b0:575:1168:a970 with SMTP id k9-20020a628409000000b005751168a970mr54638196pfd.54.1671019373770; Wed, 14 Dec 2022 04:02:53 -0800 (PST) MIME-Version: 1.0 References: <20221105194943.826847-1-robimarko@gmail.com> <20221105194943.826847-2-robimarko@gmail.com> <20221107174727.GA7535@thinkpad> <87cz9xcqbd.fsf@kernel.org> <877czn8c2n.fsf@kernel.org> In-Reply-To: <877czn8c2n.fsf@kernel.org> From: Robert Marko Date: Wed, 14 Dec 2022 13:02:42 +0100 Message-ID: Subject: Re: [PATCH 2/2] wifi: ath11k: use unique QRTR instance ID To: Kalle Valo Cc: Manivannan Sadhasivam , Robert Marko , davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, gregkh@linuxfoundation.org, elder@linaro.org, hemantk@codeaurora.org, quic_jhugo@quicinc.com, quic_qianyu@quicinc.com, bbhatt@codeaurora.org, mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org, ath11k@lists.infradead.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, ansuelsmth@gmail.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Tue, Nov 22, 2022 at 12:26 PM Kalle Valo wrote: > > Kalle Valo writes: > > > Manivannan Sadhasivam writes: > > > >> On Sat, Nov 05, 2022 at 08:49:43PM +0100, Robert Marko wrote: > >>> Currently, trying to use AHB + PCI/MHI cards or multiple PCI/MHI cards > >>> will cause a clash in the QRTR instance node ID and prevent the driver > >>> from talking via QMI to the card and thus initializing it with: > >>> [ 9.836329] ath11k c000000.wifi: host capability request failed: 1 90 > >>> [ 9.842047] ath11k c000000.wifi: failed to send qmi host cap: -22 > >>> > >> > >> There is still an outstanding issue where you cannot connect two WLAN modules > >> with same node id. > >> > >>> So, in order to allow for this combination of cards, especially AHB + PCI > >>> cards like IPQ8074 + QCN9074 (Used by me and tested on) set the desired > >>> QRTR instance ID offset by calculating a unique one based on PCI domain > >>> and bus ID-s and writing it to bits 7-0 of BHI_ERRDBG2 MHI register by > >>> using the SBL state callback that is added as part of the series. > >>> We also have to make sure that new QRTR offset is added on top of the > >>> default QRTR instance ID-s that are currently used in the driver. > >>> > >> > >> Register BHI_ERRDBG2 is listed as Read only from Host as per the BHI spec. > >> So I'm not sure if this solution is going to work on all ath11k supported > >> chipsets. > >> > >> Kalle, can you confirm? > > > > I can't look at this in detail right now, but hopefully in few days. > > I'll get back to you. > > The solution we have been thinking internally would not use > MHI_CB_EE_SBL_MODE at all, it's not clear for me yet why the mode was > not needed in our solution. Maybe there are firmware modifications? I > think it's best that we submit our proposal as well, then we can then > compare implementations and see what is the best course of action. Kalle, any ETA when you will post your idea? I am constantly hitting this crazy limitation and my idea does not work on cards like QCA6390 so it's not a viable workaround at all. Regards, Robert > > But it looks that not all ath11k hardware and firmware releases support > this feature, we would need meta data information from the firmware to > detect it. I am working on adding firmware meta data support[1] to > ath11k, will post patches for that "soon". > > [1] similar to firmware-N.bin support ath10k has > > -- > https://patchwork.kernel.org/project/linux-wireless/list/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches > > -- > ath11k mailing list > ath11k@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/ath11k -- Robert Marko Staff Embedded Linux Engineer Sartura Ltd. Lendavska ulica 16a 10000 Zagreb, Croatia Email: robert.marko@sartura.hr Web: www.sartura.hr