DepSurf

Function: exynos4_mct_tick_start

Status

Regular

• In 4.4: Absent ⚠️
• In 4.8: Absent ⚠️
• In 4.10: Absent ⚠️
• In 4.13: Absent ⚠️
• In 4.15: Absent ⚠️
• In 4.18: Absent ⚠️
• In 5.0: Absent ⚠️
• In 5.3: Absent ⚠️
• In 5.4: Absent ⚠️
• In 5.8: Absent ⚠️
• In 5.11: Absent ⚠️
• In 5.13: Absent ⚠️
• In 5.15: Absent ⚠️
• In 5.19: Absent ⚠️
• In 6.2: Absent ⚠️
• In 6.5: Absent ⚠️
• In 6.8: Absent ⚠️

Arch

• In arm64: Absent ⚠️
• In armhf: ✅

  void exynos4_mct_tick_start(long unsigned int cycles, struct mct_clock_event_device *mevt);
  

  Collision: Unique Static

  Inline: No

  Transformation: False

  Instances:

  In drivers/clocksource/exynos_mct.c (c0c49f18)
  Location: drivers/clocksource/exynos_mct.c:365
  Inline: False
  Direct callers:
    - drivers/clocksource/exynos_mct.c:set_state_periodic
    - drivers/clocksource/exynos_mct.c:exynos4_tick_set_next_event
  

  Symbols:

  c0c49f18-c0c49f84: exynos4_mct_tick_start (STB_LOCAL)
  

• In ppc64el: Absent ⚠️
• In riscv64: Absent ⚠️

Flavor

• In aws: Absent ⚠️
• In azure: Absent ⚠️
• In gcp: Absent ⚠️
• In lowlatency: Absent ⚠️

Differences

Arch