include/dt-bindings/soc/renesas,r8a78000-mfis.h

File Facts

System

Linux kernel

Corpus path

include/dt-bindings/soc/renesas,r8a78000-mfis.h

Extension

.h

Size

1042 bytes

Lines

29

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

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

#ifndef _DT_BINDINGS_SOC_RENESAS_R8A78000_MFIS_H
#define _DT_BINDINGS_SOC_RENESAS_R8A78000_MFIS_H

/*
 * Constants for the second mbox-cell of the Renesas MFIS IP core. To be treated
 * as bit flags which can be ORed.
 */

/*
 * MFIS HW design before r8a78001 requires a channel to be marked as either
 * TX or RX.
 */
#define MFIS_CHANNEL_TX (0 << 0)
#define MFIS_CHANNEL_RX (1 << 0)

/*
 * MFIS variants before r8a78001 work with pairs of IICR and EICR registers.
 * Usually, it is specified in the datasheets which of the two a specific core
 * should use. Then, it does not need extra description in DT. For plain MFIS
 * of r8a78000, this is selectable, though. According to the system design and
 * the firmware in use, these channels need to be marked. This is not needed
 * with other versions of the MFIS, not even with MFIS-SCP of r8a78000.
 */
#define MFIS_CHANNEL_IICR (0 << 1)
#define MFIS_CHANNEL_EICR (1 << 1)

#endif /* _DT_BINDINGS_SOC_RENESAS_R8A78000_MFIS_H */

Annotation

• Atlas domain: Repository Root And Misc / include.
• Implementation status: source implementation candidate.

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.