From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (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 DAFA123D7FF for ; Thu, 4 Sep 2025 16:08:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757002136; cv=none; b=LRE4W8fgyqE+raclxGdiTSJMz8nwOZPtrPr/XPXQDIJguPjgDXvdXHCqrSU4tHNd6na7CVYOSjgSsqxqopBRjMnwsTjLa5h1qByCNzvnZOW2kPywtrC0Yx3h6uIe1flBbhNSMnbyaHZUYXuJPE7b5FKY7SMcsBxVlLQC0toIyLk= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1757002136; c=relaxed/simple; bh=fGXsrzt6u8YTKnC/hBZpqHUAVKGxcAQu9zwDNMaiVlo=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=f/WMLT63nHqMwVD+BH9C8K3GzrL0AoR+wlm8zo2rui/jxzzMXIdYfpyfJF9IIElXZYQnlsz/8aKK0qoAGejaABUs/yrhuu9QQNnFPrQOoXI4cs51Mj/XHYHWELCNLTmI27iyDfGMQ5yaFRitwDHJDT2qUooX35k1J1BrMcnzuY8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=fwATaZHN; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="fwATaZHN" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=fGXs rzt6u8YTKnC/hBZpqHUAVKGxcAQu9zwDNMaiVlo=; b=fwATaZHNVLw5UQDUrrt/ Vs66TdoJ8AIiN4XiINPlBk6/WdC3Ye80fUOSfLwNnnIZp7G+XlFknHpfUqRYocFC ZRqPaAIsAC7XlIwfQwfnK/n+6qci6i/80I1N65Srr72JaD+FlcMN8L822lp6R6Uc tUq1fD56DjxXBQTmQi9ySso1HHOdGaserRCikoBL0kmsV1fSwrx4X+ueJA/HAfIl rTAuPePQcDgHclAUfcEAO8XoQi6b86E73VrRxIfIPwYiw4vS6vgT85+31+6SSkhR ukCuGscr/4q26PzKnyu7lo1Zp2Upivn5l5M2Ch0A+xIQBlMuZc6zv2ArwTUjYvNE KA== Received: (qmail 3727582 invoked from network); 4 Sep 2025 18:08:50 +0200 Received: by mail.zeus03.de with UTF8SMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 4 Sep 2025 18:08:50 +0200 X-UD-Smtp-Session: l3s3148p1@gcfS7/s9SN8ujnuV Date: Thu, 4 Sep 2025 18:08:49 +0200 From: Wolfram Sang To: Prabhakar Cc: Tommaso Merciai , Alexandre Belloni , Frank Li , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Geert Uytterhoeven , Magnus Damm , linux-i3c@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org, Biju Das , Fabrizio Castro , Lad Prabhakar Subject: Re: [PATCH] dt-bindings: i3c: renesas,i3c: Add RZ/V2H(P) and RZ/V2N support Message-ID: References: <20250904160305.247618-1-prabhakar.mahadev-lad.rj@bp.renesas.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250904160305.247618-1-prabhakar.mahadev-lad.rj@bp.renesas.com> Hi, > Add device tree binding support for the I3C Bus Interface on Renesas > RZ/V2H(P) and RZ/V2N SoCs. The I3C IP on these SoCs is identical to > that found on the RZ/G3E SoC. Cool, has it been tested with devices already? > -title: Renesas RZ/G3S and RZ/G3E I3C Bus Interface > +title: Renesas RZ/G3S, RZ/G3E, RZ/V2H(P) and RZ/V2N I3C Bus Interface I suggest "Renesas I3C Bus Interface". The above is not going to scale. Rest looks good from a glimpse!