SSP: need clock driver for on-demand activation of MCLK/BCLK/LRCLK

This is the mirror of the SOF issue thesofproject/sof#629

We need the ability to activate audio clocks independently either at boot or on-demand. This will require a dedicated kernel module registering the clocks with the clock framework (as done in the Skylake driver) as well as a new IPC.

@plbossart

@plbossart Should we add a new file in the drivers/clk/x86 folder? Does it make sense to reuse skl-ssp-clk.c?

On 2/22/19 1:11 AM, Bard Liao wrote: @plbossart <https://github.com/plbossart> Should we add a new file in the drivers/clk/x86 folder? Does it make sense to reuse skl-ssp-clk.c?

The main point is really how this would be handled by firmware. Currently we have no IPC to tell the firmware to start the clocks on SSP (which really means start a dummy transfer). We can certainly reuse from skl-ssp-clk.c but it's a second order problem. The first issue to agree on is how this will be told to the firmware.

nvme-core: Fix extra device_put() call on error path

FROMGIT: coresight: etm4x: Fix use-after-free of per-cpu etm drvdata

arm64: bpf: fix 32bit unconditional bswap

Bluetooth: Fix alt settings for incoming SCO with transparent coding …

ext4: avoid online resizing failures due to oversized flex bg

powerpc/bpf/32: Fix failing test_bpf tests

Navigation Menu

Repository navigation

SSP: need clock driver for on-demand activation of MCLK/BCLK/LRCLK #314

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

SSP: need clock driver for on-demand activation of MCLK/BCLK/LRCLK #314

Description

Activity

bardliao commented on Feb 22, 2019

plbossart commented on Feb 22, 2019

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions