summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/failed-syscalls-by-pid.py
diff options
context:
space:
mode:
authorBhupesh Sharma <bhupesh.sharma@linaro.org>2021-06-27 14:46:14 +0300
committerBjorn Andersson <bjorn.andersson@linaro.org>2021-07-20 16:58:12 +0300
commit2aa2b50de12d96eaf282b886330afe98c389e1e2 (patch)
tree31e9d373a7376cae9825bc4508e7b3592c4c503b /tools/perf/scripts/python/failed-syscalls-by-pid.py
parent98aee1e3cdcd74debc093cfc9297287063e88a0f (diff)
downloadlinux-2aa2b50de12d96eaf282b886330afe98c389e1e2.tar.xz
arm64: dts: qcom: Use correct naming for dwc3 usb nodes in dts files
The dwc3 usb nodes in several arm64 qcom dts are currently named differently, somewhere as 'usb@<addr>' and somewhere as 'dwc3@<addr>', leading to some confusion when one sees the entries in sysfs or dmesg: [ 1.943482] dwc3 a600000.usb: Adding to iommu group 1 [ 2.266127] dwc3 a800000.dwc3: Adding to iommu group 2 Name the usb nodes as 'usb@<addr>' for consistency, which is the correct convention as per the 'snps,dwc3' dt-binding as well (see [1]). [1]. Documentation/devicetree/bindings/usb/snps,dwc3.yaml Cc: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by: Bhupesh Sharma <bhupesh.sharma@linaro.org> Link: https://lore.kernel.org/r/20210627114616.717101-2-bhupesh.sharma@linaro.org [bjorn: Extended to also fix ipq6018] Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions