Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp2816172iog; Mon, 27 Jun 2022 03:37:18 -0700 (PDT) X-Google-Smtp-Source: AGRyM1tnCfbYwMFsudYGZ1NvkQrEkDRmMf3nS3dHTV/dJylG97OoHCMPskzemuPxOchZ+AQnKnl/ X-Received: by 2002:a17:906:2c12:b0:726:94a0:2708 with SMTP id e18-20020a1709062c1200b0072694a02708mr8386318ejh.179.1656326238315; Mon, 27 Jun 2022 03:37:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656326238; cv=none; d=google.com; s=arc-20160816; b=ZSfubSH+OKENVYeCf+nSKqR3n04Yv6gjOmIcJQxjoeT3xg++1oBpxzb5wXoFmzWFJo rLdmB/8TeuowY1v1/PjPWr8aLRKCyKdnYGg4tS2YkSW9etufu/Xd+UDYYfeJavX/FW2L 291tse8RpWJiAG9kATBufJxxVxFiQbXm3WXVUy6iRB8AVukuM+viJRi7+fgx8gOdkjVi OTdZzxFeEHF4zYmIA0NffiBYOdroZAYviP4xi0NGxJbED1r5TCCiJutQidTsWzUs7zgA tUDLRuiMlDCMhG6BVLJNKR5St8A1mnXfFSKU6B0Eg4QXH5vTYEbvSTffjd7Mtp0S4ygC nJaA== 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=cZfAPaEvqTx34DnDPzb0WJHLTgfejH45gbcwnO/wivg=; b=GRu8jAspgUDRCgJW7Vu0Qv2HhZ/u+Vq6ejHHXafLjpI5mm4nN2DFkOXZXrTknSgBvd oZV0Sjflj9mwQKyhLar5xI2jxLVN8EiIv9HAZ4Y9nDJnGFQH9UgvI1sMYq98JhCqJEOX W3JSGHHf6jFz/BUnlOUdrAbbSCKWse0g0ARFEJE0lAZ9KdZ8VoWaFxHwxC0VyhWuCLH8 ++Een0cBPDuSsPk8YBhmOOTwftMKoEVolQ7C7HtO4FwpFcl+t22Ds8uo/lC5aunqNxzY VvnbQjV/eJ6s4NqE7Ljr0M9AI8D+2ULV61lDAl/ricKMxFeviWBPJLbCNIjZHoqYV50B 2gow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=G2l+hKTC; 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=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 h8-20020a056402280800b0042fafec8901si14610325ede.130.2022.06.27.03.37.01; Mon, 27 Jun 2022 03:37:18 -0700 (PDT) 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=@gmail.com header.s=20210112 header.b=G2l+hKTC; 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=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233277AbiF0Kam (ORCPT + 64 others); Mon, 27 Jun 2022 06:30:42 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37704 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232441AbiF0Kal (ORCPT ); Mon, 27 Jun 2022 06:30:41 -0400 Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 36BA86261; Mon, 27 Jun 2022 03:30:39 -0700 (PDT) Received: by mail-qv1-xf2d.google.com with SMTP id 89so14165695qvc.0; Mon, 27 Jun 2022 03:30:39 -0700 (PDT) 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; bh=cZfAPaEvqTx34DnDPzb0WJHLTgfejH45gbcwnO/wivg=; b=G2l+hKTC3b/3VUqvEpG03cbAWnBPUCxVt0TElZyrlXe9sLwg2fGZr+Xbz7KNps23gX FUHqn/6nL6V+5PnjpOPvbU4+0MmRB82Um2XU44C0uYkdL/cw5EC6nUECFdLsKTNCSEIL TYiO7Zif4ZqUm3feIrFdS5VmRvbQcaaCtvnT2zdYqNg6RoAbf/rb6RLjUw4wzHMJvJJo FmbQ93mhlFAyaXF901/8R+aOozJuguPprdQpTYaYCVaftU/st+gZ+DjZ4DzPsSSYEcVo KBQi1zWKuk77SiLYtPDPK8cAa3OTSPMfBFrqeaP0+noIs6TO5oysc1G4glI+yYaHj6nx GIvg== 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; bh=cZfAPaEvqTx34DnDPzb0WJHLTgfejH45gbcwnO/wivg=; b=YcpWuWmC7AWCvvtsu8YSe61YPS/2vBbs9ohJQcxdK7gO9m/daWje/8CFZ6UD0uuIS/ TqNRU8QSiyXMyITnunAIqMrHRz6hkW0XpZGUn3qYO5rfnONSMFfZMMI5tIfx/GojunuC yv2NWhDmw06EaTDSxU2gEpSv/9iNf0MhOXCa2d+fnxFcaK9Z4gJRl7PQoa3a10+32Sj8 v4FMv5njJEPC3uQJC9HW3XPakB/uuutYNquntqtCMZAKBULsPouxYqRAUFnktocSsNc2 o4L+pkYdy3x4tjv7+svpVerfSn6mXmZjQbIYjXETAC+iU3sWguTcWuwdL9GAMgVBRbkT fVCA== X-Gm-Message-State: AJIora+8TfA0F3xzWX/FFhYGpCbd8gAfUaR64hakAfaaq+kUbU3kOCkm rAyjg0rCgckKrYNo1PAUlxOpgRUSTCo6ESsO9jM= X-Received: by 2002:a05:622a:1791:b0:317:76d8:d17f with SMTP id s17-20020a05622a179100b0031776d8d17fmr8667214qtk.82.1656325838358; Mon, 27 Jun 2022 03:30:38 -0700 (PDT) MIME-Version: 1.0 References: <20220621135339.1269409-1-robimarko@gmail.com> <87o7yeo104.fsf@kernel.org> In-Reply-To: <87o7yeo104.fsf@kernel.org> From: Robert Marko Date: Mon, 27 Jun 2022 12:30:27 +0200 Message-ID: Subject: Re: [PATCH 1/2] dt-bindings: net: wireless: ath11k: add new DT entry for board ID To: Kalle Valo Cc: davem@davemloft.net, Eric Dumazet , kuba@kernel.org, pabeni@redhat.com, Rob Herring , krzysztof.kozlowski+dt@linaro.org, ath11k@lists.infradead.org, linux-wireless@vger.kernel.org, netdev@vger.kernel.org, Devicetree List , open list 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,FREEMAIL_FROM, RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Mon, 27 Jun 2022 at 12:27, Kalle Valo wrote: > > Robert Marko writes: > > > bus + qmi-chip-id + qmi-board-id and optionally the variant are currently > > used for identifying the correct board data file. > > > > This however is sometimes not enough as all of the IPQ8074 boards that I > > have access to dont have the qmi-board-id properly fused and simply return > > the default value of 0xFF. > > > > So, to provide the correct qmi-board-id add a new DT property that allows > > the qmi-board-id to be overridden from DTS in cases where its not set. > > This is what vendors have been doing in the stock firmwares that were > > shipped on boards I have. > > What's wrong with using 0xff? Ie. something like this: > > bus=ahb,qmi-chip-id=0,qmi-board-id=255,variant=foo > > Or maybe even just skip qmi-board-id entirely if it's not supported? So > that the board file string would be something like: > > bus=ahb,qmi-chip-id=0,variant=foo > > I really would like to avoid adding more DT properties unless it's > absolutely critical. Well, I suppose that due to the variant property we can avoid "correcting" the qmi-board-id Regards, Robert > > -- > https://patchwork.kernel.org/project/linux-wireless/list/ > > https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches