From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from relay.smtp-ext.broadcom.com (relay.smtp-ext.broadcom.com [192.19.144.207]) (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 7365E359A7F; Mon, 16 Mar 2026 20:54:41 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.19.144.207 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773694482; cv=none; b=KEdiw+TZUnq+42QW2dpmtwrNvsPz9NCTYYJS84hmTDMNzIk3yrob75HrgPW7b84RcCyk+GRO9UH3zyEiuR5ULelhWyKhRYoXqj9O1IXT6HdDVg0nlWII+5PKfwvZpLdjYDBUvZiBfhrx+dXKbH0eBCKbUVuvzAh4KL5+I0RzBsY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1773694482; c=relaxed/simple; bh=fME5uma5DRFBzqVFOQIaRvnVYLilkqikxECnajS70uk=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=h+v/IwPA2a/MQVpP1Mx8HydI5QpSDKWwoIa3mjEAs/XtMhqR7johZewPZ1dEO2PGnaYb7u41MwNHQnm1SZHh7CPINKEC7JDUerlgN01kvYU8k6KK6bmcD9ZwCPqYd2S1Mo6az8AoWPtAX5ftyR+xe5BGfTiFkmwlg1y510gocjE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject 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=i7MJkuuX; arc=none smtp.client-ip=192.19.144.207 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject 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="i7MJkuuX" Received: from mail-lvn-it-01.broadcom.com (mail-lvn-it-01.lvn.broadcom.net [10.36.132.253]) by relay.smtp-ext.broadcom.com (Postfix) with ESMTP id 944D6C0003EE; Mon, 16 Mar 2026 13:54:40 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com 944D6C0003EE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com; s=dkimrelay; t=1773694480; bh=fME5uma5DRFBzqVFOQIaRvnVYLilkqikxECnajS70uk=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=i7MJkuuXWpnqpP4qWr0x0IDCaXUPq7jU69ic4z5eHiVCgsi+/MK9Bg91HpGjjlIwj RTzTkXVTBRr96uOe8DG97KsA2m4+5dg5AGJPBrkaeQOtUqh8vFJqYHdxrFp93TC8Bc 8IICXdREzJMpiS4QyZJ8PIQrqKlrsWQaenhauuOc= Received: from fainelli-desktop.igp.broadcom.net (fainelli-desktop.dhcp.broadcom.net [10.67.48.245]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mail-lvn-it-01.broadcom.com (Postfix) with ESMTPSA id 30258A83; Mon, 16 Mar 2026 13:54:40 -0700 (PDT) From: Florian Fainelli To: bcm-kernel-feedback-list@broadcom.com, Gregor Herburger , Andrea della Porta , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Florian Fainelli Cc: Florian Fainelli , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 1/6] arm64: dts: broadcom: rp1: add i2c controller Date: Mon, 16 Mar 2026 13:54:39 -0700 Message-ID: <20260316205439.2146628-1-florian.fainelli@broadcom.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20260226-raspi-dts-updates-v1-1-60832d20ff04@linutronix.de> References: <20260226-raspi-dts-updates-v1-0-60832d20ff04@linutronix.de> <20260226-raspi-dts-updates-v1-1-60832d20ff04@linutronix.de> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: Florian Fainelli On Thu, 26 Feb 2026 09:55:54 +0100, Gregor Herburger wrote: > The RaspberryPi 5 has 7 designware-i2c I2C controller on the RP1 > chipset. > > Add the relevant nodes to the devicetree. > > Signed-off-by: Gregor Herburger > --- Applied to https://github.com/Broadcom/stblinux/commits/devicetree-arm64/next, thanks! -- Florian