Skip to content

DT510: TAS6424 — lab validation, rails, GPIOs, TDM vs I2S (Tier C2) #10

@ajlennon

Description

@ajlennon

Parent tracking

Sub-issue of #2 (DT510 BSP bring-up plan).

Scope (Tier C2 — step 1)

Complete TAS6424 class-D bring-up: lab validation, rails, GPIOs, and TDM vs stereo I2S product decision.

Hardware input (@ohull456 + Google Doc, 2026-04-14)

Power (DVDD / VBAT / PVDD): Always-on — no SW sequencing; DTS uses fixed regulators (vddext, tas6424_hi_rail); 12 V / 3.3 V placeholders — confirm vs schematic (@ohull456).

Outputs (codec driver): standby-gpios = GPIO1_IO10 (AMP_STBY#), mute-gpios = GPIO1_IO11 (AMP_MUTE#), active-low — in DTS as &gpio1 10/11 + pinctrl_tas6424_gpio (commit 0fca95f on main).

Inputs (not in ti,tas6424 driver): GPIO1_IO12 (AMP_FAULT#), GPIO1_IO13 (AMP_WARN#) — muxed with pinctrl; Linux driver polls faults via I2C. Optional later: gpio-keys or IRQ consumer if product wants pin-level monitoring.

DAI format: I2S first; TDM deferred.

Deferred (low priority): I2C3 GPIO for charger IRQ / HDMI.

Current state

  • DTS: tas6424@6a has pinctrl, standby / mute GPIOs; tas6424_hi_rail still placeholder voltage — confirm with Ollie.

Work

References

Assignees

Per parent #2: @ajlennon @ohull456

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions