Searched refs:SOF (Results 1 – 25 of 30) sorted by relevance
12
| /Zephyr-latest/modules/ |
| D | Kconfig.sof | 7 config SOF config
8 bool "Sound Open Firmware (SOF)"
11 Build Sound Open Firmware (SOF) support.
|
| /Zephyr-latest/soc/mediatek/mt8xxx/ |
| D | CMakeLists.txt | 17 # available; generally it isn't except in SOF builds). Note that the
24 # containing the .toml files for the platforms, which SOF will set on
26 # by Zephyr and needs tob e found by a SOF build by passing it in
30 # exercised from a SOF build and it doesn't belong here in Zephyr;
31 # rimage is a SOF tool. Signing audio firmware is only done for SOF
33 # should live in SOF where it doesn't have to be duplicated for every
|
| D | Kconfig.defconfig | 74 # fact SOF has its own heap. Just leave a little for stray malloc()
|
| D | linker.ld | 68 /* SOF extended manifest */
|
| /Zephyr-latest/drivers/dma/ |
| D | Kconfig.nxp_sof_host_dma | 5 bool "NXP DMA driver used by SOF's host component"
10 SOF (Sound Open Firmware) host
12 is used by the SOF host component to
|
| /Zephyr-latest/soc/intel/intel_adsp/ |
| D | Kconfig.defconfig | 10 # A workaround for HWMv2 to recover SOF arch/xtensa defaults overridden by arch/host.
11 if SOF
|
| D | Kconfig | 39 default $(dt_compat_enabled,$(DT_COMPAT_INTEL_ADSP_HOST_IPC)) if !SOF
40 default $(dt_compat_enabled,$(DT_COMPAT_INTEL_ADSP_IDC)) if !SOF
43 Currently SOF has its own driver for this hardware.
89 addresses here. The SOF application also makes direct use
137 SOF traditionally contains this workaround on its ADSP
|
| /Zephyr-latest/drivers/ipm/ |
| D | Kconfig.intel_adsp | 28 with host driver and SOF source code (must match
36 Location of the "outbox" region for SOF IPC3/4 message
39 location must be synchronized with host driver and SOF
|
| /Zephyr-latest/drivers/audio/mic_privacy/intel/ |
| D | Kconfig.mic_privacy | 1 # SOF Microphone Privacy configuration options
|
| /Zephyr-latest/drivers/dai/intel/hda/ |
| D | Kconfig.hda | 1 # SOF HDA configuration options
|
| /Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/ |
| D | README.rst | 28 USB host. Because the sample clock is independent from USB SOF it is inevitable
45 The nRF5340 is capable of counting both edges of I2S LRCLK relative to USB SOF
48 provide relative timing information between I2S FRAMESTART and USB SOF.
51 to USB SOF offset) has been tested on :ref:`nrf5340dk_nrf5340`.
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.adsp_mtrace | 10 using the SOF Linux driver mtrace buffer layout.
|
| /Zephyr-latest/boards/nxp/imx8qm_mek/ |
| D | imx8qm_mek_mimx8qm6_adsp_defconfig | 11 # TODO: maybe move this to SOF?
|
| /Zephyr-latest/boards/nxp/imx8qxp_mek/ |
| D | imx8qxp_mek_mimx8qx6_adsp_defconfig | 11 # TODO: maybe move this to SOF?
|
| /Zephyr-latest/drivers/dai/intel/ssp/ |
| D | Kconfig.ssp | 1 # SOF SSP configuration options
|
| /Zephyr-latest/drivers/dai/intel/alh/ |
| D | Kconfig.alh | 1 # SOF ALH configuration options
|
| /Zephyr-latest/boards/nxp/imx93_evk/doc/ |
| D | index.rst | 299 Using the SOF-specific variant
306 in running SOF on this board had to be found. The alternative consists of running SOF
308 assign it to Zephyr with `SOF`_.
348 SOF+Zephyr will run as an inmate, alongside Linux, on core 1 of the board. This means that
382 This board has been designed for SOF so it's only intended to be used with SOF.
384 TODO: document the SOF build process for this board. For now, the support for
385 i.MX93 is still in review and has yet to merged on SOF side.
|
| /Zephyr-latest/boards/amd/acp_6_0_adsp/doc/ |
| D | index.rst | 8 the SOF based framework.
10 SOF can be built with either Zephyr or Cadence's proprietary
|
| /Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/ |
| D | README.rst | 23 buffer gets out) relative to USB SOF. The relative offset must be reported with
|
| /Zephyr-latest/boards/intel/adsp/doc/ |
| D | intel_adsp_generic.rst | 25 (`SOF`_) project. SOF can be built with either Zephyr or Cadence's proprietary
50 Note that if you plan to use SOF on your board, you will need to build and
51 install the modified Linux SOF kernel instead of the default kernel. It is
52 recommended you follow the `SOF instructions`_ to build and run SOF on Zephyr.
61 you will also need to set up the SOF rimage signing tool and key.
|
| D | chromebooks_adsp.rst | 6 The Audio DSP on Intel Chromebooks is configured to use the SOF
9 SOF is one), including the Zephyr samples and test suite.
381 the key in use for the Tiger Lake DSP is the "3k" key from SOF, not
396 console output (in the SOF shared memory trace buffer) can be read by
|
| /Zephyr-latest/drivers/dai/intel/dmic/ |
| D | Kconfig.dmic | 1 # SOF DMIC configuration options
|
| /Zephyr-latest/boards/mediatek/ |
| D | index.rst | 32 DRAM area, a convention it inherits from SOF (these devices have
102 are maintained by the SOF project, however, and building a toolchain
|
| /Zephyr-latest/soc/intel/intel_adsp/cavs/include/ |
| D | xtensa-cavs-linker.ld | 462 * emitted by SOF and inspected by the kernel driver. It doesn't
|
| /Zephyr-latest/soc/intel/intel_adsp/ace/ |
| D | ace-link.ld | 581 * emitted by SOF and inspected by the kernel driver. It doesn't
|
12
