- Sound-open-firmware - mailman.alsa-project.org

[Sound-open-firmware] host_dma_cb() error: Wrong callback type = 3
by Paul Olaru 06 Aug '19

06 Aug '19

Hello, I'm currently implementing the DMA driver for the IMX platform (Dummy DMA). With this partial implementation I have noticed the error message in the title. The thing is, within host.c I see that dma_set_cb is called with the type as DMA_CB_TYPE_IRQ | DMA_CB_TYPE_COPY (which is 3), yet in host_dma_cb itself I only see the cases for these bits individually, and it falls into the default case. I've also noticed this in the dai.c file.

3 6

[Sound-open-firmware] Signed firmware availability for kbl/cnl
by Daniel Drake 05 Aug '19

05 Aug '19

Hi, Thanks for all the hard work on SOF! We are hoping to try it on consumer products in order to support the internal digital mic, which is not supported when running in HDA mode. Specifically Acer AIO Aspire Z24-890 (Intel i3-8100T) and ASUS MJ401TA (Intel m3-8100Y) are two models we have in hand right now. I gather from previous discussions that even though the sof source code is public, the resultant binary files need to be signed by Intel before they can be used. Is that correct? If so, when will these be made available? The files that Linux 5.2 is looking for here are: sof-cnl.ri sof-cnl-nocodec.tplg sof-kbl.ri sof-kbl-nocodec.tplg Thanks

6 28

Re: [Sound-open-firmware] [GIT PULL] SOF v1.3 firmware binaries
by Liam Girdwood 31 Jul '19

31 Jul '19

On Tue, 2019-07-30 at 17:19 -0400, Josh Boyer wrote: > > I don't understand what you're suggesting nor how it would work > > with the > > way the kernel deals with directories. I tried to explain that we > > need > > an intel/sof-production and intel/sof directories, each with > > generic > > names that are symlinked to another location. This helps if you > > want to > > build quirks that select one or the other capabilities by just > > changing > > the firmware directory prefix. Pointers below. > > > > https://github.com/thesofproject/linux/blob/9d7da69a1e85db2cdbbaae78dd7eda4… > > > > https://github.com/thesofproject/linux/blob/9d7da69a1e85db2cdbbaae78dd7eda4… > > > > https://github.com/thesofproject/linux/blob/9d7da69a1e85db2cdbbaae78dd7eda4… So the commit did support this, but it would put all "production" signed binaries at the intel/sof/ level via soft links (to be automatically loaded by the driver as the default). A subsequent commit would have added the community signed images. I planned to link community signed binaries at the intel/sof/community level since most users would use the production signed images by default (and would not need to use a module param to select). My assumption was that machines using community signed by default would have this in their default_fw_path ? > > > > I guess we need to talk off-line since we are evidently not on the > > same > > page or something is missing for people to use this pull request. > > I suggest you guys do that. At the moment, I'm not pulling anything > related to this until it has a signoff from both you and Liam in the > commit logs at a minimum. Yep, no problem - Pierre and I will refine and resend shortly. I also need to remove links for aliases. Thanks Liam

1 0

[Sound-open-firmware] Audio miniconf + sof meeting at ELCE, Lyon
by Daniel Baluta 31 Jul '19

31 Jul '19

Hi Mark, Pierre, Liam, Ranjani, Will you be in Lyon for ELCE this year? I'm very interested in participating to an (eventual) audio miniconf meeting. Maybe we can also do a separate SOF meeting if they are enough people interested.

2 1

[Sound-open-firmware] [GIT PULL] SOF v1.3 firmware binaries
by Liam Girdwood 31 Jul '19

31 Jul '19

