From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 98ACFC433F5 for ; Fri, 20 May 2022 20:35:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353492AbiETUfY (ORCPT ); Fri, 20 May 2022 16:35:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59386 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237028AbiETUfW (ORCPT ); Fri, 20 May 2022 16:35:22 -0400 Received: from mail-pg1-x529.google.com (mail-pg1-x529.google.com [IPv6:2607:f8b0:4864:20::529]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CD94819FF5B for ; Fri, 20 May 2022 13:35:21 -0700 (PDT) Received: by mail-pg1-x529.google.com with SMTP id j21so8458366pga.13 for ; Fri, 20 May 2022 13:35:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=3vHBVIVFWKzsVxkwc0nHHOOCh+s7xB12NezweFvNW6E=; b=BuiiqR40Fh9qrE/Wrzuu+BttdgbfvoE5pQkQfFAFV/s2HTC2A/0XUWCPD/l4KH7Zd3 AxLHjBC+5RknD/9gzB04Y0DSbIN5PB6HMEcTyuMIZMnQjjl1XocPBuQXZl/QUHXKgfuH 1KRo4Wk0of63noo+XGTjV9GnM8O6wDHcBTBeg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=3vHBVIVFWKzsVxkwc0nHHOOCh+s7xB12NezweFvNW6E=; b=1QUPE97raLF+KfGFK8cKoCNc4V9XXLfQrzU6yW6wV0HIs6CqWJzMCl8QrR7cZo6qgg zfPGCyb8kUNuEUrOF2qBNZBWIXMMMiepxHqgadORv2koAZx9HnxBe+UY2/mdoNdyYIKq 2yOu1t4HSf7tQjSJ9DICqF99wmnjHSkdZvTq74iikBNynTUQeIxBoBjjaj25NlQH9NsJ 7bbF9Ip79ZIsN+bTzpb4GNe7c+0yxRlMl+eYXj8kgpbfe78FAOaTY+VOTODMgVTwrqyb Z7ZvTMVaP3iLNXpJ5EcfpQUPpMTHsVGp2tG6ORMUMPN/sqvPHGM/DlgjAHTCIdd5GdUz llcg== X-Gm-Message-State: AOAM532qqWKu5uSClcdzJ/t7oYaxTMHaKcYxuZXzmptPmeQImFNYf5hn 84hAjRkp1rYVkZxqeBIKEXEMew== X-Google-Smtp-Source: ABdhPJzI7hQHoQSzMwA79g07yOdZRZqt49wF8VqdqwqSu7Dgzggk6BMoyBJC+wYWFmGhcGSRO9zAbQ== X-Received: by 2002:a63:1d6:0:b0:3c1:732a:3855 with SMTP id 205-20020a6301d6000000b003c1732a3855mr9913625pgb.571.1653078920547; Fri, 20 May 2022 13:35:20 -0700 (PDT) Received: from localhost ([2620:15c:11a:202:5332:2096:60a3:3455]) by smtp.gmail.com with UTF8SMTPSA id nh11-20020a17090b364b00b001df4e851aecsm2306272pjb.3.2022.05.20.13.35.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 20 May 2022 13:35:20 -0700 (PDT) Date: Fri, 20 May 2022 13:35:19 -0700 From: Matthias Kaehlcke To: Doug Anderson Cc: Andy Gross , Bjorn Andersson , Rob Herring , Krzysztof Kozlowski , linux-arm-msm , Kevin Lund , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , LKML Subject: Re: [PATCH] arm64: dts: qcom: sc7280: Enable wifi for Chrome OS boards Message-ID: References: <20220518155252.1.I176d4254c79cfaafa38cbe36f066f02f819df9b6@changeid> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 20, 2022 at 01:07:53PM -0700, Doug Anderson wrote: > Hi, > > On Wed, May 18, 2022 at 3:53 PM Matthias Kaehlcke wrote: > > > > Enable the 'wifi' and 'remoteproc_wpss' nodes for all sc7280 > > based Chrome OS boards. Delete the corresponding entries from > > sc7280-idp.dtsi since this file includes sc7280-chrome-common.dtsi. > > > > Signed-off-by: Matthias Kaehlcke > > --- > > > > arch/arm64/boot/dts/qcom/sc7280-chrome-common.dtsi | 13 +++++++++++++ > > arch/arm64/boot/dts/qcom/sc7280-idp.dtsi | 11 ----------- > > 2 files changed, 13 insertions(+), 11 deletions(-) > > Looks right to me. You're also adding the firmware-name, but: > > * That's in the bindings. > > * The name you have there matches what's in the linux-firmware > repository in commit 0d5e9f7e0aa1 ("ath11k: WCN6750 hw1.0: add to > WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1") > > Hmmm, I guess one question is whether this same firmware would also be > used for other, non-Chrome sc7280 devices. If so then the > firmware-name probably belongs straight in sc7280.dtsi? I suppose that > could always happen in a future change if/when we have other sc7280 > devices and it's clear that they're sharing firmware. Thus: It could go either way. One of our wifi engineers mentioned that his contact at QC said the FW should reside directly in /lib/firmware, not in any sub-directory, which would be odd, but up to them ;-) > Reviewed-by: Douglas Anderson Thanks!