From: sashiko-bot@kernel.org
To: "Moteen Shah" <m-shah@ti.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 1/4] dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf
Date: Thu, 12 Nov 2026 09:19:25 +0000 [thread overview]
Message-ID: <sashiko-outbox-210862@kernel.org> (raw)
In-Reply-To: <20261112091027.1601122-2-m-shah@ti.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Medium] dt-bindings: soc: ti: unresolved maintainer objection to
ti,proxy-id
--
commit 5a8bd1f31bfabd409d005d1090df37a55a89dc38
Author: Moteen Shah <m-shah@ti.com>
dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf
This commit adds a Device Tree binding schema for the Texas Instruments
TDA54 MCU domain System Control Module configuration register region and
its clock gates.
> diff --git a/Documentation/devicetree/bindings/soc/ti/ti,tda54-mcu-scm-conf.yaml b/Documentation/devicetree/bindings/soc/ti/ti,tda54-mcu-scm-conf.yaml
> new file mode 100644
> index 0000000000000..111cbb739b5f1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/soc/ti/ti,tda54-mcu-scm-conf.yaml
[ ... ]
> + ti,proxy-id:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + minimum: 0
> + maximum: 7
> + description:
> + Proxy region (0-7) through which this node's clients access
> + claimable registers and their fault status registers.
> +
> + "#clock-cells":
> + const: 1
> + description:
> + The cell selects the ePWM time-base clock gate. Values 0 to 12 select
> + ehrpwm_tbclk0 to ehrpwm_tbclk12, i.e. the gate for ePWM instance N is
> + specifier N.
> +
> +required:
> + - compatible
> + - reg
> + - ti,proxy-id
[Severity: Medium]
As reported by Krzysztof Kozlowski on v2 [1], is the custom ti,proxy-id
property needed here instead of the standard access-controllers binding?
For a single device where the full 0x20000 region covering all 8 proxies
is mapped from reg, the proxy selection does not describe a board-level
hardware difference, and gating register access per host or VM instance
duplicates Documentation/devicetree/bindings/access-controllers/access-controllers.yaml.
[1] https://lore.kernel.org/r/20261028-inventive-screeching-bettong-9f4240@quoll
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112091027.1601122-1-m-shah@ti.com?part=1
next prev parent reply other threads:[~2026-11-12 9:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 9:10 [PATCH v4 0/4] soc: ti: Add TDA54 SCM configuration syscon support Moteen Shah
2026-11-12 9:10 ` [PATCH v4 1/4] dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf Moteen Shah
2026-11-12 9:19 ` sashiko-bot [this message]
2026-11-12 9:10 ` [PATCH v4 2/4] soc: ti: k3-socinfo: Use device managed allocations and unregistration Moteen Shah
2026-11-12 9:10 ` [PATCH v4 3/4] soc: ti: k3-socinfo: Export SoC registration helper Moteen Shah
2026-11-12 9:10 ` [PATCH v4 4/4] soc: ti: Add TDA54 SCM configuration syscon support Moteen Shah
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=sashiko-outbox-210862@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=m-shah@ti.com \
--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