The following changes since commit dff98c6c57383fe343407bcb7b6e775e0b87274f: Merge branch 'master' of git://github.com/skeggsb/linux-firmware (2019-07-26 07:32:37 -0400) are available in the Git repository at: https://github.com/thesofproject/linux-firmware.git sof-v1.3 for you to fetch changes up to cde3a116cea96976125b9215b303edfda85c9b54: sof: Add Intel SOF V1.3 release firmware binaries. (2019-07-30 16:06:41 +0100) ---------------------------------------------------------------- Liam Girdwood (1): sof: Add Intel SOF V1.3 release firmware binaries. LICENCE.sof | 1090 ++++++++++++++++++++++++++ WHENCE | 33 + intel/sof/apl/intel/sof-apl-v1.3.ri | Bin 0 -> 270336 bytes intel/sof/bdw/sof-bdw-v1.3.ri | Bin 0 -> 100144 bytes intel/sof/byt/sof-byt-v1.3.ri | Bin 0 -> 89668 bytes intel/sof/cht/sof-cht-v1.3.ri | Bin 0 -> 90484 bytes intel/sof/cnl/intel/sof-cnl-v1.3-6cc8da10.ri | Bin 0 -> 274432 bytes intel/sof/icl/intel/sof-icl-v1.3.ri | Bin 0 -> 278528 bytes intel/sof/sof-apl.ri | 1 + intel/sof/sof-bdw.ri | 1 + intel/sof/sof-byt.ri | 1 + intel/sof/sof-cht.ri | 1 + intel/sof/sof-cml.ri | 1 + intel/sof/sof-cnl.ri | 1 + intel/sof/sof-glk.ri | 1 + intel/sof/sof-icl.ri | 1 + intel/sof/sof-whl.ri | 1 + 17 files changed, 1132 insertions(+) create mode 100644 LICENCE.sof create mode 100644 intel/sof/apl/intel/sof-apl-v1.3.ri create mode 100644 intel/sof/bdw/sof-bdw-v1.3.ri create mode 100644 intel/sof/byt/sof-byt-v1.3.ri create mode 100644 intel/sof/cht/sof-cht-v1.3.ri create mode 100644 intel/sof/cnl/intel/sof-cnl-v1.3-6cc8da10.ri create mode 100644 intel/sof/icl/intel/sof-icl-v1.3.ri create mode 120000 intel/sof/sof-apl.ri create mode 120000 intel/sof/sof-bdw.ri create mode 120000 intel/sof/sof-byt.ri create mode 120000 intel/sof/sof-cht.ri create mode 120000 intel/sof/sof-cml.ri create mode 120000 intel/sof/sof-cnl.ri create mode 120000 intel/sof/sof-glk.ri create mode 120000 intel/sof/sof-icl.ri create mode 120000 intel/sof/sof-whl.ri

2 3

[Sound-open-firmware] Questions about the SOF coredump reader
by Paul Olaru 26 Jul '19

26 Jul '19

I'm trying to diagnose a few issues on the IMX platform and it would be nice if I would be able to interpret panics and exceptions. I have just fixed a minor issue so that the debugfs "exception" entry is correct. I would like to know if the tool in sof/tools/coredumper/sof-coredump-reader.py is usable for interpreting such dumps and how it should be used. Right now, I have inserted a "panic" call in my code (that makes a dump which seems to be in the proper format), but whenever I try to run this tool on that /sys/kernel/debug/sof/exception file it gets exceptions (one about exccause and, if I remove the corresponding code, it messes up the pathname interpretation too, complaining about UTF-8 being invalid - I suspect wrong offsets?). So, how is this tool supposed to be used?

2 2

[Sound-open-firmware] [PATCH 0/3] Add DSP node on i.MX8QXP board
by Daniel Baluta 23 Jul '19

23 Jul '19

i.MX8QXP boards feature an Hifi4 DSP from Tensilica. This patch series adds the DT node. Note that we switched to the new yaml format for bindings documentation. The DSP will run SOF Firmware [1]. Patches adding support for Linux DSP driver are already sent for review to SOF folks [2]. This patch series also contains a patch introducing DT related clocks. The patch was already reviewed here: https://lkml.org/lkml/2019/7/17/975 but I added it in this patch series because it wasn't yet picked by Shawn so patches 2/3 will not compiled without patch 1. [1] https://github.com/thesofproject/sof [2] https://github.com/thesofproject/linux/pull/1048/commits Daniel Baluta (3): clk: imx8: Add DSP related clocks arm64: dts: imx8qxp: Add DSP DT node dt-bindings: dsp: fsl: Add DSP core binding support .../devicetree/bindings/dsp/fsl,dsp.yaml | 87 +++++++++++++++++++ arch/arm64/boot/dts/freescale/imx8qxp-mek.dts | 4 + arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 32 +++++++ drivers/clk/imx/clk-imx8qxp-lpcg.c | 5 ++ include/dt-bindings/clock/imx8-clock.h | 6 +- 5 files changed, 133 insertions(+), 1 deletion(-) create mode 100644 Documentation/devicetree/bindings/dsp/fsl,dsp.yaml -- 2.17.1

6 10

[Sound-open-firmware] Linux build for arm64
by Daniel Baluta 18 Jul '19

18 Jul '19

Hi Liam / Pierre, Could we add a build for arm64 too in CI? With recent patches that add support for i.MX8 SOF Linux driver it would be handy to also have the build for arm64. I can help you with the cross-compilers and build instructions. Currently we are only building for x86_64. https://travis-ci.org/thesofproject/linux/builds/560509972 thanks, Daniel.

2 3

[Sound-open-firmware] New platform bringup docs
by Curtis Malainey 11 Jul '19

11 Jul '19

