aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/intel-pt-events.py
diff options
context:
space:
mode:
authorMaxime Ripard <[email protected]>2022-10-26 15:17:39 +0200
committerFlorian Fainelli <[email protected]>2022-11-10 10:15:15 -0800
commit27ab05e1b7e5c5ec9b4f658e1b2464c0908298a6 (patch)
tree6b547c1f96dd1a3c89aebcd52aeef78ecc3a84d9 /tools/perf/scripts/python/intel-pt-events.py
parent9d9491b6411903703a9e20d9e5c1a74861a8fbb2 (diff)
ARM: dts: bcm2835-rpi: Use firmware clocks for display
We've experienced a number of issues around the cohabitation between the "real" clock driver in Linux and the one backed by the firmware. One solution around this is to follow what the RaspberryPi foundation in its downstream clock, which is also what we've been doing on the RaspberryPi4: to use the clocks exposed by the firmware. Link: https://lore.kernel.org/linux-clk/20221021140505.kjmw5x4s6qhnrfif@houat/ Signed-off-by: Maxime Ripard <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Florian Fainelli <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/intel-pt-events.py')
0 files changed, 0 insertions, 0 deletions