summaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorJon Hunter <jonathanh@nvidia.com>2022-10-26 18:56:33 +0300
committerMark Brown <broonie@kernel.org>2022-10-28 19:27:44 +0300
commitae4b3c1252f0fd0951d2f072a02ba46cac8d6c92 (patch)
tree042a88df97a61a1c8b3b513c2192381c897fe2c7 /tools/perf/util/scripting-engines/trace-event-python.c
parentc1de355e04e6ae8da21cb6bfbd5bbfd8deee0fe5 (diff)
downloadlinux-ae4b3c1252f0fd0951d2f072a02ba46cac8d6c92.tar.xz
spi: tegra210-quad: Don't initialise DMA if not supported
The following error messages are observed on boot for Tegra234 ... ERR KERN tegra-qspi 3270000.spi: cannot use DMA: -19 ERR KERN tegra-qspi 3270000.spi: falling back to PIO Tegra234 does not support DMA for the QSPI and so initialising the DMA is expected to fail. The above error messages are misleading for devices that don't support DMA and so fix this by skipping the DMA initialisation for devices that don't support DMA. Signed-off-by: Jon Hunter <jonathanh@nvidia.com> Acked-by: Thierry Reding <treding@nvidia.com> Link: https://lore.kernel.org/r/20221026155633.141792-1-jonathanh@nvidia.com Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions