drivers/gpu/drm/msm/msm_dsc_helper.h

File Facts

System

Linux kernel

Corpus path

drivers/gpu/drm/msm/msm_dsc_helper.h

Extension

.h

Size

862 bytes

Lines

28

Domain

Driver Families

Bucket

drivers/gpu

Inferred role

Driver Families: implementation source

Status

source implementation candidate

Why This File Exists

Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.

• Repeatable hardware-adapter layer. Deep compatibility for every driver is out of scope; this atlas records patterns, probe lifecycles, bus glue, IRQ/DMA usage, and links back to core abstractions.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• linux/math.h
• drm/display/drm_dsc_helper.h

Detected Declarations

• function Copyright

Annotated Snippet

#ifndef MSM_DSC_HELPER_H_
#define MSM_DSC_HELPER_H_

#include <linux/math.h>
#include <drm/display/drm_dsc_helper.h>

/**
 * msm_dsc_get_bytes_per_line() - calculate bytes per line
 * @dsc: Pointer to drm dsc config struct
 * Returns: Integer value representing bytes per line. DSI and DP need
 *          to perform further calculations to turn this into pclk_per_intf,
 *          such as dividing by different values depending on if widebus is enabled.
 */
static inline u32 msm_dsc_get_bytes_per_line(const struct drm_dsc_config *dsc)
{
	return dsc->slice_count * dsc->slice_chunk_size;
}

#endif /* MSM_DSC_HELPER_H_ */

Annotation

• Immediate include surface: `linux/math.h`, `drm/display/drm_dsc_helper.h`.
• Detected declarations: `function Copyright`.
• Atlas domain: Driver Families / drivers/gpu.
• 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.