Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Akash Sukhavasi" <akash.sukhavasi@gmail.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] dt-bindings: usb: richtek,rt1711h: add missing 'port' property
Date: Mon, 18 May 2026 14:45:19 +0000	[thread overview]
Message-ID: <20260518144521.0A681C2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260518142901.1747-3-akash.sukhavasi@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The `port` node in the device tree example is incorrectly nested inside the `connector` node instead of being at the top level of the `rt1711h@4e` node.
--

commit 18a1ecff9551deb9d653752f739ababa33eb01fd
Author: Akash Sukhavasi <akash.sukhavasi@gmail.com>

dt-bindings: usb: richtek,rt1711h: add missing 'port' property

This commit adds the missing top-level port property to the
richtek,rt1711h schema to describe the role-switch graph endpoint. It also
updates the example to include this new port configuration.

> diff --git a/Documentation/devicetree/bindings/usb/richtek,rt1711h.yaml b/Documentation/devicetree/bindings/usb/richtek,rt1711h.yaml
> --- a/Documentation/devicetree/bindings/usb/richtek,rt1711h.yaml
> +++ b/Documentation/devicetree/bindings/usb/richtek,rt1711h.yaml
[ ... ]
> @@ -107,6 +114,12 @@ examples:
>                };
>              };
>            };
> +
> +          port {
> +            endpoint {
> +              remote-endpoint = <&usb_role_switch>;
> +            };
> +          };
>          };
>        };
>      };

Is this port node indented correctly in the example?

It looks like the 10-space indentation places it inside the connector node
rather than as a top-level property of the rt1711h@4e node as intended by
the schema update.

Should it be aligned with fewer spaces to be a sibling of the connector node
instead?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260518142901.1747-1-akash.sukhavasi@gmail.com?part=2

  reply	other threads:[~2026-05-18 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 14:28 [PATCH 0/2] dt-bindings: usb: richtek,rt1711h: remove .txt binding and fix schema Akash Sukhavasi
2026-05-18 14:29 ` [PATCH 1/2] dt-bindings: usb: richtek,rt1711h: remove deprecated .txt file Akash Sukhavasi
2026-05-18 14:29 ` [PATCH 2/2] dt-bindings: usb: richtek,rt1711h: add missing 'port' property Akash Sukhavasi
2026-05-18 14:45   ` sashiko-bot [this message]
2026-05-18 16:12     ` Akash Sukhavasi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260518144521.0A681C2BCB7@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=akash.sukhavasi@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox