Documentation/devicetree/bindings/remoteproc/ti,hsm-m4fss.yaml
Source file repositories/reference/linux-study-clean/Documentation/devicetree/bindings/remoteproc/ti,hsm-m4fss.yaml
File Facts
- System
- Linux kernel
- Corpus path
Documentation/devicetree/bindings/remoteproc/ti,hsm-m4fss.yaml- Extension
.yaml- Size
- 1668 bytes
- Lines
- 73
- Domain
- Support Tooling And Documentation
- Bucket
- Documentation
- Inferred role
- Support Tooling And Documentation: configuration, schema, or hardware description
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
%YAML 1.2
---
$id: http://devicetree.org/schemas/remoteproc/ti,hsm-m4fss.yaml#
$schema: http://devicetree.org/meta-schemas/core.yaml#
title: TI K3 HSM M4F processor subsystems
maintainers:
- Beleswar Padhi <b-padhi@ti.com>
description: |
Some K3 family SoCs have a HSM (High Security Module) M4F core in the
Wakeup Voltage Domain which could be used to run secure services like
Authentication. Some of those are J721S2, J784S4, J722S, AM62X.
$ref: /schemas/arm/keystone/ti,k3-sci-common.yaml#
properties:
compatible:
enum:
- ti,hsm-m4fss
reg:
items:
- description: SRAM0_0 internal memory region
- description: SRAM0_1 internal memory region
- description: SRAM1 internal memory region
reg-names:
items:
- const: sram0_0
- const: sram0_1
- const: sram1
resets:
maxItems: 1
firmware-name:
maxItems: 1
required:
- compatible
- reg
- reg-names
- resets
- firmware-name
- ti,sci
- ti,sci-dev-id
- ti,sci-proc-ids
unevaluatedProperties: false
examples:
- |
soc {
#address-cells = <2>;
#size-cells = <2>;
remoteproc@43c00000 {
compatible = "ti,hsm-m4fss";
reg = <0x00 0x43c00000 0x00 0x20000>,
<0x00 0x43c20000 0x00 0x10000>,
<0x00 0x43c30000 0x00 0x10000>;
reg-names = "sram0_0", "sram0_1", "sram1";
resets = <&k3_reset 225 1>;
firmware-name = "hsm.bin";
ti,sci = <&sms>;
ti,sci-dev-id = <225>;
ti,sci-proc-ids = <0x80 0xff>;
Annotation
- Atlas domain: Support Tooling And Documentation / Documentation.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.