Commit 4a6fd066 authored by Rob Clark's avatar Rob Clark
Browse files

Merge remote-tracking branch 'drm-misc/drm-misc-next' into msm-next



Merging to pick up commit 785324db ("drm/msm/dp: migrate the
ycbcr_420_allowed to drm_bridge").

Signed-off-by: default avatarRob Clark <robdclark@chromium.org>
parents d6d1ad32 904bc547
Loading
Loading
Loading
Loading
+10 −0
Original line number Diff line number Diff line
What:		/sys/bus/platform/drivers/panthor/.../profiling
Date:		September 2024
KernelVersion:	6.11.0
Contact:	Adrian Larumbe <adrian.larumbe@collabora.com>
Description:
		Bitmask to enable drm fdinfo's job profiling measurements.
		Valid values are:
		0: Don't enable fdinfo job profiling sources.
		1: Enable GPU cycle measurements for running jobs.
		2: Enable GPU timestamp sampling for running jobs.
+14 −0
Original line number Diff line number Diff line
.. SPDX-License-Identifier: GPL-2.0-only

===============================
 Qualcomm Cloud AI 80 (AIC080)
===============================

Overview
========

The Qualcomm Cloud AI 80/AIC080 family of products are a derivative of AIC100.
The number of NSPs and clock rates are reduced to fit within resource
constrained solutions. The PCIe Product ID is 0xa080.

As a derivative product, all AIC100 documentation applies.
+2 −0
Original line number Diff line number Diff line
@@ -229,6 +229,8 @@ of the defined channels, and their uses.
| _PERIODIC      |         |          | timestamps in the device side logs with|
|                |         |          | the host time source.                  |
+----------------+---------+----------+----------------------------------------+
| IPCR           | 24 & 25 | AMSS     | AF_QIPCRTR clients and servers.        |
+----------------+---------+----------+----------------------------------------+

DMA Bridge
==========
+1 −0
Original line number Diff line number Diff line
@@ -10,4 +10,5 @@ accelerator cards.
.. toctree::

   qaic
   aic080
   aic100
+1 −1
Original line number Diff line number Diff line
@@ -12,7 +12,7 @@ ones.

Of course this is a bad idea to rely on the alignment trap to perform
unaligned memory access in general.  If those access are predictable, you
are better to use the macros provided by include/asm/unaligned.h.  The
are better to use the macros provided by include/linux/unaligned.h.  The
alignment trap can fixup misaligned access for the exception cases, but at
a high performance cost.  It better be rare.

Loading