Home
last modified time | relevance | path

Searched full:sof (Results 1 – 25 of 75) sorted by relevance

123

/Zephyr-Core-3.5.0/modules/
DKconfig.sof4 config SOF config
5 bool "Sound Open Firmware (SOF)"
7 Build Sound Open Firmware (SOF) support.
/Zephyr-Core-3.5.0/soc/nios2/nios2f-zephyr/cpu/
DREADME13 To flash this CPU, use the nios2-configure-sof tool:
15 $ nios2-configure-sof ghrd_10m50da.sof
/Zephyr-Core-3.5.0/boards/nios2/altera_max10/
Dboard.cmake3 board_runner_args(nios2 "--cpu-sof=${ZEPHYR_BASE}/soc/nios2/nios2f-zephyr/cpu/ghrd_10m50da.sof")
/Zephyr-Core-3.5.0/drivers/ipm/
DKconfig.intel_adsp28 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
Dipm_cavs_host.c18 * current SOF ipc3/4 layout, which means that:
40 * whether this is required, and the SOF code that will be using this
70 /* Protocol variant (used by SOF "ipc4"): store the first word in send()
86 * interrupt context, and it's not clear to me that SOF would in send()
184 /* Initialize hardware SRAM window. SOF will give the host 8k in init()
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/
DKconfig26 default $(dt_compat_enabled,$(DT_COMPAT_INTEL_ADSP_HOST_IPC)) if !SOF
27 default $(dt_compat_enabled,$(DT_COMPAT_INTEL_ADSP_IDC)) if !SOF
30 Currently SOF has its own driver for this hardware.
76 addresses here. The SOF application also makes direct use
/Zephyr-Core-3.5.0/boards/arm64/mimx93_evk/doc/
Dindex.rst129 Using the SOF-specific variant
136 in running SOF on this board had to be found. The alternative consists of running SOF
138 assign it to Zephyr with `SOF`_.
141 https://github.com/thesofproject/sof
178 SOF+Zephyr will run as an inmate, alongside Linux, on core 1 of the board. This means that
206 https://github.com/thesofproject/sof/issues/7192
212 This board has been designed for SOF so it's only intended to be used with SOF.
214 TODO: document the SOF build process for this board. For now, the support for
215 i.MX93 is still in review and has yet to merged on SOF side.
/Zephyr-Core-3.5.0/boards/riscv/niosv_g/doc/
Dindex.rst26 ready_to_test/top.sof file is the prebuilt SRAM Object File for hello world example design system a…
33 …Nios® V/g processor inside the FPGA device, please download the generated .sof file onto the board…
37 quartus_pgm -c 1 -m JTAG -o "p;top.sof@1"
44 top.sof is referring to Nios® V/m processor based system SRAM Object File.
/Zephyr-Core-3.5.0/boards/riscv/niosv_m/doc/
Dindex.rst26 ready_to_test/top.sof file is the prebuilt SRAM Object File for hello world example design system a…
33 …Nios® V/m processor inside the FPGA device, please download the generated .sof file onto the board…
37 quartus_pgm -c 1 -m JTAG -o "p;top.sof@1"
44 top.sof is referring to Nios® V/m processor based system SRAM Object File.
/Zephyr-Core-3.5.0/drivers/timer/
DKconfig.cavs7 # SoF is still referencing this symbol. The reason is the
10 # Once it gets merged, we have to update SoF to use INTEL_ADSP_TIMER
/Zephyr-Core-3.5.0/scripts/west_commands/runners/
Dnios2.py36 parser.add_argument('--cpu-sof', required=True,
37 help='path to the the CPU .sof data')
58 raise ValueError('Cannot flash; --cpu-sof not given.')
63 '--sof', self.cpu_sof,
/Zephyr-Core-3.5.0/submanifests/
Doptional.yaml30 - name: sof
32 path: modules/audio/sof
/Zephyr-Core-3.5.0/boards/xtensa/intel_adsp_cavs25/doc/
Dintel_adsp_generic.rst27 (`SOF`_) project. SOF can be built with either Zephyr or Cadence's proprietary
52 Note that if you plan to use SOF on your board, you will need to build and
53 install the modified Linux SOF kernel instead of the default kernel. It is
54 recommended you follow the `SOF instructions`_ to build and run SOF on Zephyr.
63 you will also need to set up the SOF rimage signing tool and key.
67 cd zephyrproject/modules/audio/sof/
80 The SOF project does not require this manual step because its west manifest
82 matching SOF sources. An indirect Zephyr -> SOF -> rimage dependency chain is
83 unfortunately not appropriate because unlike rimage, SOF is *not* required to
86 Until https://github.com/thesofproject/sof/issues/7270 is implemented,
/Zephyr-Core-3.5.0/scripts/support/
Dquartus-flash.py72 """given an input CPU .sof file and a kernel binary, return a file-like
122 parser.add_argument("-s", "--sof",
123 help=".sof file with Nios II CPU configuration")
133 flash_kernel(args.device, args.sof, args.kernel)
/Zephyr-Core-3.5.0/boards/xtensa/nxp_adsp_imx8/
Dnxp_adsp_imx8.yaml10 - sof
/Zephyr-Core-3.5.0/boards/xtensa/nxp_adsp_imx8x/
Dnxp_adsp_imx8x.yaml10 - sof
/Zephyr-Core-3.5.0/boards/xtensa/nxp_adsp_imx8m/
Dnxp_adsp_imx8m.yaml10 - sof
/Zephyr-Core-3.5.0/boards/arm64/mimx93_evk/
Dmimx93_evk_a55_sof.yaml2 name: NXP i.MX93 Plus EVK A55 for SOF module
Dmimx93_evk_a55_sof.dts35 /* TODO: all of the nodes below are needed by SOF and should
36 * be removed once all drivers used by SOF have been moved
/Zephyr-Core-3.5.0/drivers/dai/intel/hda/
DKconfig.hda1 # SOF HDA configuration options
/Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/common/
Drimage_modules.c9 * SOF with IPC3, but instead are inserted to *MANIFEST* of the final
15 * other used on cAVS 1.8+ platforms. Because SOF with IPC4 requires the
/Zephyr-Core-3.5.0/dts/bindings/can/
Dmicrochip,mcp251xfd.yaml64 sof-on-clko:
67 Output start-of-frame (SOF) signal on the CLKO pin every time
/Zephyr-Core-3.5.0/subsys/logging/backends/
DKconfig.adsp_mtrace10 using the SOF Linux driver mtrace buffer layout.
/Zephyr-Core-3.5.0/drivers/dai/intel/alh/
DKconfig.alh1 # SOF ALH configuration options
/Zephyr-Core-3.5.0/drivers/dai/intel/ssp/
DKconfig.ssp1 # SOF SSP configuration options

123