From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 567C73CE4B1 for ; Thu, 9 Jul 2026 08:50:14 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783587015; cv=none; b=M/A9Vkvfcfr8aIUYznkcQtOvyHAOKwTeluCy5Vu0E53HoqX7+HeR8Q65dUq6QfAVZ246Xc3oIO1cX6GrnpR3DwycVFRhnuuTV9qX7OoOrU0Z60isz5X8NRNmnSgm+dJ/WC09zpp62T76J29wG7m7J59l/NKV0pE4nkp8/7ScLLQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783587015; c=relaxed/simple; bh=CZ30nEVVrbIrJTO9++64KG5znMhA0nDWWXNcC2b+oTo=; h=From:Subject:To:Cc:In-Reply-To:References:Content-Type:Date: Message-Id; b=cVtgV4mNrnxTUNc1tsuaDt94cIsvLYMDo7fmmw/uREkyuPxIjSG50hQ9J5qTzU6XpIzAvses08hpgjzWV2Dal+oD2HYOefvfHSD9SIm0cnfvG5EoZd68UvX5LVxlgfQm5huEdTslVX7RPFc+mlP++4pbCMtpZTPw+MNZHRUIRSQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=P6x4YwKZ; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="P6x4YwKZ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 824831F00A3A; Thu, 9 Jul 2026 08:50:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783587014; bh=SnB7NBJvkB6Lwc+UsNdNTbksNkeyE6wuDODerJjvkB8=; h=From:Subject:Reply-To:To:Cc:In-Reply-To:References:Date; b=P6x4YwKZMxKAWiY+f0SJsAaXwr4FB7+MfztDg3QWyIjSiNETYoCl/h5nwT/xuBji8 XftpEBv5E7g/94mnq2+gCoOjbH7stzQgt47fioJcJmiz8ideuapSW2X6yU6Jhb9QGc BDKf+qU+rJUKssoeNxqzyWU7QHd33ushM5KgxIU16iCdVvv9qoCDpf1sxKcQBf2HA3 4XnUr/5SHcX+0koLt4c4Iz+DqwmYliegW4/71ryd/G0J/MG+ewQl0CnD0EuTlwE0fv rDpmaO2WN8Jd598pclXB9rKdoIMVVlzjQ8nLV9S3giqqKBf/5iQTpyACYNlXkci88f QacZ+usvHCAmQ== From: sashiko-bot@kernel.org Subject: Re: [PATCH v4 5/9] dt-bindings: phy: renesas,usb2-phy: Document RZ/G3L PHY bindings Reply-To: sashiko-reviews@lists.linux.dev To: Biju Cc: vkoul@kernel.org, robh@kernel.org, wsa+renesas@sang-engineering.com, conor+dt@kernel.org, olteanv@gmail.com, devicetree@vger.kernel.org, neil.armstrong@linaro.org, linux-phy@lists.infradead.org In-Reply-To: <20260709083108.108370-6-biju.das.jz@bp.renesas.com> References: <20260709083108.108370-1-biju.das.jz@bp.renesas.com> <20260709083108.108370-6-biju.das.jz@bp.renesas.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Date: Thu, 09 Jul 2026 08:50:13 +0000 Message-Id: <20260709085013.824831F00A3A@smtp.kernel.org> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: Thank you for your contribution! Sashiko AI review found 1 potential issue(= s) to consider: - [Low] Missing related device tree binding update for the RZ/G3L USBHS (OT= G) controller. -- --- Patch [5]: [PATCH v4 5/9] dt-bindings: phy: renesas,usb2-phy: Document = RZ/G3L PHY bindings --- commit c4d05b9a2128264caed7e80893a3e4cb7297b32f Author: Biju Das dt-bindings: phy: renesas,usb2-phy: Document RZ/G3L PHY bindings This patch adds device tree binding support for the RZ/G3L (r9a08g046) USB2 PHY. The commit message notes the RZ/G3L is almost identical to the RZ/G3S USB PHY, but with 2 OTG blocks instead of 1. > diff --git a/Documentation/devicetree/bindings/phy/renesas,usb2-phy.yaml = b/Documentation/devicetree/bindings/phy/renesas,usb2-phy.yaml > index 9740e5b335f93..d6b9d08ceec6d 100644 > --- a/Documentation/devicetree/bindings/phy/renesas,usb2-phy.yaml > +++ b/Documentation/devicetree/bindings/phy/renesas,usb2-phy.yaml > @@ -16,6 +16,7 @@ properties: > - enum: > - renesas,usb2-phy-r8a77470 # RZ/G1C > - renesas,usb2-phy-r9a08g045 # RZ/G3S > + - renesas,usb2-phy-r9a08g046 # RZ/G3L [Severity: Low] Does Documentation/devicetree/bindings/usb/renesas,usbhs.yaml also need to = be updated to include the "renesas,usbhs-r9a08g046" compatible string for the RZ/G3L OTG blocks mentioned in the commit message? Currently, renesas,usbhs.yaml enumerates related SoCs like RZ/G3S (renesas,usbhs-r9a08g045) under the renesas,rzg2l-usbhs fallback, but is missing RZ/G3L. This might cause device tree nodes for these OTG blocks to fail schema validation. --=20 Sashiko AI review =C2=B7 https://sashiko.dev/#/patchset/20260709083108.1083= 70-1-biju.das.jz@bp.renesas.com?part=3D5