ssp: move ssp driver out of the cavs specific directory
Shared ssp driver implementation between all possible Intel
platforms and not only cAVS. Currently depends only on cAVS,
since all other supported platforms don't support it.
Implementations for Baytrail and Haswell stay in their respective
platform directiories. It's built based on CONFIG_INTEL_SSP.
Signed-off-by: Tomasz Lauda <email address hidden>
dmic: move dmic driver out of the cavs specific directory
Shares dmic driver implementation between all possible Intel
platforms and not only cAVS. Currently depends only on cAVS,
since all other supported platforms don't support it.
It's built based on CONFIG_INTEL_DMIC.
Signed-off-by: Tomasz Lauda <email address hidden>
alh: move alh driver out of the cavs specific directory
Shares alh driver implementation between all possible Intel
platforms and not only cAVS. Currently depends only on
cAVS, since all other supported platforms don't support it.
It's built based on CONFIG_INTEL_ALH.
Signed-off-by: Tomasz Lauda <email address hidden>
hda: move hda driver out of the cavs specific directory
Shares hda driver implementation between all Intel platforms and
not only cAVS. Currently it depends only on cAVS, since no other
supported Intel platform has the hardware. It's built based on new
CONFIG_INTEL_HDA, which is mandatory for cAVS and not user selectable.
Signed-off-by: Tomasz Lauda <email address hidden>
c939302...
by
Karol Trzcinski <email address hidden>
trace: Pass trace context to logging function
UUID key is too detailed information for logging function to allow
easy functionality extension in future. Trace context structure is
designed to work directly with logging function, so there is no
reason to unpack values from this struct in trace macro-functions
and pass them as separate arguments to trace_log().
Signed-off-by: Karol Trzcinski <email address hidden>
bcd9628...
by
Karol Trzcinski <email address hidden>
Section of this section should be aligned to EXT_MAN_ALIGN,
proper way of doing this with ALIGN() function inside linker
script didn't work, because of removing READONLY attribute
for this segment, what leads to error in rimage.
This solution introduce changes only for platforms, where problem
exists, so generic tools like rimage are kept clean of such a hacks.
Signed-off-by: Karol Trzcinski <email address hidden>
0596f5b...
by
Karol Trzcinski <email address hidden>
logger: Pass input file in -d flag
Such an approach is more logical, user add flag to dump information
and specify what to dump just after it. Using separate argument
with file path and flag to dump is less natural. So after change
`./sof-logger -l file.ldc -d`
will be replaced with
`./sof-logger -d file.ldc`
Signed-off-by: Karol Trzcinski <email address hidden>
