^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 1) ==============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 2) DMA Test Guide
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 3) ==============
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 4)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 5) Andy Shevchenko <andriy.shevchenko@linux.intel.com>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 6)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 7) This small document introduces how to test DMA drivers using dmatest module.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 8)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 9) .. note::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10) The test suite works only on the channels that have at least one
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) capability of the following: DMA_MEMCPY (memory-to-memory), DMA_MEMSET
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) (const-to-memory or memory-to-memory, when emulated), DMA_XOR, DMA_PQ.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14) .. note::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15) In case of any related questions use the official mailing list
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16) dmaengine@vger.kernel.org.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) Part 1 - How to build the test module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19) =====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21) The menuconfig contains an option that could be found by following path:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) Device Drivers -> DMA Engine support -> DMA Test client
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25) In the configuration file the option called CONFIG_DMATEST. The dmatest could
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26) be built as module or inside kernel. Let's consider those cases.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) Part 2 - When dmatest is built as a module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29) ==========================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31) Example of usage::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33) % modprobe dmatest timeout=2000 iterations=1 channel=dma0chan0 run=1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35) ...or::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) % modprobe dmatest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) % echo 2000 > /sys/module/dmatest/parameters/timeout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) % echo 1 > /sys/module/dmatest/parameters/iterations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) % echo dma0chan0 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) % echo 1 > /sys/module/dmatest/parameters/run
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) ...or on the kernel command line::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45) dmatest.timeout=2000 dmatest.iterations=1 dmatest.channel=dma0chan0 dmatest.run=1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47) Example of multi-channel test usage (new in the 5.0 kernel)::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 49) % modprobe dmatest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 50) % echo 2000 > /sys/module/dmatest/parameters/timeout
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 51) % echo 1 > /sys/module/dmatest/parameters/iterations
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 52) % echo dma0chan0 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 53) % echo dma0chan1 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 54) % echo dma0chan2 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 55) % echo 1 > /sys/module/dmatest/parameters/run
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 56)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 57) .. note::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 58) For all tests, starting in the 5.0 kernel, either single- or multi-channel,
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 59) the channel parameter(s) must be set after all other parameters. It is at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 60) that time that the existing parameter values are acquired for use by the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 61) thread(s). All other parameters are shared. Therefore, if changes are made
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 62) to any of the other parameters, and an additional channel specified, the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 63) (shared) parameters used for all threads will use the new values.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 64) After the channels are specified, each thread is set as pending. All threads
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 65) begin execution when the run parameter is set to 1.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 66)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 67) .. hint::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 68) A list of available channels can be found by running the following command::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 69)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 70) % ls -1 /sys/class/dma/
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 71)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 72) Once started a message like " dmatest: Added 1 threads using dma0chan0" is
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 73) emitted. A thread for that specific channel is created and is now pending, the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 74) pending thread is started once run is to 1.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 75)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 76) Note that running a new test will not stop any in progress test.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 77)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 78) The following command returns the state of the test. ::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 79)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 80) % cat /sys/module/dmatest/parameters/run
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 81)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 82) To wait for test completion userpace can poll 'run' until it is false, or use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 83) the wait parameter. Specifying 'wait=1' when loading the module causes module
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 84) initialization to pause until a test run has completed, while reading
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 85) /sys/module/dmatest/parameters/wait waits for any running test to complete
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 86) before returning. For example, the following scripts wait for 42 tests
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 87) to complete before exiting. Note that if 'iterations' is set to 'infinite' then
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 88) waiting is disabled.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 89)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 90) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 91)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 92) % modprobe dmatest run=1 iterations=42 wait=1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 93) % modprobe -r dmatest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 94)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 95) ...or::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 96)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 97) % modprobe dmatest run=1 iterations=42
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 98) % cat /sys/module/dmatest/parameters/wait
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 99) % modprobe -r dmatest
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 100)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 101) Part 3 - When built-in in the kernel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 102) ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 103)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 104) The module parameters that is supplied to the kernel command line will be used
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 105) for the first performed test. After user gets a control, the test could be
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 106) re-run with the same or different parameters. For the details see the above
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 107) section `Part 2 - When dmatest is built as a module`_.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 108)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 109) In both cases the module parameters are used as the actual values for the test
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 110) case. You always could check them at run-time by running ::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 111)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 112) % grep -H . /sys/module/dmatest/parameters/*
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 113)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 114) Part 4 - Gathering the test results
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 115) ===================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 116)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 117) Test results are printed to the kernel log buffer with the format::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 118)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 119) "dmatest: result <channel>: <test id>: '<error msg>' with src_off=<val> dst_off=<val> len=<val> (<err code>)"
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 120)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 121) Example of output::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 122)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 123) % dmesg | tail -n 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 124) dmatest: result dma0chan0-copy0: #1: No errors with src_off=0x7bf dst_off=0x8ad len=0x3fea (0)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 125)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 126) The message format is unified across the different types of errors. A
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 127) number in the parentheses represents additional information, e.g. error
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 128) code, error counter, or status. A test thread also emits a summary line at
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 129) completion listing the number of tests executed, number that failed, and a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 130) result code.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 131)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 132) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 133)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 134) % dmesg | tail -n 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 135) dmatest: dma0chan0-copy0: summary 1 test, 0 failures 1000 iops 100000 KB/s (0)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 136)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 137) The details of a data miscompare error are also emitted, but do not follow the
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 138) above format.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 139)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 140) Part 5 - Handling channel allocation
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 141) ====================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 142)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 143) Allocating Channels
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 144) -------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 145)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 146) Channels do not need to be configured prior to starting a test run. Attempting
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 147) to run the test without configuring the channels will result in testing any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 148) channels that are available.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 149)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 150) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 151)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 152) % echo 1 > /sys/module/dmatest/parameters/run
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 153) dmatest: No channels configured, continue with any
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 154)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 155) Channels are registered using the "channel" parameter. Channels can be requested by their
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 156) name, once requested, the channel is registered and a pending thread is added to the test list.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 157)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 158) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 159)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 160) % echo dma0chan2 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 161) dmatest: Added 1 threads using dma0chan2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 162)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 163) More channels can be added by repeating the example above.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 164) Reading back the channel parameter will return the name of last channel that was added successfully.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 165)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 166) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 167)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 168) % echo dma0chan1 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 169) dmatest: Added 1 threads using dma0chan1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 170) % echo dma0chan2 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 171) dmatest: Added 1 threads using dma0chan2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 172) % cat /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 173) dma0chan2
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 174)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 175) Another method of requesting channels is to request a channel with an empty string, Doing so
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 176) will request all channels available to be tested:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 177)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 178) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 179)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 180) % echo "" > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 181) dmatest: Added 1 threads using dma0chan0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 182) dmatest: Added 1 threads using dma0chan3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 183) dmatest: Added 1 threads using dma0chan4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 184) dmatest: Added 1 threads using dma0chan5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 185) dmatest: Added 1 threads using dma0chan6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 186) dmatest: Added 1 threads using dma0chan7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 187) dmatest: Added 1 threads using dma0chan8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 188)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 189) At any point during the test configuration, reading the "test_list" parameter will
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 190) print the list of currently pending tests.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 191)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 192) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 193)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 194) % cat /sys/module/dmatest/parameters/test_list
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 195) dmatest: 1 threads using dma0chan0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 196) dmatest: 1 threads using dma0chan3
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 197) dmatest: 1 threads using dma0chan4
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 198) dmatest: 1 threads using dma0chan5
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 199) dmatest: 1 threads using dma0chan6
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 200) dmatest: 1 threads using dma0chan7
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 201) dmatest: 1 threads using dma0chan8
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 202)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 203) Note: Channels will have to be configured for each test run as channel configurations do not
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 204) carry across to the next test run.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 205)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 206) Releasing Channels
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 207) -------------------
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 208)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 209) Channels can be freed by setting run to 0.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 210)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 211) Example::
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 212)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 213) % echo dma0chan1 > /sys/module/dmatest/parameters/channel
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 214) dmatest: Added 1 threads using dma0chan1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 215) % cat /sys/class/dma/dma0chan1/in_use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 216) 1
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 217) % echo 0 > /sys/module/dmatest/parameters/run
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 218) % cat /sys/class/dma/dma0chan1/in_use
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 219) 0
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 220)
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 221) Channels allocated by previous test runs are automatically freed when a new
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 222) channel is requested after completing a successful test run.
Orange Pi5 kernel
Deprecated Linux kernel 5.10.110 for OrangePi 5/5B/5+ boards
3 Commits
0 Branches
0 Tags