Hello SOF community, Do we have any documents similar to the new architecture links (https://thesofproject.github.io/latest/architectures/dsp/index.html#adding-…) but more advanced. I was thinking ideally something along the lines of a check/worklist of features to be built for introducing a new platform to SOF. Daniel you have done this, do you have any documents or experiences that we can turn into a doc? Thanks in advance. Curtis

2 2

[Sound-open-firmware] Problems booting byt in qemu
by Dragos Tarcatu 03 Jul '19

03 Jul '19

Hi, I've been trying to put together a qemu test environment for byt but I'm struggling to get the firmware to properly boot up. My setup is as following: - x86 host VM: Linux kernel from topic/sof-dev configured for x86_64_defconfig + sof for Baytrail (acpi) with forced nocodec mode, on top of some Ubuntu root file system - DSP VM: sof firmware from master built for byt according to the sof documentation - qemu from sof-stable - topology: sof-byt-nocodec I'm launching the qemu VMs using: xtensa-host.sh byt -d and x86-host.sh byt <my-ubuntu-image> Shortly after the x86 VM boots up, the DSP VM starts logging a lot of shim.io messages, but the linux driver fails after: [ 3.054963] sof-audio-acpi 80860F28:00: ACPI DSP detected [ 3.054966] sof-audio-acpi 80860F28:00: IOSF_MBI not available, no BYT-CR detection [ 3.054967] sof-audio-acpi 80860F28:00: Force to use nocodec mode [ 3.054971] sof-audio-acpi 80860F28:00: LPE PHY base at 0xf1400000 size 0x200000 [ 3.054981] sof-audio-acpi 80860F28:00: LPE VADDR 000000009309825a [ 3.054982] sof-audio-acpi 80860F28:00: IMR not set by BIOS. Ignoring [ 3.054984] sof-audio-acpi 80860F28:00: using IRQ 11 [ 3.058424] sof-audio-acpi 80860F28:00: loading firmware [ 3.070402] sof-audio-acpi 80860F28:00: header size=0x15e60 modules=0x1 abi=0x1 size=16 [ 3.070504] sof-audio-acpi 80860F28:00: new module size 0x15e54 blocks 0x11 type 0x0 [ 3.070506] sof-audio-acpi 80860F28:00: block 0 type 0x1 size 0xf0 ==> offset 0xc0000 [ 3.070524] sof-audio-acpi 80860F28:00: block 1 type 0x1 size 0x16c ==> offset 0xc0400 [ 3.070525] sof-audio-acpi 80860F28:00: block 2 type 0x1 size 0x8 ==> offset 0xc057c [ 3.070527] sof-audio-acpi 80860F28:00: block 3 type 0x1 size 0x8 ==> offset 0xc059c [ 3.070528] sof-audio-acpi 80860F28:00: block 4 type 0x1 size 0x8 ==> offset 0xc05bc [ 3.070529] sof-audio-acpi 80860F28:00: block 5 type 0x1 size 0x8 ==> offset 0xc05dc [ 3.070530] sof-audio-acpi 80860F28:00: block 6 type 0x1 size 0x8 ==> offset 0xc05fc [ 3.070532] sof-audio-acpi 80860F28:00: block 7 type 0x1 size 0x4 ==> offset 0xc061c [ 3.070533] sof-audio-acpi 80860F28:00: block 8 type 0x1 size 0x8 ==> offset 0xc063c [ 3.070534] sof-audio-acpi 80860F28:00: block 9 type 0x1 size 0x4 ==> offset 0xc0658 [ 3.070536] sof-audio-acpi 80860F28:00: block 10 type 0x1 size 0x18 ==> offset 0xc065c [ 3.070537] sof-audio-acpi 80860F28:00: block 11 type 0x1 size 0x8 ==> offset 0xc067c [ 3.070539] sof-audio-acpi 80860F28:00: block 12 type 0x1 size 0x12660 ==> offset 0xc06c0 [ 3.070599] sof-audio-acpi 80860F28:00: block 13 type 0x2 size 0x21e8 ==> offset 0x100008 [ 3.070611] sof-audio-acpi 80860F28:00: block 14 type 0x2 size 0x28 ==> offset 0x1021f0 [ 3.070613] sof-audio-acpi 80860F28:00: block 15 type 0x2 size 0x11f8 ==> offset 0x102218 [ 3.070617] sof-audio-acpi 80860F28:00: block 16 type 0x2 size 0x6c ==> offset 0x103a98 [ 3.070623] sof-audio-acpi 80860F28:00: booting DSP firmware [ 3.172697] sof-audio-acpi 80860F28:00: error: firmware boot failure [ 3.176674] sof-audio-acpi 80860F28:00: error: unexpected fault 0x70028800 trace 0x00000000 [ 3.177125] sof-audio-acpi 80860F28:00: error: failed to boot DSP firmware -5 [ 3.181048] sof-audio-acpi 80860F28:00: error: failed to probe DSP hardware! [ 3.181477] sof-audio-acpi: probe of 80860F28:00 failed with error -5 Any idea what may be wrong? Thanks, Dragoș

4 9