Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2201945pxb; Thu, 3 Feb 2022 01:20:02 -0800 (PST) X-Google-Smtp-Source: ABdhPJwF0mmTcBml6Ujk5oQCmA4udMCB+wbALXcyONpimC1hcEKefmdQz8zZimxsl8d5MiJCkK7U X-Received: by 2002:a17:902:7ec8:: with SMTP id p8mr34365261plb.165.1643880001879; Thu, 03 Feb 2022 01:20:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643880001; cv=none; d=google.com; s=arc-20160816; b=hEV22wDDKPZNJSDdvg1COIVYD1/9fMg22C4XP9v0oKNrKLx7Sk8sgJ/7G39xm3qPhm +Vn9gZYYEKum7r7OnRAT5Lkq8uSu/P2zbqG7mMn3OGMCYeVkLvtcV9slO+wHyky5PgD3 tL5nRGUdngCNgL5XkiUsSlxS+WaiPa16q/6sHUw4KXsBTv0MJGhpONPFfLRqtYZq673u mz8BvtlDmMBjoqpDOV9RK0cS0T5AbrFvmh9pOYomo72AtUlvNfhx9D6++ReMkoRYUVTp HfkgAwYsR3NIgA0Lixj4WGPx61Ort0DV/nBGXlsMRp9Mswk4TfcITNHvYsfQ2oqpUcKE rQLQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=VTOPnaRquWicISMRZD83cjOQfdkXCxYB8Ac7cHDsTWs=; b=O4TO5r13l1j2tTF/x+QHb91u0Zmu1jrz+hlpClDW7NdVgiq+RdR4UOIzfSK+3HG12C BN+sM6Mgq3vKce1EFFgCQfy5FgjkL1Oa0DEQhsBNHKM92VUpHWDllZ04st0/Enb6s0Qi FFu7rnukAqe+StsnPrYf1b3B6qm/mDK3OTykKOaEO5YKJCVyJjBWglVmLTv+P8pYRt0f 5tdzX0SSPGUbtyKjTITHU/9eS2xnmCC4dgZ5OQrgNf2Q4S8IisqPwqCuMAUZqsm8svnE ZZtELUw7YLxdBGH3O5YFUETJ2gDYeKL387bGCtl/CGJ0MO2McTR1BFf3I+XBIWcg+WAD LW+g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=HOGlJ2+2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k15si25978927pga.245.2022.02.03.01.19.50; Thu, 03 Feb 2022 01:20:01 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-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=@gmail.com header.s=20210112 header.b=HOGlJ2+2; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346769AbiBBSt4 (ORCPT + 99 others); Wed, 2 Feb 2022 13:49:56 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46144 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346631AbiBBStz (ORCPT ); Wed, 2 Feb 2022 13:49:55 -0500 Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 53FF3C061714; Wed, 2 Feb 2022 10:49:55 -0800 (PST) Received: by mail-qt1-x834.google.com with SMTP id y8so66086qtn.8; Wed, 02 Feb 2022 10:49:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=VTOPnaRquWicISMRZD83cjOQfdkXCxYB8Ac7cHDsTWs=; b=HOGlJ2+27xL5/WqxZJdwbp7tuNHB36A0n0ah5gbe2JaqwLe6kVXWNbHx47yMO+j51x fPTa6ZTGRy8Dzk9PLpGA5X3sDbNQXspYP6nSzZqzzwtDSnZcwM9QXQQz3Ai6SwHowsdH mzplefphGpL2xJGlKs6rUevuGCVHhqLiEIfyuk4LQJ4kOPRAAuatau+gN4AYIK0kZ0l0 HcpT2KMNmVvC+E39EiBvqtDTtq8xzKS74fTjw8B9MfN6+za7P4s8Vli16oJlQ628izLi juEG/Ot8g6dvQRKzO+8DCSD4CEgMJZuWhCvqIOF7AIojYxpI7IRHl8J6+iaCvWi7+H5a eJ7Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=VTOPnaRquWicISMRZD83cjOQfdkXCxYB8Ac7cHDsTWs=; b=s484Ftw6yHX9+ngYzS64rijkPmaCzTMTAeykvzCdHG7BMTbD2Ib711powpRg92SqEP REUTWVKruAR8cTQ8RVNMlbR9M2JF6OHGWEsWGX+3iDqpV6u+qQD0bcoylMRirZqQCd7i vgicVUNW5UxLb2mxh7ltrgRquaCswMxbRt4SIwNLNBuqidr6wKxaOigbskx6AnGH3RkQ YTl2Pn0a75YuV2YsJRnWxrwSn4TcIFhWYA9cWlh8sDDY+ODVTMDjzypSIV4agvMX1WHO SMo/KcXN8N3IGKxLZoDNLP0AD1Hlf132KVJKflS467QEmd2HUXR+aZID29cLOSMlATl7 EJIw== X-Gm-Message-State: AOAM5323VMxWksBNVfkGtZN2eGFSieQDwX8pXxOn9Aaw3nNSwSmiyOMF CCqqam16y5pczZsv2VbBKsFatsow6GC3AeilXQ8= X-Received: by 2002:ac8:5c49:: with SMTP id j9mr18334765qtj.297.1643827794431; Wed, 02 Feb 2022 10:49:54 -0800 (PST) MIME-Version: 1.0 References: <20211009221711.2315352-1-robimarko@gmail.com> <163890036783.24891.8718291787865192280.kvalo@kernel.org> <09a27912-9ea4-fe75-df72-41ba0fa5fd4e@gmail.com> In-Reply-To: From: Robert Marko Date: Wed, 2 Feb 2022 19:49:43 +0100 Message-ID: Subject: Re: [PATCH] ath10k: support bus and device specific API 1 BDF selection To: Thibaut Cc: Christian Lamparter , Kalle Valo , kvalo@codeaurora.org, davem@davemloft.net, kuba@kernel.org, ath10k@lists.infradead.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, open list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kalle, What is your opinion on this? I would really love to see this get merged as we are having more and more devices that are impacted without it. Regards, Robert On Fri, 17 Dec 2021 at 13:25, Thibaut wrote: > > > > > Le 17 d=C3=A9c. 2021 =C3=A0 13:06, Robert Marko a= =C3=A9crit : > > > > On Wed, 8 Dec 2021 at 15:07, Christian Lamparter w= rote: > >> > >> Isn't the only user of this the non-upstreamable rb_hardconfig > >> mikrotik platform driver? > > The driver could be upstreamed if desirable. > Yet I think it=E2=80=99s quite orthogonal to having the possibility to dy= namically load a different BDF via API 1 for each available radio, which be= fore this patch couldn=E2=80=99t be done and is necessary for this particul= ar hardware. > > >> So, in your case the devices in question > >> needs to setup a detour through the userspace firmware (helper+scripts= ) > >> to pull on the sysfs of that mikrotik platform driver? Wouldn't it > >> be possible to do this more directly? > > > > Yes, its the sole current user as its the only vendor shipping the BDF > > as part of the > > factory data and not like a userspace blob. > > > > I don't see how can it be more direct, its the same setup as when > > getting pre-cal > > data for most devices currently. > > Indeed, not sure how it could be more direct than it already is. I=E2=80= =99m open to suggestions though. > > > I am adding Thibaut who is the author of the platform driver. > > Best, > Thibaut