From nobody Mon Feb 9 13:57:26 2026 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 561EB3EDAB3; Wed, 21 Jan 2026 19:56:57 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769025417; cv=none; b=AHHkMhaJyTTiv0sjJYbFA6fd28aTExX0xCu7HDBdrTl6ai71Uo38j0jebMI1U5bBqxnG37hH7vpEHz75lZcttEGEKoFYGpkPpwesr/ggVj9NREcAv+4NlDTh6y4yx0hRItoZeWbXfu9bRkXrKcCE7oOji55kLxS8aMBrS9UnXWY= ARC-Message-Signature: i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1769025417; c=relaxed/simple; bh=/ZlnKnKx7utqc5wND/d2GRMNuYYpxYnoMehK3GUY9hQ=; h=From:Date:Subject:MIME-Version:Content-Type:Message-Id:References: In-Reply-To:To:Cc; b=kJnl/+87e1TyglRuhq31pp+raMc86hvrS4E+ha6QsPmzHGDj17ZGi0pk14J8XCE79GHD58krPhbB8Je0TGOoC8ZP8xIh54zvfVsDXmzmE20sp4JZ9XKrVcWAMexK79drf51zij34gOtFk9PYN0jydKxIVNCWCX8Eu1r8sBtwMxI= ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=B3b/aQth; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="B3b/aQth" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BE381C4CEF1; Wed, 21 Jan 2026 19:56:56 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1769025416; bh=/ZlnKnKx7utqc5wND/d2GRMNuYYpxYnoMehK3GUY9hQ=; h=From:Date:Subject:References:In-Reply-To:To:Cc:From; b=B3b/aQthrQzJU9J5LRmk/7/delrvkOOR5vjzUHVjx0YypDVYWHp7m93d8aznCFT2L rtewlrw6IXMuQJSyRLFxOcsFxMn42ruoInR/7VH3qqoeA0enRNNART74n/huMd1574 Luhsc8F+hg+EA22YOdzzqVfnQr934geK0fH780D7M/Vi+4+IEMA+7hD+1/fpS4ZdhA 5vyIXnDL+B9azBNcnFPTXJi5Iyfmvz3ZbqICjSNNoiSlDpPez7h2ZCj95yHxyDdlJV b5cbTu/RM/KNfMaaXN+CiQz9Ag8iT5HDDjM6pyGvpEKOQbCbPBn5x758Q6t6LJqO6H 8Fr6tEI9zn8Rg== From: "Rob Herring (Arm)" Date: Wed, 21 Jan 2026 13:56:34 -0600 Subject: [PATCH v3 01/10] dt-bindings: mtd: brcm,brcmnand: Drop "brcm,brcmnand" compatible for iProc Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <20260121-dt-mtd-partitions-v3-1-ec3af93c8f93@kernel.org> References: <20260121-dt-mtd-partitions-v3-0-ec3af93c8f93@kernel.org> In-Reply-To: <20260121-dt-mtd-partitions-v3-0-ec3af93c8f93@kernel.org> To: Miquel Raynal , Richard Weinberger , Vignesh Raghavendra , Krzysztof Kozlowski , Conor Dooley , Brian Norris , Kamal Dasu , William Zhang , Nick Terrell , David Sterba , =?utf-8?q?Rafa=C5=82_Mi=C5=82ecki?= , Simon Glass , Linus Walleij , Ulf Hansson , Marcus Folkesson , Tony Lindgren , Roger Quadros , Hauke Mehrtens Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, Krzysztof Kozlowski X-Mailer: b4 0.15-dev Some users of "brcm,nand-iproc" include "brcm,brcmnand" and some don't. The "brcm,brcmnand" compatible is not useful for iProc systems as there's a separate driver for iProc. So drop it as a fallback. Reviewed-by: William Zhang Reviewed-by: Krzysztof Kozlowski Signed-off-by: Rob Herring (Arm) --- Documentation/devicetree/bindings/mtd/brcm,brcmnand.yaml | 1 - 1 file changed, 1 deletion(-) diff --git a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.yaml b/Doc= umentation/devicetree/bindings/mtd/brcm,brcmnand.yaml index 064e840aeaa1..3105f8e6cbd6 100644 --- a/Documentation/devicetree/bindings/mtd/brcm,brcmnand.yaml +++ b/Documentation/devicetree/bindings/mtd/brcm,brcmnand.yaml @@ -66,7 +66,6 @@ properties: items: - const: brcm,nand-iproc - const: brcm,brcmnand-v6.1 - - const: brcm,brcmnand - description: BCM63168 SoC-specific NAND controller items: - const: brcm,nand-bcm63168 --=20 2.51.0