Am 29.06.22 um 01:35 schrieb Rob Clark:
From: Rob Clark
drive-by cleanup
Signed-off-by: Rob Clark
We should probably completely remove that dependency and rather use
dma_fence_unwrap instead.
But that's probably for another patch Reviewed-by: Christian König
.
Christian.
---
driv
On 5/27/22 01:50, Dmitry Osipenko wrote:
Unlock reservations on dma_resv_reserve_fences() error to fix recursive
locking of the reservations when this error happens.
Fixes:
Cc: sta...@vger.kernel.org
With that fixed,
Reviewed-by: Thomas Hellström
Signed-off-by: Dmitry Osipenko
---
d
On 5/27/22 01:50, Dmitry Osipenko wrote:
Drivers that use drm_gem_mmap() and drm_gem_mmap_obj() helpers don't
handle imported dma-bufs properly, which results in mapping of something
else than the imported dma-buf. For example, on NVIDIA Tegra we get a hard
lockup when userspace writes to the m
https://bugzilla.kernel.org/show_bug.cgi?id=216119
--- Comment #28 from Harald Judt (h.j...@gmx.at) ---
Created attachment 301304
--> https://bugzilla.kernel.org/attachment.cgi?id=301304&action=edit
dmesg.out
The new 2 patches alone work fine _without_ setting amdgpu.dc=0.
--
You may reply to
The issue cause by the commit :
721255b527(drm/syncobj: flatten dma_fence_chains on transfer).
Because it use the point of dma_fence incorrectly
Correct the point of dma_fence by fence array
Signed-off-by: jie1zhan
Reviewed-by: Christian König
Reviewed-by: Nirmoy Das
---
drivers/gpu/drm/
On Wed, Jun 29, 2022 at 01:51:01PM +0800, Jiapeng.Chong wrote:
> Sorry, we didn't see this patch.
> commit c09b1f372e746aeeb61ef8ffe0fea3970fd9273e
I am sorry, I do not understand what you mean here at all.
confused,
greg k-h
Sorry, we didn't see this patch.
commit c09b1f372e746aeeb61ef8ffe0fea3970fd9273e
--
发件人：Greg KH
发送时间：2022年6月24日(星期五) 19:45
收件人：Jiapeng Chong
抄 送：neal_liu ; balbi ; joel
; andrew ; sumit.semwal
; christian.koenig ;
linux-aspeed ;
> void intel_fbdev_unregister(struct drm_i915_private *dev_priv) {
> struct intel_fbdev *ifbdev = dev_priv->fbdev; @@ -573,6 +594,8 @@
> void intel_fbdev_unregister(struct drm_i915_private *dev_priv)
> if (!ifbdev)
> return;
>
> + intel_fbdev_hpd_set_suspend(dev_pri
On Tue, 28 Jun 2022 12:17:41 -0700, Ashutosh Dixit wrote:
>
> From: Chris Wilson
>
> When resuming after hibernate sometimes we see hangs in unrelated kernel
> subsystems. These hangs often result in the following i915 trace:
>
> i915 :00:02.0: [drm] \
> *ERROR* intel_gt_reset_global tim
On 6/29/22 01:35, Rob Clark wrote:
From: Rob Clark
drive-by cleanup
Signed-off-by: Rob Clark
Reviewed-by: Thomas Hellström
---
drivers/gpu/drm/i915/gem/i915_gem_wait.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_wait.c
On 6/29/2022 9:59 AM, Bjorn Andersson wrote:
On Tue 10 May 02:53 CDT 2022, Akhil P Oommen wrote:
Add a new sku to the fuse map of 7c3 gpu.
Signed-off-by: Akhil P Oommen
Is this series still needed/wanted? I've been waiting for patch 1 to be
merged in the driver so that I can pick up the dts
On Tue 10 May 02:53 CDT 2022, Akhil P Oommen wrote:
> Add a new sku to the fuse map of 7c3 gpu.
>
> Signed-off-by: Akhil P Oommen
Is this series still needed/wanted? I've been waiting for patch 1 to be
merged in the driver so that I can pick up the dts change.
Regards,
Bjorn
> ---
>
> (no ch
> -Original Message-
> From: Intel-gfx On Behalf Of
> Andrzej Hajda
> Sent: Thursday, June 23, 2022 10:08 PM
> To: Jani Nikula ; Ville Syrjälä
>
> Cc: Hajda, Andrzej ; intel-
> g...@lists.freedesktop.org; dri-devel@lists.freedesktop.org; Vivi, Rodrigo
>
> Subject: [Intel-gfx] [PATCH 1
On 6/28/2022 5:42 AM, David Hildenbrand wrote:
On 28.06.22 02:14, Alex Sierra wrote:
With DEVICE_COHERENT, we'll soon have vm_normal_pages() return
device-managed anonymous pages that are not LRU pages. Although they
behave like normal pages for purposes of mapping in CPU page, and for
COW. Th
The objective is to test device migration mechanism in pages marked
as COW, for private and coherent device type. In case of writing to
COW private page(s), a page fault will migrate pages back to system
memory first. Then, these pages will be duplicated. In case of COW
device coherent type, pages
In order to configure device coherent in test_hmm, two module parameters
should be passed, which correspond to the SP start address of each
device (2) spm_addr_dev0 & spm_addr_dev1. If no parameters are passed,
private device type is configured.
Signed-off-by: Alex Sierra
Acked-by: Felix Kuehling
new ioctl cmd added to query zone device type. This will be
used once the test_hmm adds zone device coherent type.
Signed-off-by: Alex Sierra
Acked-by: Felix Kuehling
Reviewed-by: Alistair Poppple
Signed-off-by: Christoph Hellwig
---
lib/test_hmm.c | 11 +--
lib/test_hmm_uapi.h |
Device Coherent type uses device memory that is coherently accesible by
the CPU. This could be shown as SP (special purpose) memory range
at the BIOS-e820 memory enumeration. If no SP memory is supported in
system, this could be faked by setting CONFIG_EFI_FAKE_MEMMAP.
Currently, test_hmm only sup
The intention is to test hmm device coherent type under different get
user pages paths. Also, test gup with FOLL_LONGTERM flag set in
device coherent pages. These pages should get migrated back to system
memory.
Signed-off-by: Alex Sierra
Reviewed-by: Alistair Popple
---
tools/testing/selftests
From: Alistair Popple
Currently any attempts to pin a device coherent page will fail. This is
because device coherent pages need to be managed by a device driver, and
pinning them would prevent a driver from migrating them off the device.
However this is no reason to fail pinning of these pages.
Test cases such as migrate_fault and migrate_multiple, were modified to
explicit migrate from device to sys memory without the need of page
faults, when using device coherent type.
Snapshot test case updated to read memory device type first and based
on that, get the proper returned results migrat
Add two more parameters to set spm_addr_dev0 & spm_addr_dev1
addresses. These two parameters configure the start SP
addresses for each device in test_hmm driver.
Consequently, this configures zone device type as coherent.
Signed-off-by: Alex Sierra
Acked-by: Felix Kuehling
Reviewed-by: Alistair
From: Alistair Popple
migrate_vma_setup() checks that a valid vma is passed so that the page
tables can be walked to find the pfns associated with a given address
range. However in some cases the pfns are already known, such as when
migrating device coherent pages during pin_user_pages() meaning
With DEVICE_COHERENT, we'll soon have vm_normal_pages() return
device-managed anonymous pages that are not LRU pages. Although they
behave like normal pages for purposes of mapping in CPU page, and for
COW. They do not support LRU lists, NUMA migration or THP.
Callers to follow_page that expect LR
This case is used to migrate pages from device memory, back to system
memory. Device coherent type memory is cache coherent from device and CPU
point of view.
Signed-off-by: Alex Sierra
Acked-by: Felix Kuehling
Reviewed-by: Alistair Poppple
Signed-off-by: Christoph Hellwig
---
include/linux/m
When CPU is connected throug XGMI, it has coherent
access to VRAM resource. In this case that resource
is taken from a table in the device gmc aperture base.
This resource is used along with the device type, which could
be DEVICE_PRIVATE or DEVICE_COHERENT to create the device
page map region.
Also
Device memory that is cache coherent from device and CPU point of view.
This is used on platforms that have an advanced system bus (like CAPI
or CXL). Any page of a process can be migrated to such memory. However,
no one should be allowed to pin such memory so that it can always be
evicted.
Signed
is_pinnable_page() and folio_is_pinnable() were renamed to
is_longterm_pinnable_page() and folio_is_longterm_pinnable()
respectively. These functions are used in the FOLL_LONGTERM flag
context.
Signed-off-by: Alex Sierra
---
include/linux/memremap.h | 24
include/linux/m
This is our MEMORY_DEVICE_COHERENT patch series rebased and updated
for current 5.19.0-rc4
Changes since the last version:
- Fixed problems with migration during long-term pinning in
get_user_pages
- Open coded vm_normal_lru_pages as suggested in previous code review
- Update hmm_gup_test with mor
https://bugzilla.kernel.org/show_bug.cgi?id=201957
rafael castillo (jrch2...@gmail.com) changed:
What|Removed |Added
CC||jrch2...@gmail.com
Hi all,
Today's linux-next merge of the drm-misc tree got a conflict in:
drivers/gpu/drm/vc4/vc4_drv.c
between commit:
538f6061 ("drm/vc4: drv: Register a different driver on BCM2711")
from Linus' tree and commit:
da8e393e23ef ("drm/vc4: drv: Adopt the dma configuration from the HVS
https://bugzilla.kernel.org/show_bug.cgi?id=216173
--- Comment #9 from Witold Baryluk (witold.baryluk+ker...@gmail.com) ---
Bisected:
9cad937c0c58618fe5b0310fd539a854dc1ae95 is the first bad commit
commit c9cad937c0c58618fe5b0310fd539a854dc1ae95
Author: Arunpravin Paneer Selvam
Date: Fri Apr 8
From: Rob Clark
drive-by cleanup
Signed-off-by: Rob Clark
---
drivers/gpu/drm/i915/gem/i915_gem_wait.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/i915/gem/i915_gem_wait.c
b/drivers/gpu/drm/i915/gem/i915_gem_wait.c
index 319936f91ac5..667841780514
On 6/28/22 19:48, Rob Clark wrote:
> On Tue, Jun 28, 2022 at 5:51 AM Dmitry Osipenko
> wrote:
>>
>> On 6/28/22 15:31, Robin Murphy wrote:
>>> ->8-
>>> [ 68.295951] ==
>>> [ 68.295956] WARNING: possible circular locking dependency dete
Ah-nevermind! Seems like someone already pushed this for you :)
On Tue, 2022-06-28 at 18:55 -0400, Lyude Paul wrote:
> Nice catch!
>
> Reviewed-by: Lyude Paul
>
> Will push to drm-intel-next
>
> On Fri, 2022-06-24 at 10:28 +0800, Hangyu Hua wrote:
> > If drm_connector_init fails, intel_connect
Nice catch!
Reviewed-by: Lyude Paul
Will push to drm-intel-next
On Fri, 2022-06-24 at 10:28 +0800, Hangyu Hua wrote:
> If drm_connector_init fails, intel_connector_free will be called to take
> care of proper free. So it is necessary to drop the refcount of port
> before intel_connector_free.
>
Oh-it's back up now! will push now :)
On Tue, 2022-06-28 at 17:35 -0400, Lyude Paul wrote:
> …ah, I totally forgot that gitlab happens to be down right now which part of
> the DRM maintainer scripts rely on - so I can't actually push this patch
> upstream right away. I will set this email as unrea
On 6/29/22 01:42, Dmitry Osipenko wrote:
> The code assumes that Tegra GEM is permanently vmapped, which is not
> true for the scattered buffers. After converting Tegra video decoder
> driver to V4L API, we're now getting a BUG_ON from dma-buf core on playing
> video using libvdpau-tegra on T30+ be
The code assumes that Tegra GEM is permanently vmapped, which is not
true for the scattered buffers. After converting Tegra video decoder
driver to V4L API, we're now getting a BUG_ON from dma-buf core on playing
video using libvdpau-tegra on T30+ because tegra_gem_prime_vmap() sets
vaddr to NULL.
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/Kconfig | 2 ++
drivers/gpu/drm/Makefile | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/Kconfig b/drivers/gpu/drm/Kconfig
index 30d5b91b717f..475d20c58da0 100644
--- a/drivers/gpu/drm/Kconfig
+++ b/drivers/
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/Makefile | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 drivers/gpu/drm/via/Makefile
diff --git a/drivers/gpu/drm/via/Makefile b/drivers/gpu/drm/via/Makefile
new file mode 100644
index 0
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/Kconfig | 10 ++
1 file changed, 10 insertions(+)
create mode 100644 drivers/gpu/drm/via/Kconfig
diff --git a/drivers/gpu/drm/via/Kconfig b/drivers/gpu/drm/via/Kconfig
new file mode 100644
index ..760bf59
From: Kevin Brace
Signed-off-by: Kevin Brace
---
include/drm/drm_pciids.h | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/include/drm/drm_pciids.h b/include/drm/drm_pciids.h
index e91b93d635fa..a4567d2918a9 100644
--- a/include/drm/drm_pciids.h
+++ b/include/d
From: Kevin Brace
Signed-off-by: Kevin Brace
---
include/linux/pci_ids.h | 15 +++
1 file changed, 15 insertions(+)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index 0178823ce8c2..809c61a10fe1 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@
From: Kevin Brace
Signed-off-by: Kevin Brace
---
include/drm/drm_pciids.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/drm/drm_pciids.h b/include/drm/drm_pciids.h
index b7e899ce44f0..e91b93d635fa 100644
--- a/include/drm/drm_pciids.h
+++ b/include/drm/drm_pciids.h
@@ -777,7 +
From: Kevin Brace
Signed-off-by: Kevin Brace
---
include/uapi/drm/via_drm.h | 309 +
1 file changed, 309 insertions(+)
create mode 100644 include/uapi/drm/via_drm.h
diff --git a/include/uapi/drm/via_drm.h b/include/uapi/drm/via_drm.h
new file mode 100644
in
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_vt1632.c | 583 +++
1 file changed, 583 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_vt1632.c
diff --git a/drivers/gpu/drm/via/via_vt1632.c b/drivers/gpu/drm/via/via_vt1632.c
new f
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_ttm.c | 168 ++
1 file changed, 168 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_ttm.c
diff --git a/drivers/gpu/drm/via/via_ttm.c b/drivers/gpu/drm/via/via_ttm.c
new file mode
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_tmds.c | 714 +
1 file changed, 714 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_tmds.c
diff --git a/drivers/gpu/drm/via/via_tmds.c b/drivers/gpu/drm/via/via_tmds.c
new file mo
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_sii164.c | 563 +++
1 file changed, 563 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_sii164.c
diff --git a/drivers/gpu/drm/via/via_sii164.c b/drivers/gpu/drm/via/via_sii164.c
new f
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_pm.c | 187 +++
1 file changed, 187 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_pm.c
diff --git a/drivers/gpu/drm/via/via_pm.c b/drivers/gpu/drm/via/via_pm.c
new file mode 100
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_pll.c | 263 ++
1 file changed, 263 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_pll.c
diff --git a/drivers/gpu/drm/via/via_pll.c b/drivers/gpu/drm/via/via_pll.c
new file mode
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_object.c | 324 +++
1 file changed, 324 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_object.c
diff --git a/drivers/gpu/drm/via/via_object.c b/drivers/gpu/drm/via/via_object.c
new f
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_lvds.c | 1420
1 file changed, 1420 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_lvds.c
diff --git a/drivers/gpu/drm/via/via_lvds.c b/drivers/gpu/drm/via/via_lvds.c
new file m
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_init.c | 1300
1 file changed, 1300 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_init.c
diff --git a/drivers/gpu/drm/via/via_init.c b/drivers/gpu/drm/via/via_init.c
new file m
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_ioctl.c | 122
1 file changed, 122 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_ioctl.c
diff --git a/drivers/gpu/drm/via/via_ioctl.c b/drivers/gpu/drm/via/via_ioctl.c
new file
From: Kevin Brace
Note that the code here is GPL based.
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_i2c.c | 209 ++
1 file changed, 209 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_i2c.c
diff --git a/drivers/gpu/drm/via/via_i2c.c b/drive
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_hdmi.c | 719 +
1 file changed, 719 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_hdmi.c
diff --git a/drivers/gpu/drm/via/via_hdmi.c b/drivers/gpu/drm/via/via_hdmi.c
new file mo
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_encoder.c | 173 ++
1 file changed, 173 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_encoder.c
diff --git a/drivers/gpu/drm/via/via_encoder.c
b/drivers/gpu/drm/via/via_encoder.c
n
From: Kevin Brace
Note that GPL is chosen as a license type. This is due to via_i2c.c
being GPL based. Everything else is MIT license based.
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_drv.c | 313 ++
1 file changed, 313 insertions(+)
create mode 1
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_display.c | 125 ++
1 file changed, 125 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_display.c
diff --git a/drivers/gpu/drm/via/via_display.c
b/drivers/gpu/drm/via/via_display.c
n
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_cursor.c | 419 +++
1 file changed, 419 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_cursor.c
diff --git a/drivers/gpu/drm/via/via_cursor.c b/drivers/gpu/drm/via/via_cursor.c
new f
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_dac.c | 504 ++
1 file changed, 504 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_dac.c
diff --git a/drivers/gpu/drm/via/via_dac.c b/drivers/gpu/drm/via/via_dac.c
new file mode
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_crtc_hw.c | 91 +++
1 file changed, 91 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_crtc_hw.c
diff --git a/drivers/gpu/drm/via/via_crtc_hw.c
b/drivers/gpu/drm/via/via_crtc_hw.c
ne
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_crtc.c | 2324
1 file changed, 2324 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_crtc.c
diff --git a/drivers/gpu/drm/via/via_crtc.c b/drivers/gpu/drm/via/via_crtc.c
new file m
From: Kevin Brace
Likely originated from VIA Technologies.
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_regs.h | 296 +
1 file changed, 296 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_regs.h
diff --git a/drivers/gpu/drm/via/via_regs.h b/
From: Kevin Brace
Main header file for the module.
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_drv.h | 437 ++
1 file changed, 437 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_drv.h
diff --git a/drivers/gpu/drm/via/via_drv.h b/drivers/gp
From: Kevin Brace
Likely originated from VIA Technologies.
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_disp_reg.h | 513 +
1 file changed, 513 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_disp_reg.h
diff --git a/drivers/gpu/drm/via/via_disp_
From: Kevin Brace
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_crtc_hw.h | 1048 +
1 file changed, 1048 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_crtc_hw.h
diff --git a/drivers/gpu/drm/via/via_crtc_hw.h
b/drivers/gpu/drm/via/via_crtc_hw.h
From: Kevin Brace
Originated from VIA Technologies. Currently unused.
Signed-off-by: Kevin Brace
---
drivers/gpu/drm/via/via_3d_reg.h | 1863 ++
1 file changed, 1863 insertions(+)
create mode 100644 drivers/gpu/drm/via/via_3d_reg.h
diff --git a/drivers/gpu/drm/vi
From: Kevin Brace
OpenChrome DRM for Linux 5.20
Hi Dave and Daniel,
This is my first attempt (this is not a RFC posting) in trying to get
OpenChrome DRM pulled in for Linux 5.20.
I started to work on this seriously around the summer of 2017, so it has
been a long journey.
I know that the code i
…ah, I totally forgot that gitlab happens to be down right now which part of
the DRM maintainer scripts rely on - so I can't actually push this patch
upstream right away. I will set this email as unread so hopefully I don't lose
track of this, but please feel free to ping me if I do end up forgetti
On 6/19/22 18:31, Melissa Wen wrote:
> Add 3D LUT for gammar correction using a 3D lookup table. The position
> in the color correction pipeline where 3D LUT is applied depends on hw
> design, being after CTM or gamma. If just after CTM, a shaper lut must
> be set to shape the content for a non
https://bugzilla.kernel.org/show_bug.cgi?id=216119
--- Comment #27 from Alex Deucher (alexdeuc...@gmail.com) ---
Created attachment 301300
--> https://bugzilla.kernel.org/attachment.cgi?id=301300&action=edit
patch 2/2
--
You may reply to this email to add a comment.
You are receiving this mai
https://bugzilla.kernel.org/show_bug.cgi?id=216119
--- Comment #26 from Alex Deucher (alexdeuc...@gmail.com) ---
Created attachment 301299
--> https://bugzilla.kernel.org/attachment.cgi?id=301299&action=edit
patch 1/2
Can you try the attached 2 patches (without any previous patches) both with a
Reviewed-by: Lyude Paul
Going to change the name of the patch slightly so it's more obvious this is
just about the MST selftests
On Thu, 2022-06-23 at 18:06 +0800, Jiang Jian wrote:
> there is an unexpected word 'for' in the comments that need to be dropped
>
> file - ./drivers/gpu/drm/selftest
On 6/19/22 18:31, Melissa Wen wrote:
> Add details about color correction capabilities and explain a bit about
> differences between DC hw generations and also how they are mapped
> between DRM and DC interface. Two schemas for DCN 2.0 and 3.0
> (rasterized from the original png) is included to
On 5/30/22 15:57, Dmitry Osipenko wrote:
On 5/30/22 16:41, Christian König wrote:
Hi Dmitry,
Am 30.05.22 um 15:26 schrieb Dmitry Osipenko:
Hello Christian,
On 5/30/22 09:50, Christian König wrote:
Hi Dmitry,
First of all please separate out this patch from the rest of the series,
since th
https://bugzilla.kernel.org/show_bug.cgi?id=216119
--- Comment #25 from Harald Judt (h.j...@gmx.at) ---
Created attachment 301298
--> https://bugzilla.kernel.org/attachment.cgi?id=301298&action=edit
dmesg.out
I report success, partly.
Setting amdgpu.dc=0 on the kernel command line also exhibit
On Tue, Jun 28, 2022 at 1:40 PM Stephen Boyd wrote:
>
> Quoting Prashant Malani (2022-06-28 12:48:11)
> > On Tue, Jun 28, 2022 at 12:25 PM Stephen Boyd wrote:
> > >
> > > Quoting Prashant Malani (2022-06-22 10:34:34)
> > > > diff --git a/drivers/gpu/drm/bridge/analogix/anx7625.c
> > > > b/driver
Image.dx gets wrong value because of missing '()'.
If xres == logo->width and n == 1, image.dx = -16.
Signed-off-by: Guiling Deng
---
drivers/video/fbdev/core/fbmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/video/fbdev/core/fbmem.c b/drivers/video/fbdev/core/
On 6/28/22 10:39, Geert Uytterhoeven wrote:
> Hi Helge,
>
> On Sun, Jun 26, 2022 at 12:33 PM Helge Deller wrote:
>> We need to prevent that users configure a screen size which is smaller than
>> the
>> currently selected font size. Otherwise rendering chars on the screen will
>> access memory out
Hi Geert,
On 6/28/22 10:36, Geert Uytterhoeven wrote:
> On Sun, Jun 26, 2022 at 12:32 PM Helge Deller wrote:
>> Prevent that drivers or the user sets the virtual screen resolution
>> smaller than the physical screen resolution. This is important, because
>> otherwise we may access memory outside
Quoting Prashant Malani (2022-06-28 12:48:11)
> On Tue, Jun 28, 2022 at 12:25 PM Stephen Boyd wrote:
> >
> > Quoting Prashant Malani (2022-06-22 10:34:34)
> > > diff --git a/drivers/gpu/drm/bridge/analogix/anx7625.c
> > > b/drivers/gpu/drm/bridge/analogix/anx7625.c
> > > index bd21f159b973..5992f
On 2022-06-19 18:31, Melissa Wen wrote:
> AMDGPU DM maps DRM color management properties (degamma, ctm and gamma)
> to DC color correction entities. Part of this mapping is already
> documented as code comments and can be converted as kernel docs.
>
> Signed-off-by: Melissa Wen
> ---
> .../gp
On 28 June 2022 18:20:06 GMT+03:00, Kuogee Hsieh
wrote:
>Some userspace presumes that the first connected connector is the main
>display, where it's supposed to display e.g. the login screen. For
>laptops, this should be the main panel.
>
>This patch call drm_helper_move_panel_connectors_to_he
Hi,
On 5/27/22 01:50, Dmitry Osipenko wrote:
Use ww_acquire_fini() in the error code paths. Otherwise lockdep
thinks that lock is held when lock's memory is freed after the
drm_gem_lock_reservations() error. The WW needs to be annotated
as "freed"
s /WW/ww_acquire_context/ ?
s /"freed"/"releas
On 2022-06-19 18:30, Melissa Wen wrote:
> Hi,
>
> I've been working on a proposal to add 3D LUT interface to DRM CRTC
> color mgmt, that means new **after-blending** properties for color
> correction. As I'm targeting AMD display drivers, I need to map these
> new properties to AMD DC interface
On Tue, Jun 28, 2022 at 12:25 PM Stephen Boyd wrote:
>
> Quoting Prashant Malani (2022-06-22 10:34:34)
> > From: Pin-Yen Lin
> >
> > Add the callback function when the driver receives state
> > changes of the Type-C port. The callback function configures the
> > crosspoint switch of the anx7625 b
On 2022-06-27 08:18, Ville Syrjälä wrote:
> On Sun, Jun 19, 2022 at 09:31:03PM -0100, Melissa Wen wrote:
>> Add 3D LUT for gammar correction using a 3D lookup table. The position
>> in the color correction pipeline where 3D LUT is applied depends on hw
>> design, being after CTM or gamma. If ju
Quoting Prashant Malani (2022-06-22 10:34:34)
> From: Pin-Yen Lin
>
> Add the callback function when the driver receives state
> changes of the Type-C port. The callback function configures the
> crosspoint switch of the anx7625 bridge chip, which can change the
> output pins of the signals accord
From: Chris Wilson
When resuming after hibernate sometimes we see hangs in unrelated kernel
subsystems. These hangs often result in the following i915 trace:
i915 :00:02.0: [drm] \
*ERROR* intel_gt_reset_global timed out, cancelling all in-flight
rendering.
implying our reset task
Like was done for read, provide the equivalent for write. Even if
current users are not in the hot path, this should future-proof it.
v2:
- Remove default from _Generic() - callers wanting to write more
than u64 should use iosys_map_memcpy_to()
- Add WRITE_ONCE() cases dereferencing the po
Instead of always falling back to memcpy_fromio() for any size, prefer
using read{b,w,l}(). When reading struct members it's common to read
individual integer variables individually. Going through memcpy_fromio()
for each of them poses a high penalty.
Employ a similar trick as __seqprop() by using
On Tue, Jun 28, 2022 at 11:47:45AM -0700, Lucas De Marchi wrote:
From: Ville Syrjälä
Sorry for the noise.
This should NOT be the patch 1, of course. It went here beacuse my local
and remote branch were out of sync (and drm-tip/drm-tip.. then includes
it)
This is intended for CI, but it will
Em seg., 27 de jun. de 2022 às 13:13, José Expósito
escreveu:
>
> Hello everyone,
>
> This series is a follow up of the XRGB to RGB332 conversion KUnit tests.
>
> The first 3 patches refactor the existing test to make them agnostic of the
> target format and add support for "swab".
>
> The la
Instead of always falling back to memcpy_fromio() for any size, prefer
using read{b,w,l}(). When reading struct members it's common to read
individual integer variables individually. Going through memcpy_fromio()
for each of them poses a high penalty.
Employ a similar trick as __seqprop() by using
Like was done for read, provide the equivalent for write. Even if
current users are not in the hot path, this should future-proof it.
v2:
- Remove default from _Generic() - callers wanting to write more
than u64 should use iosys_map_memcpy_to()
- Add WRITE_ONCE() cases dereferencing the po
From: Ville Syrjälä
---
integration-manifest | 26 ++
1 file changed, 26 insertions(+)
create mode 100644 integration-manifest
diff --git a/integration-manifest b/integration-manifest
new file mode 100644
index ..baffa2a57cd4
--- /dev/null
+++ b/integration-
On Tue, Jun 28, 2022 at 10:54:58AM -0700, Kees Cook wrote:
> which must also be assuming it's a header. So probably better to just
> drop the driver_data field? I don't see anything using it (that I can
> find) besides as a sanity-check that the field exists and is at the end
> of the struct.
T
1 - 100 of 195 matches
Mail list logo
