Received: by 2002:a05:6512:3d0e:0:0:0:0 with SMTP id d14csp38535lfv; Tue, 12 Apr 2022 16:20:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwMtpwlAbnaAhQi4UqSxRGi4BTmDgftwTqcP3dFAIjayLZFLNkrzesowYMVYJcjLP7sFAyO X-Received: by 2002:a17:902:9b87:b0:156:bf3e:9ab5 with SMTP id y7-20020a1709029b8700b00156bf3e9ab5mr39817419plp.119.1649805629659; Tue, 12 Apr 2022 16:20:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1649805629; cv=none; d=google.com; s=arc-20160816; b=RJk5eO0Ryc3tR2KnQlsPluiPXiU0kGvpbW4sHFKU+kPnLG9Go+J73BBEuYmq7mGNo0 rYTJpagVXTXjNxUJrAQdWvaCPc07tKCrn7JXm3S7MUhti+SH2HSiilCR2uFUi/9UuOBn oAyt3lhMgYYuunYVHvn8roV0buWuTuQ3ZZuafb2AeG4Hg1evezTkBg2ziigfZqwMXXS9 hD1wbuknRL9WsPRZSaFNh1Y3hRMAuFMDNW3lKEiX3Qb5DyLTbVHE3UXp535w1S9hx6mU 1i7N6Q1bEAreBu1gPCxnCI+4wxMQvn16M8v1H4Iu0tqeFiwHt5Phrx6285ua+dKtnlXR ry5Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:message-id:in-reply-to :date:references:subject:cc:to:from:dkim-signature; bh=rhVsggMX16Z1D0VVF7TXPm6s3Vx4qUaelNBTWaetss4=; b=jFHZ68Og3o8FTOP0JI0bh1m8eI52noOh87SnPBsDm9Kfplr2j4Ub/Npa0s7dkWZO3F 5CaBbTpY1dIt8m0cIH9Aw1Q9KJ+rvjw3lMikVoY6CvJPXyGt3R8ZQU9y4rQp/aQo9+hu MFHGBBR6KDz9CrtkffmPOBV3EV7c6ydDaUxqKc1Sx8t5HvWbbmrqk0AQfGphQPpr7zUG unBbb5U35vSPepV97xXNyElny0AQsGAp8/GXCVx8O+zxRq7dKW2WvZYdeLmsglSuRIfG LwG8orE0TpHty58I5qdUpKhNPB++dE5v2d1xLHPebSgvdVyPOZzcyql0lxnnYrdZYHyd 0eXA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=IFJ0f4ZD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id t8-20020a6549c8000000b003816043f03dsi4120435pgs.562.2022.04.12.16.20.29 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Apr 2022 16:20:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=IFJ0f4ZD; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 9D50051E67; Tue, 12 Apr 2022 14:12:08 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346881AbiDLMAk (ORCPT + 99 others); Tue, 12 Apr 2022 08:00:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59502 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349365AbiDLL5t (ORCPT ); Tue, 12 Apr 2022 07:57:49 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 82A6D60DB5; Tue, 12 Apr 2022 03:47:07 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id 2CD02B81CBB; Tue, 12 Apr 2022 10:47:06 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id C90C5C385A1; Tue, 12 Apr 2022 10:47:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1649760424; bh=8nrqqM3IkuVaMYtRsABBZlIcS5QBrVTQAj/P3+5fYYI=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=IFJ0f4ZD3Llfeaj09qoCE9fqavR0fqRwZhrOfd+ghn84ggQnDQE8GFnbmO08hqc8c JU2zcJpWxRU9xlS2+iOAJVmdlpFlYPlfjMaZ+TgCK19Tk0XJ4Xehrzzr0XlQGF9/Mm d/U1TWLuYMyucl59ci/bEKB6t+9Zu5cmuypNYgNrNXp/8dTfQd1FYIUgiJ/j5MoDyR D0llTsWIxesJzjKOrQy6NdDLgGXJE8RK2eUESE9sWSpQVCZ9xXaQDO/hyUmOQ8YWjo T/KN8c4LpQexG+qvay1ZBzDW2gRysRhGBVsJjK6plN+gbY/I5FgCgpoxQIt9r01whD mtGRjmuH7zPXg== From: Kalle Valo To: Abhishek Kumar Cc: Doug Anderson , Rakesh Pillai , LKML , linux-wireless , "David S. Miller" , Jakub Kicinski , ath10k , netdev Subject: Re: [PATCH 1/2] ath10k: search for default BDF name provided in DT References: <20220107200417.1.Ie4dcc45b0bf365077303c596891d460d716bb4c5@changeid> <87sfrqqfzy.fsf@kernel.org> Date: Tue, 12 Apr 2022 13:46:55 +0300 In-Reply-To: (Abhishek Kumar's message of "Mon, 11 Apr 2022 16:25:10 -0700") Message-ID: <87fsmio9y8.fsf@kernel.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI, RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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-kernel@vger.kernel.org Abhishek Kumar writes: > Hi All, > > Apologies for the late reply, too many things at the same time. Trust me, I know the feeling :) > Just a quick note, Qcomm provided a new BDF file with support for > 'bus=snoc,qmi-board-id=ff' as well, so even without this patch, the > non-programmed devices(with board-id=0xff) would work. However, for > optimization of the BDF search strategy, the above mentioned strategy > would still not work: - The stripping of full Board name would not > work if board-id itself is not programmed i.e. =0xff e.g. for > 'bus=snoc,qmi-board-id=ff,qmi-chip-id=320,variant=GO_LAZOR' => no > match 'bus=snoc,qmi-board-id=ff,qmi-chip-id=320' => no match > 'bus=snoc,qmi-board-id=ff' => no match 'bus=snoc' => no match because > all the BDFs contains board-id=67 Sorry, not fully following your here. Are you saying that the problem is that WCN3990/hw1.0/board-2.bin is missing board file for 'bus=snoc'? That's easy to add, each board file within board-2.bin has multiple names so we can easily select one board file for which we add 'bus=snoc'. > So with this DT patch specifically for case 'bus=snoc,qmi-board-id=ff' > => no match, we fallback to default case ( the one provided in DT) > i.e. 'bus=snoc,qmi-board-id=67' => match . I do not see how exactly > the driver can know that it should check for a board-id of 67. Sorry, not following you here either. Why would the driver need to use board-id 67? > However, to still remove dependency on the DT, we can make the > board-id as no-op if it is not programmed i.e. if the board-id=ff then > we would pick any BDF that match 'bus=snoc,qmi-board-id=' where XX > can be any arbitrary number. Thoughts ? To me using just 'bus=snoc' is more logical than picking up an arbitrary number. But I might be missing something here. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches