From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pg1-f174.google.com (mail-pg1-f174.google.com [209.85.215.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D735D18DF97 for ; Tue, 20 Aug 2024 12:50:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.215.174 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1724158228; cv=none; b=OGbMS9YI/z7/u7a1lMtufLN+e0t9Mwi4djwMRX9di5MOf3ZEtJpqHDWDQOwEoFaRlDyzcSXC/BKR1bw1XiGziTbOck3mxo663nGbypzDmvVvzh+6xPPMiYNKmIqoQz5DfY65Km7SaXExFAKBYPsXMw4yqDjXeoChoJxynam0guw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1724158228; c=relaxed/simple; bh=o3JYLIeuXXfMYe52twwHljtfqemaqhTyjVwfm7Wesy0=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=QPyz2WOGFCI0hLRuK6hywtEJnEQHGUZt6cvzTMLMH7SjvhnpPRPztvPyyN/hqTgKrYt7ivLDKvqkHHO9fB2d5acwi7ac7Wb+pJMPfgZKtEEnnKGBOExl/UBOcuKZLkRIwnVZsIdFX5RR04R0EKRTTvBZs1/rVxuAHalnfCnd3fc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=broadcom.com; spf=fail smtp.mailfrom=broadcom.com; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b=RSbrx4oB; arc=none smtp.client-ip=209.85.215.174 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=broadcom.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=broadcom.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=broadcom.com header.i=@broadcom.com header.b="RSbrx4oB" Received: by mail-pg1-f174.google.com with SMTP id 41be03b00d2f7-7c3e1081804so3563472a12.3 for ; Tue, 20 Aug 2024 05:50:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; t=1724158225; x=1724763025; darn=vger.kernel.org; h=content-transfer-encoding:in-reply-to:autocrypt:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:from:to:cc:subject:date:message-id:reply-to; bh=Qs9ma4QG5LdeflE2AV0PxSzJpzkXwNO+9SVCx1KRHls=; b=RSbrx4oB4CdoNy2o6272K6jmb3xd+2TyvvrRtkv+IzCJ3AkflJSR/lW08iKynZssDb 553EnmaDaqW4EsVr3Vr/46OiCbqJLqQNw1aK5KOzNoP23KygFLHEpIca17456Cwokfke zmuxGLnvIL7ctVsvfgf0bU4g9rATdoxRNcR+A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724158225; x=1724763025; h=content-transfer-encoding:in-reply-to:autocrypt:from :content-language:references:cc:to:subject:user-agent:mime-version :date:message-id:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=Qs9ma4QG5LdeflE2AV0PxSzJpzkXwNO+9SVCx1KRHls=; b=lmzAp1pwijLXizRojrLEVt8w7/RCHIrEgmGoWeasyEnGSV2gdDy01uk1TnEtgR63dh h09J5cfOwN/OObpG5IXeMtv7LvzVgg7UUriE9G2WonG8hNqHq6Tgkb72DhhZh88tuL+0 KxKLb2WmrCpBcy0dKN955r2mfXOTnyUNidM5JxqAL02/3K8+uyr0ePZuYxRCsuyj7S7V W+m7lxLONRJ6z4tQdZg0JK17L2YupxrAj6Os0my3I3hBN1cafAVDqEjywOlb5tPrw3Sp 8DE+RMmi+MRq+qkZVkTVFYz+f5eMCaKblg+ZyC5QJdEfDlCMMKW1iWCZNesswa6OKzIH GP5w== X-Forwarded-Encrypted: i=1; AJvYcCXgMgg/aLwSmIoZF8X3rXmqHqJaUh/G85UBmiBpM2v1VV47w9LmUsZ7+jnhHCx38ncb0wS05p19BChSVTTBR6DX87wsS+mHGRrgiW2faBY= X-Gm-Message-State: AOJu0Yxr/83vvOOy7S/cmmyqVePTRFrJkrlndUPRXMzQeS6q2Cz32bBP BP91Pq5S2Xhm3QBuPQrUMFYV90SAtGhZwnLIHqE1AKBxULVrVesqyVnEl+QA/Q== X-Google-Smtp-Source: AGHT+IE/zWoTzNwFQB3/n0Le/r4FJzGkyWwuIZAtfJ9eEen6Qko1iXr4Fw17jQuTTUwsd1DT7GQB/Q== X-Received: by 2002:a17:90a:c918:b0:2c9:7cc8:8e33 with SMTP id 98e67ed59e1d1-2d3dffc0fe9mr14233367a91.13.1724158224730; Tue, 20 Aug 2024 05:50:24 -0700 (PDT) Received: from [10.176.68.61] ([192.19.176.250]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-2d3e3c74f3fsm9278835a91.46.2024.08.20.05.50.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 20 Aug 2024 05:50:24 -0700 (PDT) Message-ID: <6777d425-b27f-43d0-ba81-b36ac0b8f929@broadcom.com> Date: Tue, 20 Aug 2024 14:50:18 +0200 Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 1/2] dt-bindings: wireless: restore constraint for brcm,bcm4329-fmac compatible property To: Krzysztof Kozlowski Cc: Kalle Valo , Hector Martin , Krzysztof Kozlowski , devicetree@vger.kernel.org, linux-wireless@vger.kernel.org, brcm80211@lists.linux.dev, asahi@lists.linux.dev References: <20240820101216.355012-1-arend.vanspriel@broadcom.com> <20240820101216.355012-2-arend.vanspriel@broadcom.com> <7881c303-bef1-403a-aa70-30d33558f57f@kernel.org> Content-Language: en-US From: Arend van Spriel Autocrypt: addr=arend.vanspriel@broadcom.com; keydata= xsFNBGP96SABEACfErEjSRi7TA1ttHYaUM3GuirbgqrNvQ41UJs1ag1T0TeyINqG+s6aFuO8 evRHRnyAqTjMQoo4tkfy21XQX/OsBlgvMeNzfs6jnVwlCVrhqPkX5g5GaXJnO3c4AvXHyWik SOd8nOIwt9MNfGn99tkRAmmsLaMiVLzYfg+n3kNDsqgylcSahbd+gVMq+32q8QA+L1B9tAkM UccmSXuhilER70gFMJeM9ZQwD/WPOQ2jHpd0hDVoQsTbBxZZnr2GSjSNr7r5ilGV7a3uaRUU HLWPOuGUngSktUTpjwgGYZ87Edp+BpxO62h0aKMyjzWNTkt6UVnMPOwvb70hNA2v58Pt4kHh 8ApHky6IepI6SOCcMpUEHQuoKxTMw/pzmlb4A8PY//Xu/SJF8xpkpWPVcQxNTqkjbpazOUw3 12u4EK1lzwH7wjnhM3Fs5aNBgyg+STS1VWIwoXJ7Q2Z51odh0XecsjL8EkHbp9qHdRvZQmMu Ns8lBPBkzpS7y2Q6Sp7DcRvDfQQxPrE2sKxKLZVGcRYAD90r7NANryRA/i+785MSPUNSTWK3 MGZ3Xv3fY7phISvYAklVn/tYRh88Zthf6iDuq86m5mr+qOO8s1JnCz6uxd/SSWLVOWov9Gx3 uClOYpVsUSu3utTta3XVcKVMWG/M+dWkbdt2KES2cv4P5twxyQARAQABzS9BcmVuZCB2YW4g U3ByaWVsIDxhcmVuZC52YW5zcHJpZWxAYnJvYWRjb20uY29tPsLBhwQTAQgAMRYhBLX1Z69w T4l/vfdb0pZ6NOIYA/1RBQJj/ek9AhsDBAsJCAcFFQgJCgsFFgIDAQAACgkQlno04hgD/VGw 8A//VEoGTamfCks+a12yFtT1d/GjDdf3i9agKMk3esn08JwjJ96x9OFFl2vFaQCSiefeXITR K4T/yT+n/IXntVWT3pOBfb343cAPjpaZvBMh8p32z3CuV1H0Y+753HX7gdWTEojGWaWmKkZh w3nGoRZQEeAcwcF3gMNwsM5Gemj7aInIhRLUeoKh/0yV85lNE1D7JkyNheQ+v91DWVj5/a9X 7kiL18fH1iC9kvP3lq5VE54okpGqUj5KE5pmHNFBp7HZO3EXFAd3Zxm9ol5ic9tggY0oET28 ucARi1wXLD/oCf1R9sAoWfSTnvOcJjG+kUwK7T+ZHTF8YZ4GAT3k5EwZ2Mk3+Rt62R81gzRF A6+zsewqdymbpwgyPDKcJ8YUHbqvspMQnPTmXNk+7p7fXReVPOYFtzzfBGSCByIkh1bB45jO +TM5ZbMmhsUbqA0dFT5JMHjJIaGmcw21ocgBcLsJ730fbLP/L08udgWHywPoq7Ja7lj5W0io ZDLz5uQ6CEER6wzD07vZwSl/NokljVexnOrwbR3wIhdr6B0Hc/0Bh7T8gpeM+QcK6EwJBG7A xCHLEacOuKo4jinf94YQrOEMnOmvucuQRm9CIwZrQ69Mg6rLn32pA4cK4XWQN1N3wQXnRUnb MTymLAoxE4MInhDVsZCtIDFxMVvBUgZiZZszN33OwU0EY/3pIgEQAN35Ii1Hn90ghm/qlvz/ L+wFi3PTQ90V6UKPv5Q5hq+1BtLA6aj2qmdFBO9lgO9AbzHo8Eizrgtxp41GkKTgHuYChijI kdhTVPm+Pv44N/3uHUeFhN3wQ3sTs1ZT/0HhwXt8JvjqbhvtNmoGosZvpUCTwiyM1VBF/ICT ltzFmXd5z7sEuDyZcz9Q1t1Bb2cmbhp3eIgLmVA4Lc9ZS3sK1UMgSDwaR4KYBhF0OKMC1OH8 M5jfcPHR8OLTLIM/Thw0YIUiYfj6lWwWkb82qa4IQvIEmz0LwvHkaLU1TCXbehO0pLWB9HnK r3nofx5oMfhu+cMa5C6g3fBB8Z43mDi2m/xM6p5c3q/EybOxBzhujeKN7smBTlkvAdwQfvuD jKr9lvrC2oKIjcsO+MxSGY4zRU0WKr4KD720PV2DCn54ZcOxOkOGR624d5bhDbjw1l2r+89V WLRLirBZn7VmWHSdfq5Xl9CyHT1uY6X9FRr3sWde9kA/C7Z2tqy0MevXAz+MtavOJb9XDUlI 7Bm0OPe5BTIuhtLvVZiW4ivT2LJOpkokLy2K852u32Z1QlOYjsbimf77avcrLBplvms0D7j6 OaKOq503UKfcSZo3lF70J5UtJfXy64noI4oyVNl1b+egkV2iSXifTGGzOjt50/efgm1bKNkX iCVOYt9sGTrVhiX1ABEBAAHCwXYEGAEIACAWIQS19WevcE+Jf733W9KWejTiGAP9UQUCY/3p PgIbDAAKCRCWejTiGAP9UaC/EACZvViKrMkFooyACGaukqIo/s94sGuqxj308NbZ4g5jgy/T +lYBzlurnFmIbJESFOEq0MBZorozDGk+/p8pfAh4S868i1HFeLivVIujkcL6unG1UYEnnJI9 uSwUbEqgA8vwdUPEGewYkPH6AaQoh1DdYGOleQqDq1Mo62xu+bKstYHpArzT2islvLdrBtjD MEzYThskDgDUk/aGPgtPlU9mB7IiBnQcqbS/V5f01ZicI1esy9ywnlWdZCHy36uTUfacshpz LsTCSKICXRotA0p6ZiCQloW7uRH28JFDBEbIOgAcuXGojqYx5vSM6o+03W9UjKkBGYFCqjIy Ku843p86Ky4JBs5dAXN7msLGLhAhtiVx8ymeoLGMoYoxqIoqVNaovvH9y1ZHGqS/IYXWf+jE H4MX7ucv4N8RcsoMGzXyi4UbBjxgljAhTYs+c5YOkbXfkRqXQeECOuQ4prsc6/zxGJf7MlPy NKowQLrlMBGXT4NnRNV0+yHmusXPOPIqQCKEtbWSx9s2slQxmXukPYvLnuRJqkPkvrTgjn5d eSE0Dkhni4292/Nn/TnZf5mxCNWH1p3dz/vrT6EIYk2GSJgCLoTkCcqaM6+5E4IwgYOq3UYu AAgeEbPV1QeTVAPrntrLb0t0U5vdwG7Xl40baV9OydTv7ghjYZU349w1d5mdxg== In-Reply-To: <7881c303-bef1-403a-aa70-30d33558f57f@kernel.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 8/20/2024 1:39 PM, Krzysztof Kozlowski wrote: > On 20/08/2024 13:27, Krzysztof Kozlowski wrote: >> On Tue, Aug 20, 2024 at 12:12:15PM +0200, Arend van Spriel wrote: >>> When extending the bindings for Apple PCIe devices the compatible property >>> specification was changed. However, it was changed such that for these >>> devices it was no longer necessary to have "brcm,bcm4329-fmac" listed as >>> string in the compatible list property as it was before that extension. >> >> Apart that this was never tested... That statement is not true. Look at >> "fixed" commit - it is not doing like that at all. >> >> I don't understand the reasoning. >> >>> This patch restores that constraint. >>> >>> Fixes: e2e37224e8b3 ("dt-bindings: net: bcm4329-fmac: Add Apple properties & chips") >>> Signed-off-by: Arend van Spriel >>> --- >>> .../net/wireless/brcm,bcm4329-fmac.yaml | 19 ++++++++++--------- >>> 1 file changed, 10 insertions(+), 9 deletions(-) >>> >>> diff --git a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml >>> index e564f20d8f41..47f90446322f 100644 >>> --- a/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml >>> +++ b/Documentation/devicetree/bindings/net/wireless/brcm,bcm4329-fmac.yaml >>> @@ -7,7 +7,7 @@ $schema: http://devicetree.org/meta-schemas/core.yaml# >>> title: Broadcom BCM4329 family fullmac wireless SDIO/PCIE devices >>> >>> maintainers: >>> - - Arend van Spriel >>> + - Arend van Spriel >>> >>> description: >>> The Broadcom Single chip MAC part for the BCM4329 family and >>> @@ -27,7 +27,6 @@ properties: >>> - brcm,bcm4341b0-fmac >>> - brcm,bcm4341b4-fmac >>> - brcm,bcm4341b5-fmac >>> - - brcm,bcm4329-fmac >>> - brcm,bcm4330-fmac >>> - brcm,bcm4334-fmac >>> - brcm,bcm43340-fmac >>> @@ -46,13 +45,15 @@ properties: >>> - cypress,cyw43012-fmac >>> - infineon,cyw43439-fmac >>> - const: brcm,bcm4329-fmac >>> - - enum: >>> - - brcm,bcm4329-fmac >>> - - pci14e4,43dc # BCM4355 >>> - - pci14e4,4464 # BCM4364 >>> - - pci14e4,4488 # BCM4377 >>> - - pci14e4,4425 # BCM4378 >>> - - pci14e4,4433 # BCM4387 >>> + - items: >>> + - enum: >>> + - pci14e4,43dc # BCM4355 >>> + - pci14e4,4464 # BCM4364 >>> + - pci14e4,4488 # BCM4377 >>> + - pci14e4,4425 # BCM4378 >>> + - pci14e4,4433 # BCM4387 >>> + - const: brcm,bcm4329-fmac >>> + - const: brcm,bcm4329-fmac >> >> And this does not make sense... You claim that some constrained was >> droppped and you re-add it, but in fact you still add the same code as >> it was before. >> >> NAK. > > Ah, the last "const" actually makes sense, I missed that. > > Commit still however lacks rationale why these devices are compatible. > Plus existing rationale that e2e37224e8b3 changed something is entirely > WRONG. It changed nothing. ZERO. It only added new devices, which was > claimed are not compatible with brcm,bcm4329-fmac. So is that claim true? What does it mean that these new devices are not compatible. If they are they should be in a separate binding or the applicable properties for these devices should be made conditional. > Now if you claim that original commit which said "these devices are not > compatible with brcm,bcm4329-fmac", then please provide arguments, not > just say "other commit did something". It did nothing... Not entirely true. Indeed new devices were added for which no "brcm,bcm4329-fmac" string is required in the compatible property. Also the commit added new properties for these new devices. Now in my opinion a driver should not use these properties without a "compatible" check. Hope we can agree to that. However, the driver patch for supporting the binding change does no such thing. So if we leave the binding as it currently is the driver will have to check if compatible has any of the listed PCI IDs before processing the properties. As all properties old and new are marked as optional I can not come up with an argument that these new devices are *not* compatible with brcm,bcm4329-fmac. Regards, Arend > Best regards, > Krzysztof >