recipes-kernel: Fix warning of license

diff options

author	Yannick Gicquel <yannick.gicquel@iot.bzh>	2016-09-07 15:00:18 +0200
committer	Yannick Gicquel <yannick.gicquel@iot.bzh>	2016-11-02 15:41:22 +0100
commit	7086d09a84a2c522a256759321c820469fe2b896 (patch)
tree	1c6df23e4b277b2e0d4b4fd33f23383955088cc3 /meta-rcar-gen2/recipes-kernel/ssp-module
parent	b0ca2942f2e7abefe45745608400c1ddb7be1a97 (diff)

This is report 7ffdb1f20d8 upstream patch to avoid QA warning while do_rootfs tasks occured. Change-Id: Ie2661c7e85dc50ee6a736fa4d5ccc8b1373aa5a1 Signed-off-by: Yannick Gicquel <yannick.gicquel@iot.bzh>

Diffstat (limited to 'meta-rcar-gen2/recipes-kernel/ssp-module')

-rw-r--r--

meta-rcar-gen2/recipes-kernel/ssp-module/ssp-kernel-module.bb

1 files changed, 1 insertions, 1 deletions

Using AVIRT =================================== ## Introduction ## Table of Contents 1. [Load/Unload AVIRT](#un-load-avirt) 2. [Configuring AVIRT](#configuring-avirt) 3. [Checking AVIRT](#checking-avirt) <a name="un-load-avirt"/> ## 1. Loading and Unloading AVIRT ### Load Out of Tree As root, load the required `avirt_core.ko` and subsequent audio path. As an example, the Dummy Audiopath is being loaded here. ```sh insmod snd-avirt-core.ko insmod dummy/snd-avirt-ap-dummy.ko insmod loopback/snd-avirt-ap-loopback.ko ``` ### Note: The loading and unloading of drivers can be performed using the helper scripts. To run, we must load the kernel modules using the `scripts/load.sh` script: ```sh $ ./scripts/load.sh ``` To unload the drivers use: ```sh $ ./scripts/unload.sh ``` ### Load In Tree #### Note: Either build the module in tree, or you can copy the modules manually and then run `depmod` to generate dependencies. For example, in AGL: ```sh mkdir -p /lib/modules/$(uname -r)/extra cp snd-avirt-core.ko snd-avirt-ap-dummy.ko snd-avirt-ap-loopback.ko /lib/modules/$(uname -r)/extra depmod ``` Once the modules are in place, we can load the modules using: ```sh modprobe snd-avirt-core modprobe snd-avirt-ap-dummy modprobe snd-avirt-ap-loopback ``` <a name="configure-avirt" /> ## 2. Configuring AVIRT AVIRT is configured using configfs. ### Note: A sample script for the following is supplied inside the `scripts` folder. First, verify the kernel supports the use of configfs. ```sh fgrep configfs /proc/filesystems ``` The expected output is: ``` nodev configfs ``` Once confirmed, we can mount the `configfs` filesystem at the conventional point: ```sh # Check configfs is mounted on the system mkdir -p /config mount -t configfs none /config ``` Finally, we can configure AVIRT, for example: ```sh # Set up each of the cards channels mkdir /config/snd-avirt/streams/playback_media echo "2">/config/snd-avirt/streams/playback_media/channels echo "ap_dummy">/config/snd-avirt/streams/playback_media/map mkdir /config/snd-avirt/streams/playback_navigation echo "1">/config/snd-avirt/streams/playback_navigation/channels echo "ap_dummy">/config/snd-avirt/streams/playback_navigation/map mkdir /config/snd-avirt/streams/playback_emergency echo "1">/config/snd-avirt/streams/playback_emergency/channels echo "ap_dummy">/config/snd-avirt/streams/playback_emergency/map mkdir /config/snd-avirt/streams/capture_voice echo "1">/config/snd-avirt/streams/capture_voice/channels echo "ap_dummy">/config/snd-avirt/streams/capture_voice/map # Finally, seal the card, and initiate configuration echo "1">/config/snd-avirt/streams/sealed ``` Alternatively, the test script at `scripts/test_configfs.sh` can be used. The user-space library, [libavirt](https://github.com/fiberdyne/libavirt) can be used to interact with the configfs interface. Please refer to the README in libavirt for further details. <a name="checking-avirt" /> ## 3. Checking AVIRT Loaded Correctly We can see the newly created streams by using the `aplay` utility. For example, the device list might look a little like this: ```sh aplay -l ... card 2: avirt [avirt], device 0: multimedia [multimedia] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: avirt [avirt], device 1: navigation [navigation] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: avirt [avirt], device 2: emergency [emergency] Subdevices: 1/1 Subdevice #0: subdevice #0 ... ```


context:
space:
mode: