Home
last modified time | relevance | path

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

12345

/Zephyr-latest/samples/subsys/usb/uac2_implicit_feedback/src/
Dfeedback.h12 /* Nominal number of samples received on each SOF. This sample is currently
22 /* Return offset between I2S block start and USB SOF in samples.
24 * Positive offset means that I2S block started at least 1 sample after SOF and
27 * Negative offset means that I2S block started at least 1 sample before SOF and
30 * Offset 0 means that I2S block started within 1 sample around SOF. This is the
Dfeedback_nrf53.c26 /* While it might be possible to determine I2S FRAMESTART to USB SOF offset
33 * Use timer clock (independent from both Audio clock and USB host SOF clock)
35 * regulator cares only about error (SOF offset is both error and regulator
37 * SOF offset is around 0 when regulated and therefore the relative clock
68 /* Subscribe TIMER CAPTURE task to USBD SOF event */ in feedback_init()
167 /* I2S data was supposed to go out at SOF, but it is inevitably in feedback_start()
169 * SOF offset value in a way that ensures that values past "half in feedback_start()
Dmain.c37 * SOF/I2S offset errors), but add 2 additional buffers to prevent out of memory
156 * we can control the SOF to I2S offset is by varying the number in uac2_data_recv_cb()
206 /* Determine next number of samples to send, called at most once every SOF */
219 /* I2S buffer starts at least 1 sample before SOF, send nominal in next_mic_num_samples()
227 /* I2S buffer starts at least 1 sample after SOF, send nominal in next_mic_num_samples()
443 /* If we didn't receive data since last SOF but either terminal is in uac2_sof()
449 /* No data received since last SOF but we have to keep going */ in uac2_sof()
467 * during SOF n should be transmitted on I2S during SOF n+3. This in uac2_sof()
472 * USB SOF n in uac2_sof()
474 * USB SOF n+1 in uac2_sof()
[all …]
/Zephyr-latest/soc/mediatek/mt8xxx/
DCMakeLists.txt17 # 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
/Zephyr-latest/modules/
DKconfig.sof7 config SOF config
8 bool "Sound Open Firmware (SOF)"
11 Build Sound Open Firmware (SOF) support.
/Zephyr-latest/dts/bindings/clock/
Dst,stm32-hsi48-clock.yaml11 crs-usb-sof:
14 Clock Recovery System using USB SOF packet reception
16 the USB SOF packet reception as a reference.
/Zephyr-latest/soc/altr/zephyr_nios2f/cpu/
DREADME13 To flash this CPU, use the nios2-configure-sof tool:
15 $ nios2-configure-sof ghrd_10m50da.sof
/Zephyr-latest/drivers/dma/
DKconfig.nxp_sof_host_dma5 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/dts/bindings/dma/
Dnxp,sof-host-dma.yaml4 description: NXP SOF host DMA node
6 compatible: "nxp,sof-host-dma"
/Zephyr-latest/boards/altr/max10/
Dboard.cmake3 board_runner_args(nios2 "--cpu-sof=${ZEPHYR_BASE}/soc/nios2/nios2f-zephyr/cpu/ghrd_10m50da.sof")
/Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/src/
Dfeedback_nrf53.c37 * we use such estimate on PI controller updated on every SOF.
39 * While it might be possible to determine I2S FRAMESTART to USB SOF offset
166 /* Subscribe TIMER CAPTURE task to USBD SOF event */ in feedback_init()
212 * USB host SOF clock) to fake sample clock shifted by P values. in update_sof_offset()
214 * (SOF offset is both error and regulator input) and achieves in update_sof_offset()
215 * its goal by adjusting feedback value. SOF offset is around 0 in update_sof_offset()
269 /* SOF offset is measured in pow(2, -FEEDBACK_P) samples, i.e. when in pi_update()
278 * USB SOF and therefore Set Point is 0. in pi_update()
285 * SOF n appears on I2S during SOF n+3, the Ziegler Nichols Ultimate in pi_update()
286 * Gain is around 1.15 and the oscillation period is around 90 SOF. in pi_update()
[all …]
Dmain.c34 * buffer, 3rd acquired by USB stack to receive data to, and 2 to handle SOF/I2S
162 * there are nominally 48 samples every SOF. The corresponding value is thus
165 * sink is shorter than 1 ms according to USB Host 500 ppm SOF timer), then
183 * 6 samples every SOF (microframe). The nominal value is the average number of
216 /* We want to maintain 3 SOFs delay, i.e. samples received during SOF n in uac2_sof()
217 * should be on I2S during SOF n+3. This provides enough wiggle room in uac2_sof()
222 * USB SOF n in uac2_sof()
224 * USB SOF n+1 in uac2_sof()
227 * to I2S buffer before SOF n+2; i2s_blocks_written = 1 in uac2_sof()
229 * USB SOF n+2 in uac2_sof()
[all …]
/Zephyr-latest/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
/Zephyr-latest/soc/intel/intel_adsp/
DKconfig39 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
DKconfig.defconfig10 # A workaround for HWMv2 to recover SOF arch/xtensa defaults overridden by arch/host.
11 if SOF
/Zephyr-latest/samples/subsys/usb/uac2_explicit_feedback/
DREADME.rst22 USB host. Because the sample clock is independent from USB SOF it is inevitable
39 The nRF5340 is capable of counting both edges of I2S LRCLK relative to USB SOF
42 provide relative timing information between I2S FRAMESTART and USB SOF.
45 to USB SOF offset) has been tested on :ref:`nrf5340dk_nrf5340`.
/Zephyr-latest/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-latest/boards/intel/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-latest/boards/intel/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-latest/scripts/west_commands/runners/
Dnios2.py40 parser.add_argument('--cpu-sof', required=True,
41 help='path to the CPU .sof data')
62 raise ValueError('Cannot flash; --cpu-sof not given.')
67 '--sof', self.cpu_sof,
/Zephyr-latest/submanifests/
Doptional.yaml37 - name: sof
39 path: modules/audio/sof
/Zephyr-latest/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-latest/boards/nxp/imx8ulp_evk/
Dimx8ulp_evk_mimx8ud7_adsp.yaml10 - sof
/Zephyr-latest/dts/bindings/dai/
Dnxp,dai-esai.yaml17 moment, this is only used by SOF to fetch the "struct device"
18 associated with the DAI whose index Linux passes to SOF
45 because some applications (e.g: SOF) use this value directly as the
/Zephyr-latest/tests/boards/mtk_adsp/src/
Dmain.c71 /* Test in/out interrupts from the host. This relies on a SOF driver
76 * Note that there's a catch: on older kernels, SOF's "reply" comes
94 printk("Waiting for reply from SOF driver, be patient: long timeout...\n"); in ZTEST()

12345