https://bugzilla.kernel.org/show_bug.cgi?id=214207
Alexey Boldyrev (ne-vleza...@yandex.ru) changed:
What|Removed |Added
Keywords||opw
https://bugzilla.kernel.org/show_bug.cgi?id=214207
Bug ID: 214207
Summary: Nouveau crash after play youtube video from surf
browser
Product: Drivers
Version: 2.5
Kernel Version: 5.10.0-8-amd64
Hardware: x86-64
Hi Fangzhi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next linus/master v5.14-rc7 next-20210827]
[cannot apply to drm/drm-next
From: "Huang, Sean Z"
During the power event S3+ sleep/resume, hardware will lose all the
encryption keys for every hardware session, even though the
session state might still be marked as alive after resume. Therefore,
we should consider the session as dead on suspend and invalidate all the
Now that we can handle destruction and re-creation of the arb session,
we can postpone the start of the session to the first submission that
requires it, to avoid keeping it running with no user.
Signed-off-by: Daniele Ceraolo Spurio
Reviewed-by: Rodrigo Vivi
---
Note that discrete cards can support PXP as well, but we haven't tested
on those yet so keeping it disabled for now.
Signed-off-by: Daniele Ceraolo Spurio
Reviewed-by: Rodrigo Vivi
---
drivers/gpu/drm/i915/i915_pci.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
From: Anshuman Gupta
When protected sufaces has flipped and pxp session is disabled,
display black pixels by using plane color CTM correction.
v2:
- Display black pixels in async flip too.
v3:
- Removed the black pixels logic for async flip. [Ville]
- Used plane state to force black pixels.
Now that all the pieces are in place we can add a description of how the
feature works. Also modify the comments in struct intel_pxp into
kerneldoc.
Signed-off-by: Daniele Ceraolo Spurio
Cc: Daniel Vetter
Cc: Rodrigo Vivi
---
Documentation/gpu/i915.rst | 8
2 debugfs files, one to query the current status of the pxp session and one
to trigger an invalidation for testing.
Signed-off-by: Daniele Ceraolo Spurio
---
drivers/gpu/drm/i915/Makefile| 1 +
drivers/gpu/drm/i915/gt/debugfs_gt.c | 2 +
From: "Huang, Sean Z"
Implement the funcs to create the TEE channel, so kernel can
send the TEE commands directly to TEE for creating the arbitrary
(default) session.
v2: fix locking, don't pollute dev_priv (Chris)
v3: wait for mei PXP component to be bound.
v4: drop the wait, as the
This will be used for communication between the i915 driver and the mei
one. Defining it in a stand-alone patch to avoid circualr dependedencies
between the patches modifying the 2 drivers.
Split out from an original patch from Huang, Sean Z
v2: rename the component struct (Rodrigo)
From: "Huang, Sean Z"
Create the arbitrary session, with the fixed session id 0xf, after
system boot, for the case that application allocates the protected
buffer without establishing any protection session. Because the
hardware requires at least one alive session for protected buffer
creation.
From: "Huang, Sean Z"
The HW will generate a teardown interrupt when session termination is
required, which requires i915 to submit a terminating batch. Once the HW
is done with the termination it will generate another interrupt, at
which point it is safe to re-create the session.
Since the
From: Anshuman Gupta
Add support to enable/disable PLANE_SURF Decryption Request bit.
It requires only to enable plane decryption support when following
condition met.
1. PXP session is enabled.
2. Buffer object is protected.
v2:
- Used gen fb obj user_flags instead gem_object_metadata.
The context is required to send the session termination commands to the
VCS, which will be implemented in a follow-up patch. We can also use the
presence of the context as a check of pxp initialization completion.
v2: use perma-pinned context (Chris)
v3: rename pinned_context functions (Chris)
PXP (Protected Xe Path) is an i915 component, available on
GEN12+, that helps to establish the hardware protected session
and manage the status of the alive software session, as well
as its life cycle.
Changes from v6:
- reworked object invalidation to be based on PXP instance instead of
From: "Huang, Sean Z"
Teardown is triggered when the display topology changes and no
long meets the secure playback requirement, and hardware trashes
all the encryption keys for display. Additionally, we want to emit a
teardown operation to make sure we're clean on boot and resume
v2: emit in
The setting is required by hardware to allow us doing further protection
operation such as sending commands to GPU or TEE. The register needs to
be re-programmed on resume, so for simplicitly we bundle the programming
with the component binding, which is automatically called on resume.
Further HW
This api allow user mode to create protected buffers and to mark
contexts as making use of such objects. Only when using contexts
marked in such a way is the execution guaranteed to work as expected.
Contexts can only be marked as using protected content at creation time
(i.e. the parameter is
Ahead of the PXP implementation, define the relevant define flag and
kconfig option.
v2: flip kconfig default to N. Some machines have IFWIs that do not
support PXP, so we need it to be an opt-in until we add support to query
the caps from the mei device.
Signed-off-by: Daniele Ceraolo Spurio
From: Vitaly Lubart
Export PAVP client to work with i915 driver,
for binding it uses kernel component framework.
v2:drop debug prints, refactor match code to match mei_hdcp (Tomas)
Signed-off-by: Vitaly Lubart
Signed-off-by: Tomas Winkler
Signed-off-by: Daniele Ceraolo Spurio
Reviewed-by:
1. Decide MST Link Encoding Cap
2. Update MST First Link Slot Information
Signed-off-by: Fangzhi Zuo
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 4 +++-
.../drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c| 10 ++
.../drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.h
8b/10b encoding format requires to reserve the first slot for
recording metadata. Real data transmission starts from the second slot,
with a total of available 63 slots available.
In 128b/132b encoding format, metadata is transmitted separately
in LLCP packet before MTP. Real data transmission
128b/132b MST start slot information is not the same as 8b/10b.
Update based on encoding format after link detection or topology change.
Fangzhi Zuo (2):
drm: Update MST First Link Slot Information Based on Encoding Format
drm/amdgpu: Example Usage in AMDGPU
Hi
On Thu, Aug 26, 2021, at 2:31 PM, Thomas Zimmermann wrote:
>
> You said that the resolution is 3840 x 2160, but the attached log says
> 1024x768. I guess that the former is the monitor's native resolution and
> the latter is the display mode?
>
Yes, that's the monitor native resolution
Hello Daniel and Thomas,
On 8/27/21 10:20 PM, Daniel Vetter wrote:
> On Fri, Aug 27, 2021 at 07:50:23PM +0200, Thomas Zimmermann wrote:
>> Hi
>>
>> Am 27.08.21 um 12:00 schrieb Javier Martinez Canillas:
>>> This patch series splits the fbdev core support in two different Kconfig
>>> symbols: FB
https://bugzilla.kernel.org/show_bug.cgi?id=211807
Nils Tonnätt (nils.tonna...@posteo.de) changed:
What|Removed |Added
CC|
Hi,
On Mon, Jul 26, 2021 at 4:15 PM Bjorn Andersson
wrote:
>
> +static int dp_parser_find_panel(struct dp_parser *parser)
> +{
> + struct device_node *np = parser->pdev->dev.of_node;
> + int rc;
> +
> + rc = drm_of_find_panel_or_bridge(np, 2, 0, >drm_panel, NULL);
Why port 2?
Handle all DMA IOMMU group related dependencies before the
group is removed and we try to access it after free.
v2:
Move the actul handling function to TTM
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
To support libdrm tests.
Signed-off-by: Andrey Grodzovsky
---
drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
index 6400259a7c4b..c2fdf67ff551 100644
Used by drivers supporting hot unplug to handle all
DMA IOMMU group related dependencies before the group
is removed during device removal and we try to access
it after free when last device pointer from user space
is dropped.
v3:
Switch to ttm_bo_get_unless_zerom
Iterate bdev for pinned list
This list will be used to capture all non VRAM BOs not
on LRU so when device is hot unplugged we can iterate
the list and unmap DMA mappings before device is removed.
v2: Reanme function to ttm_bo_move_to_pinned
v3: Move the pinned list to ttm device
Signed-off-by: Andrey Grodzovsky
Bunch of fixes to enable passing hotplug tests i previosly added
here[1] with latest code.
Once accepted I will enable the tests on libdrm side.
[1] - https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/172
v2:
Dropping VCE patch since relevant function already fixed in latest
code.
Moving
On Fri, Aug 27, 2021 at 11:07:58AM +0200, Christian König wrote:
> Am 26.08.21 um 10:55 schrieb Daniel Vetter:
> > On Tue, Aug 24, 2021 at 10:12:24AM +0200, Christian König wrote:
> > > Just a gentle ping. Daniel any more comments on this?
> > Still haven't seen a patch set to nuke the sw_sync igt
On Fri, Aug 27, 2021 at 07:50:23PM +0200, Thomas Zimmermann wrote:
> Hi
>
> Am 27.08.21 um 12:00 schrieb Javier Martinez Canillas:
> > This patch series splits the fbdev core support in two different Kconfig
> > symbols: FB and FB_CORE. The motivation for this is to allow CONFIG_FB to
> > be
Hi Dave, Daniel,
Fixes for 5.15.
The following changes since commit 90a9266269eb9f71af1f323c33e1dca53527bd22:
drm/amdgpu: Cancel delayed work when GFXOFF is disabled (2021-08-20 12:09:44
-0400)
are available in the Git repository at:
https://gitlab.freedesktop.org/agd5f/linux.git
Yeah, that's what I meant with that the start of processing a job is a
bit swampy defined.
Jobs overload, but we simply don't have another good indicator that a
job started except that the previous one completed.
It's still better than starting the timer when pushing the job to the
ring
From: Colin Ian King
There are three identical spelling mistakes in dev_err messages.
Fix these.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/amd/pm/swsmu/smu11/vangogh_ppt.c | 2 +-
drivers/gpu/drm/amd/pm/swsmu/smu12/renoir_ppt.c | 2 +-
From: Colin Ian King
There is a spelling mistake in a printk message. Fix it.
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/i810/i810_dma.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i810/i810_dma.c b/drivers/gpu/drm/i810/i810_dma.c
index
Sure then.
Andrey
On 2021-08-27 2:30 p.m., Christian König wrote:
Yeah, that's what I meant with that the start of processing a job is a
bit swampy defined.
Jobs overload, but we simply don't have another good indicator that a
job started except that the previous one completed.
It's still
https://bugzilla.kernel.org/show_bug.cgi?id=211425
Andreas (icedragon...@web.de) changed:
What|Removed |Added
Kernel Version|5.13.11 |5.13.13
--
You may
As I mentioned to Monk before - what about cases such as in this test -
https://gitlab.freedesktop.org/mesa/drm/-/commit/bc21168fa924d3fc4a000492e861f50a1a135b25
Here you don't have serialized sequence where when jobs finishes
processing and second starts, they execute together concurrently -
Applied. Thanks!
Alex
On Thu, Aug 26, 2021 at 11:16 PM Kees Cook wrote:
>
> In preparation for FORTIFY_SOURCE performing compile-time and run-time
> field bounds checking for memcpy(), memmove(), and memset(), avoid
> intentionally writing across neighboring fields.
>
> The "Board Parameters"
Ping
Andrey
On 2021-08-26 1:27 p.m., Andrey Grodzovsky wrote:
Bunch of fixes to enable passing hotplug tests i previosly added
here[1] with latest code.
Once accepted I will enable the tests on libdrm side.
[1] - https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/172
v2:
Dropping VCE
On Wed, Aug 25, 2021 at 11:13 AM Jason Baron wrote:
>
>
>
> On 8/22/21 6:19 PM, Jim Cromie wrote:
> > Add a const void* data member to the struct, to allow attaching
> > private data that will be used soon by a setter method (via kp->data)
> > to perform more elaborate actions.
> >
> > To attach
Hi
Am 27.08.21 um 12:00 schrieb Javier Martinez Canillas:
This patch series splits the fbdev core support in two different Kconfig
symbols: FB and FB_CORE. The motivation for this is to allow CONFIG_FB to
be disabled, while still using fbcon with the DRM fbdev emulation layer.
I'm skeptical.
https://bugzilla.kernel.org/show_bug.cgi?id=214197
--- Comment #2 from Alex Deucher (alexdeuc...@gmail.com) ---
Does this patch fix the issue?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=202ead5a3c589b0594a75cb99f080174f6851fed
--
You may reply to this email to
On Fri 27 Aug 00:20 CDT 2021, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2021-08-25 16:42:31)
> > diff --git a/drivers/gpu/drm/msm/dp/dp_display.c
> > b/drivers/gpu/drm/msm/dp/dp_display.c
> > index 2c7de43f655a..4a6132c18e57 100644
> > --- a/drivers/gpu/drm/msm/dp/dp_display.c
> > +++
If run before the next bridge is initialized, of_drm_find_bridge() will
give us a NULL pointer.
If that's the case, return -EPROBE_DEFER; we may have more luck next
time.
Signed-off-by: Paul Cercueil
---
drivers/gpu/drm/bridge/ite-it66121.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
These two arrays are populated with data read from the I2C device
through regmap_read(), and the data is then compared with hardcoded
vendor/product ID values of supported chips.
However, the return value of regmap_read() was never checked. This is
fine, as long as the two arrays are
https://bugzilla.kernel.org/show_bug.cgi?id=214197
Alex Deucher (alexdeuc...@gmail.com) changed:
What|Removed |Added
CC|
On 27/08/2021 15:39, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
In short this makes i915 work for hybrid setups (DRI_PRIME=1 with Mesa)
when rendering is done on Intel dgfx and scanout/composition on Intel
igfx.
Before this patch the driver was not quite ready for that setup, mainly
because
Hi,
On Fri, Aug 27, 2021 at 1:24 AM yangcong
wrote:
>
> Add driver for BOE tv110c9m-ll3 and Inx hj110iz-01a panel
> both of those are 10.95" 1200x2000 panel.
Your commit message would be a good place to note design choices you
made in your patch. Maybe you might say:
Support for these two
Am 27.08.21 um 15:55 schrieb Thomas Hellström:
Hi, Christian.
We have a use-case with i915 where the data representation of a buffer
object is larger in system memory than in LMEM/VRAM. Hence we'd like
to create a ttm_tt that is larger than the buffer object itself.
Quickly auditing the TTM
From: Tvrtko Ursulin
In short this makes i915 work for hybrid setups (DRI_PRIME=1 with Mesa)
when rendering is done on Intel dgfx and scanout/composition on Intel
igfx.
Before this patch the driver was not quite ready for that setup, mainly
because it was able to emit a semaphore wait between
I don't think that makes sense.
See we don't want to start the time when the job is inserted into the
ring buffer, but rather when it starts processing.
Starting processing is a bit swampy defined, but just starting the timer
when the previous job completes should be fine enough.
Yes, I don't see any good reason for that either.
Christian.
Am 27.08.21 um 15:45 schrieb Andrey Grodzovsky:
So we agree if (kthread_should_park()) return NULL should go away ?
Andrey
On 2021-08-27 3:46 a.m., Liu, Monk wrote:
[AMD Official Use Only]
Yeah, that "kthread_should_park" is
Hello Jernej,
During local testing I faced an issue where YV12 buffers are displayed
all in blue.
Issue can be fixed by reverting:
ea067aee45a8 ("drm/sun4i: de2/de3: Remove redundant CSC matrices")
Could you have a look please?
Best regards,
Roman Stratiienko
+CC: jernej.skra...@gmail.com
пт, 27 авг. 2021 г. в 16:12, Roman Stratiienko :
>
> Hello Jernej,
>
> During local testing I faced an issue where YV12 buffers are displayed
> all in blue.
>
> Issue can be fixed by reverting:
> ea067aee45a8 ("drm/sun4i: de2/de3: Remove redundant CSC matrices")
>
>
So we agree if (kthread_should_park()) return NULL should go away ?
Andrey
On 2021-08-27 3:46 a.m., Liu, Monk wrote:
[AMD Official Use Only]
Yeah, that "kthread_should_park" is also irrelevant looks to me as well and it
delays the signaled job's cleanup/free
Thanks
On Fri, Aug 27, 2021 at 03:22:59PM +0200, Thierry Reding wrote:
> From: Thierry Reding
>
> The Video Image Composer (VIC) 3.0 can be found on NVIDIA Tegra124 SoCs.a
[...]
> +static int vic30_clear(struct vic *v, struct vic_image *output,
> + unsigned int alpha, unsigned int
The TS represents the point in time when the job was inserted into the
pending list.
I don't think it matters when it actually starts to be processed, what
matters is when this job was inserted into pending list because right at
that point you arm the TO timer (when no other is running
Hi, Christian.
We have a use-case with i915 where the data representation of a buffer
object is larger in system memory than in LMEM/VRAM. Hence we'd like to
create a ttm_tt that is larger than the buffer object itself. Quickly
auditing the TTM code it looks like that should be pretty safe,
From: Tvrtko Ursulin
In short this makes i915 work for hybrid setups (DRI_PRIME=1 with Mesa)
when rendering is done on Intel dgfx and scanout/composition on Intel
igfx.
Before this patch the driver was not quite ready for that setup, mainly
because it was able to emit a semaphore wait between
From: Thierry Reding
This test will attempt to use the VIC to blit from one surface to
another.
Signed-off-by: Thierry Reding
---
tests/tegra/meson.build | 9 ++
tests/tegra/vic-blit.c | 333
2 files changed, 342 insertions(+)
create mode 100644
From: Thierry Reding
The Video Image Composer (VIC) 4.1 can be found on NVIDIA Tegra186 SoCs.
It uses a different class (B1B6) that is slightly incompatible with the
class found on earlier generations.
Signed-off-by: Thierry Reding
---
tests/tegra/meson.build | 2 +
tests/tegra/vic.c
From: Thierry Reding
The Video Image Composer (VIC) 4.0 can be found on NVIDIA Tegra210 SoCs.
It uses a different class (B0B6) that is slightly incompatible with the
class found on earlier generations.
Signed-off-by: Thierry Reding
---
tests/tegra/meson.build | 2 +
tests/tegra/vic.c
From: Thierry Reding
This test will attempt to use VIC to clear a surface.
Signed-off-by: Thierry Reding
---
tests/tegra/meson.build | 9 +++
tests/tegra/vic-clear.c | 173
2 files changed, 182 insertions(+)
create mode 100644
From: Thierry Reding
These new functions can be used to open a channel to a given engine, map
and unmap buffer objects to that channel, and close the channel.
Signed-off-by: Thierry Reding
---
tegra/channel.c | 195
tegra/meson.build |
From: Thierry Reding
These new functions can be used to allocate and free syncpoints, as well
as wait for a syncpoint threshold to be reached. Jobs can also be waited
on if a syncpoint was attached to them.
Signed-off-by: Thierry Reding
---
tegra/job.c | 23 +
From: Thierry Reding
The Video Image Composer (VIC) 4.2 can be found on NVIDIA Tegra194 SoCs.
It uses a different class (C5B6) that is slightly incompatible with the
class found on earlier generations, although it is backwards compatible
with the class implemented on Tegra186 (B1B6).
From: Thierry Reding
This test will attempt to use the VIC to blit one surface to another
and perform a vertical flip.
Signed-off-by: Thierry Reding
---
tests/tegra/meson.build | 9 ++
tests/tegra/vic-flip.c | 333
2 files changed, 342 insertions(+)
From: Thierry Reding
The Video Image Composer (VIC) 3.0 can be found on NVIDIA Tegra124 SoCs.
Signed-off-by: Thierry Reding
---
tegra/private.h | 6 +
tests/tegra/meson.build | 2 +
tests/tegra/vic.c | 8 +-
tests/tegra/vic30.c | 509
From: Thierry Reding
This is a very simple sanity test to check whether or not a syncpt can
be incremented by a host1x client. This uses gr2d on Tegra20 through
Tegra114 and VIC on Tegra124 and later.
Signed-off-by: Thierry Reding
---
tests/tegra/meson.build | 9 +++
From: Thierry Reding
Implement a small abstraction interface to allow different versions of
VIC to be used transparently. An implementation will be chosen based on
the VIC version number reported by the DRM_TEGRA_IOCTL_OPEN_CHANNEL
IOCTL.
Signed-off-by: Thierry Reding
---
tests/tegra/host1x.h
From: Thierry Reding
This library provides helpers for common functionality needed by test
programs.
Signed-off-by: Thierry Reding
---
tests/tegra/drm-test.c | 248
tests/tegra/drm-test.h | 72
tests/tegra/meson.build | 7 ++
3 files
From: Thierry Reding
This makes sure that the proper dependencies are created and that the
file is distributed.
Signed-off-by: Thierry Reding
---
tegra/meson.build | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/tegra/meson.build b/tegra/meson.build
index
From: Thierry Reding
This test uses the IOCTLs for job submission and fences to fill a sub-
region of the screen to a specific color using gr2d.
Signed-off-by: Thierry Reding
---
tests/tegra/.gitignore | 1 +
tests/tegra/drm-test-tegra.c | 147 +++
From: Thierry Reding
This test can be used to purposefully trigger a job timeout.
Signed-off-by: Thierry Reding
---
tests/tegra/meson.build | 9 ++
tests/tegra/syncpt-timeout.c | 163 +++
2 files changed, 172 insertions(+)
create mode 100644
From: Thierry Reding
These new functions can be used to create a job on a given channel, add
commands to the job using its push buffer and submit the job.
Signed-off-by: Thierry Reding
---
tegra/job.c | 164
tegra/meson.build | 2 +-
From: Thierry Reding
This new UABI is a more modern version that works better with both old
and recent chips.
Signed-off-by: Thierry Reding
---
include/drm/tegra_drm.h | 429 +---
1 file changed, 404 insertions(+), 25 deletions(-)
diff --git
From: Thierry Reding
Add helpers to export and import buffer objects via flink names.
Signed-off-by: Thierry Reding
---
Changes in v3:
- add drm_public annotations
---
tegra/tegra-symbols.txt | 2 ++
tegra/tegra.c | 50 +
tegra/tegra.h
From: Thierry Reding
Allow this simple test to be installed so that it can easily be run on a
target device.
Signed-off-by: Thierry Reding
---
tests/tegra/.gitignore | 2 +-
tests/tegra/meson.build | 7 +--
2 files changed, 6 insertions(+), 3 deletions(-)
diff --git
From: Thierry Reding
These helpers facilitate exporting and importing buffer objects to and
from PRIME file descriptors.
Signed-off-by: Thierry Reding
---
Changes in v3:
- add drm_public annotations
---
tegra/tegra-symbols.txt | 2 ++
tegra/tegra.c | 61
From: Thierry Reding
Most functions in libdrm_tegra take as first parameter the object that
they operate on. Make the device and buffer object creation functions
follow the same scheme.
Signed-off-by: Thierry Reding
---
tegra/tegra.c | 13 +++--
tegra/tegra.h | 10
From: Thierry Reding
All of the buffer object allocation functions use the same boilerplate
code. Move that code into a separate function that can be reused.
Signed-off-by: Thierry Reding
---
tegra/tegra.c | 35 ++-
1 file changed, 22 insertions(+), 13
From: Thierry Reding
The DRM_TEGRA_GEM_{GET,SET}_FLAGS and DRM_TEGRA_GEM_{GET,SET}_TILING
IOCTLs were badly designed and have since been obsoleted by framebuffer
modifiers. Remove these implementations to make it clear their usage is
discouraged.
Signed-off-by: Thierry Reding
---
From: Thierry Reding
Store 64-bit offset values and use libdrm's built-in drm_mmap() function
instead of mmap() to ensure the full 64-bit offset is used.
Signed-off-by: Thierry Reding
---
tegra/private.h | 2 +-
tegra/tegra.c | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff
From: Thierry Reding
Reindent the sources according to the settings found in the newly added
.editorconfig.
Signed-off-by: Thierry Reding
---
tegra/private.h | 18 +-
tegra/tegra.c | 354
tegra/tegra.h | 12 +-
From: Thierry Reding
Hi all,
this is the userspace part of the kernel patches that were recently
merged into drm-next:
https://patchwork.freedesktop.org/series/92378/
The goal is to provide a userspace implementation of the UAPI exposed by
the kernel and show its usage in some test programs
Hi Daniel,
On Thu, 26 Aug 2021 at 06:13, Daniel Vetter wrote:
>
> dri-devel is the main user, and somehow there's been the assumption
> that component stuff is unmaintained.
>
> References:
> https://lore.kernel.org/dri-devel/CAAEAJfDWOzCJxZFNtxeT7Cvr2pWbYrfz-YnA81sVNs-rM=8...@mail.gmail.com/
>
On 8/25/21 19:49, Ralph Campbell wrote:
>
> On 8/25/21 4:15 AM, Vlastimil Babka wrote:
>> On 8/25/21 05:48, Alex Sierra wrote:
>>> From: Ralph Campbell
>>>
>>> ZONE_DEVICE struct pages have an extra reference count that complicates the
>>> code for put_page() and several places in the kernel
https://bugzilla.kernel.org/show_bug.cgi?id=214199
--- Comment #1 from Zeljko (ker...@zeljko.anonaddy.com) ---
Created attachment 298499
--> https://bugzilla.kernel.org/attachment.cgi?id=298499=edit
Suspend dmesg
--
You may reply to this email to add a comment.
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=214199
Bug ID: 214199
Summary: Sapphire NITRO+ RX 580 4G G5 - Secondary display
doesn't wake up on boot, both displays won't wake up
from suspend
Product: Drivers
https://bugzilla.kernel.org/show_bug.cgi?id=214197
Bug ID: 214197
Summary: [Asus G713QY] RX6800M not usable after exiting Vulkan
application
Product: Drivers
Version: 2.5
Kernel Version: 5.13.13
Hardware: x86-64
Now that the fbdev core has been split in FB_CORE and FB, make DRM fbdev
emulation layer to just depend on the former.
This allows to disable the CONFIG_FB option if is not needed, which will
avoid the need to explicitly disable all the legacy fbdev drivers.
Signed-off-by: Javier Martinez
Currently the CONFIG_FB option has to be enabled even if no legacy fbdev
drivers are needed, in order to have support for a framebuffer console.
The DRM subsystem has a fbdev emulation layer, but depends on CONFIG_FB
and so it can only be enabled if that dependency is enabled as well.
That means
The framebuffer_alloc() and framebuffer_release() functions are much more
related with the functions in drivers/fbdev/core/fbmem.c than the ones in
drivers/fbdev/core/fbsysfs.c, that are only to manage sysfs attributes.
Signed-off-by: Javier Martinez Canillas
---
The fb_init_device() and fb_cleanup_device() functions only register and
unregister sysfs attributes as their initialization and cleanup logic.
Let's rename these functions to better match what they actually do.
There's only a call to dev_set_drvdata() that's not related to the sysfs
This patch series splits the fbdev core support in two different Kconfig
symbols: FB and FB_CORE. The motivation for this is to allow CONFIG_FB to
be disabled, while still using fbcon with the DRM fbdev emulation layer.
The reason for doing this is that now with simpledrm we could just boot
with
1 - 100 of 123 matches
Mail list logo
