Received: by 2002:a05:7412:b995:b0:f9:9502:5bb8 with SMTP id it21csp4622406rdb; Fri, 29 Dec 2023 07:51:52 -0800 (PST) X-Google-Smtp-Source: AGHT+IF0liKqspW4S575VNvrbQ557olUnL++CWweusUvNtIVq0S+wVP+wmR6o+iZqgXte6Cdwrsv X-Received: by 2002:a05:620a:4087:b0:781:6055:9283 with SMTP id f7-20020a05620a408700b0078160559283mr5443085qko.64.1703865112634; Fri, 29 Dec 2023 07:51:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1703865112; cv=none; d=google.com; s=arc-20160816; b=Y6Hu5EQ84EyvJ3cuWdiwwqiok+vv8UY7N8zGnQcWOb7MiqrlqMVrFmnLIJbv+1u3di 8X06fXo20dbcSypsPtfOD0F0Kg+fXpaZaEuomTa2/NnKMFbMeQaKwcYi1xdlNoK8EWRh 7602LbZmhBTAXsJG50xKOthdkZnEibm8mLUdHQW7D3sU/VHZph2IytPdYIdTUn1Uvde0 dCjNso2xrQZduJzKA+xaXNz5ftGgf5t2COiqE4QHR1DtKYGjl4ktijX1eTHPi+rVnmWt IE7N9yyWTFJ7jaGjyFCp8658pl24DBXiVphVPudKNmENHLBorGhQ71vyObuo1SrJ3WWd wLzg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:list-unsubscribe:list-subscribe:list-id:precedence :references:message-id:subject:cc:to:from:date:dkim-signature; bh=0ftZcZqCImhq74HCuLwcTrqZrFr9X6xA/U+qEDxoTvE=; fh=ev8cWMV0MlP1omY3+Tm88M4DRdHF7McRSf2sMfejlSQ=; b=jTjVyPSaMrfcwsRCSLbTNl8nunzQll/nv6veXorgtGg75YPcQ2pkNSpfiAXrJlVWlP YHyiGXiybNLtF08QkS7DLhSDn4G8aZe69irn2a1d+HzfS78QFFjfy6WTfZPFFYk9SJHA FoANkETQfA8x0vYUBojAHrVkpTn3p94Wq5sfUbUL77Ot4eeOqnsbPd2ncGVTgtFyec1z vaqCcHyyVbTtAuR4tl14udU1cYCmhiD8emGm6Tvb4S9J3142al5ETe0cktB71A0l32Up 1f1pCndLBTAfW9rgVg+WF7JPu+edIYLsgsJVMdg4zXI56rLhG+xfbkLvhNCPr0fgZ9QQ X3OA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Rv8Pia6H; spf=pass (google.com: domain of linux-bluetooth+bounces-797-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-bluetooth+bounces-797-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from ny.mirrors.kernel.org (ny.mirrors.kernel.org. [147.75.199.223]) by mx.google.com with ESMTPS id l17-20020a05620a28d100b0077da9bb98a7si19996685qkp.347.2023.12.29.07.51.52 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 29 Dec 2023 07:51:52 -0800 (PST) Received-SPF: pass (google.com: domain of linux-bluetooth+bounces-797-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=Rv8Pia6H; spf=pass (google.com: domain of linux-bluetooth+bounces-797-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) smtp.mailfrom="linux-bluetooth+bounces-797-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ny.mirrors.kernel.org (Postfix) with ESMTPS id 6361D1C229F5 for ; Fri, 29 Dec 2023 15:51:52 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 4494D12B7B; Fri, 29 Dec 2023 15:51:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="Rv8Pia6H" X-Original-To: linux-bluetooth@vger.kernel.org Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A1E62125DC; Fri, 29 Dec 2023 15:51:32 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 12719C43391; Fri, 29 Dec 2023 15:51:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703865092; bh=7O3tlE/TnK1/XnaVJFlVImIMjHjO4tOg8Bzzxg1t2QA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Rv8Pia6HyhjgKIdp3aIC9TJ8IMuQkjU+xFoZYQHFVi3bYo0W7bq/M6eSRHSG9DCQ5 h+MlW7AW8pcTqylL0C2uuHXrOHgUX5YcbK1+5CMcYs5U2OXFGiJGialB+38u4IClI3 jPql9i4xdDjDokz2etKcR9gm7w0V+U3Nmp7cVYOkiIyL7n1RHKAU6wcHqJEGjUl3bX QLmWQyhV9aLtxgYzafd9FOkdlyWr13sY2BEzw76VfSq+SqCxTJXVGGx1XpIibiXcvY 247PLrOXNl0gEp6P8BdWKcWTtTFzibE/m5QX67quu/JDl3zAeG1aD3Orx4IPnsSsQH mr72NXNFs1p2A== Received: from johan by xi.lan with local (Exim 4.96.2) (envelope-from ) id 1rJF8v-0005m6-1i; Fri, 29 Dec 2023 16:51:25 +0100 Date: Fri, 29 Dec 2023 16:51:25 +0100 From: Johan Hovold To: Neal Gompa Cc: Johan Hovold , Luiz Augusto von Dentz , Marcel Holtmann , Johan Hedberg , Hector Martin , Sven Peter , Alyssa Rosenzweig , asahi@lists.linux.dev, linux-arm-kernel@lists.infradead.org, linux-bluetooth@vger.kernel.org, linux-kernel@vger.kernel.org, stable@vger.kernel.org, Felix Zhang Subject: Re: [PATCH] Bluetooth: hci_bcm4377: do not mark valid bd_addr as invalid Message-ID: References: <20231227101003.10534-1-johan+linaro@kernel.org> Precedence: bulk X-Mailing-List: linux-bluetooth@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Fri, Dec 29, 2023 at 10:11:32AM -0500, Neal Gompa wrote: > On Wed, Dec 27, 2023 at 5:10 AM Johan Hovold wrote: > > > > A recent commit restored the original (and still documented) semantics > > for the HCI_QUIRK_USE_BDADDR_PROPERTY quirk so that the device address > > is considered invalid unless an address is provided by firmware. > > > > This specifically means that this flag must only be set for devices with > > invalid addresses, but the Broadcom BCM4377 driver has so far been > > setting this flag unconditionally. > > > > Fortunately the driver already checks for invalid addresses during setup > > and sets the HCI_QUIRK_INVALID_BDADDR flag, which can simply be replaced > > with HCI_QUIRK_USE_BDADDR_PROPERTY to indicate that the default address > > is invalid but can be overridden by firmware (long term, this should > > probably just always be allowed). > > > > Fixes: 6945795bc81a ("Bluetooth: fix use-bdaddr-property quirk") > > Cc: stable@vger.kernel.org # 6.5 > > Reported-by: Felix Zhang > > Link: https://lore.kernel.org/r/77419ffacc5b4875e920e038332575a2a5bff29f.camel@mrman314.tech/ > > Signed-off-by: Johan Hovold > Looks good to me. This replaces the other patch[1], I take it? Yes, but as Sven explained here, that patch is also correct even though that wasn't obvious from just reading the commit message (which should be amended in my opinion): https://lore.kernel.org/asahi/AB87C916-9CF9-4B8C-AFF5-74CA4151C4FC@svenpeter.dev/ > Reviewed-by: Neal Gompa Thanks for reviewing. > [1]: https://lore.kernel.org/asahi/aaa107865f4cbd61f8f9006fd3e7ac43b5d1bdad.camel@mrman314.tech/ Johan