On 01/08/2024 11:29, Cristian Ciocaltea wrote:
>>> + interrupts:
>>> +minItems: 4
>>> +maxItems: 5
>>> +items:
>>> + - description: AVP Unit interrupt
>>> + - description: CEC interrupt
>>> + - description: eARC RX interrupt
>>> + - description: Main Unit interrupt
> -Original Message-
> From: Dmitry Baryshkov
> Sent: Wednesday, July 31, 2024 2:51 PM
> To: Murthy, Arun R
> Cc: dri-devel@lists.freedesktop.org; intel-...@lists.freedesktop.org
> Subject: Re: [PATCH] RFC: drm/drm_plane: Expose the plane capability and
> interoperability
>
> On Wed, 31
Hi Linus,
Regular weekly fixes. This is a bit larger than usual but doesn't seem
too crazy.
Most of it is vmwgfx changes that fix a bunch of issues with wayland
userspaces with dma-buf/external buffers and modesetting fixes.
Otherwise it's kinda spread out, v3d fixes some new ioctls, nouveau
has
In drm_client_modeset_probe(), the return value of drm_mode_duplicate() is
assigned to modeset->mode, which will lead to a possible NULL pointer
dereference on failure of drm_mode_duplicate(). Add a check to avoid npd.
Cc: sta...@vger.kernel.org
Fixes: cf13909aee05 ("drm/fb-helper: Move out modese
In ch7006_encoder_get_modes(), the return value of drm_mode_duplicate() is
used directly in drm_mode_probed_add(), which will lead to a NULL pointer
dereference on failure of drm_mode_duplicate(). Add a check to avoid npd.
Cc: sta...@vger.kernel.org
Fixes: 6ee738610f41 ("drm/nouveau: Add DRM drive
From: John Harrison
ARL and MTL share a single GSC firmware blob. However, ARL requires a
newer version of it.
So add differentiate of the PCI ids for ARL from MTL and create ARL as
a sub-platform of MTL. That way, all the existing workarounds and such
still treat ARL as MTL exactly as before. H
No functional modification involved.
./drivers/gpu/drm/amd/display/dc/dml2/dml21/src/dml2_core/dml2_core_shared.c:6463:166-167:
Unneeded semicolon.
Reported-by: Abaci Robot
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=9633
Signed-off-by: Jiapeng Chong
---
.../display/dc/dml2/dml21/s
https://bugzilla.kernel.org/show_bug.cgi?id=219117
Tim Huang (tim.hu...@amd.com) changed:
What|Removed |Added
CC||tim.hu...@amd.com
--- Com
在 2024/8/2 2:32, Kasireddy, Vivek 写道:
[Some people who received this message don't often get email from
vivek.kasire...@intel.com. Learn why this is important at
https://aka.ms/LearnAboutSenderIdentification ]
Hi Huan,
This patchset attempts to fix some errors in udmabuf and remove the
upi
On Wed, Jul 31, 2024 at 12:17:22PM GMT, Abhinav Kumar wrote:
> For cases where the crtc's connectors_changed was set without enable/active
> getting toggled , there is an atomic_enable() call followed by an
> atomic_disable() but without an atomic_mode_set().
>
> This results in a NULL ptr access
On 7/31/2024 5:17 AM, Thomas Zimmermann wrote:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so there's no
change in functionality or semantics.
Signed-off-by: Thomas Zimmermann
Cc: Neil Armstrong
Cc: Jessica Zhang
Reviewed-by
On 7/31/2024 5:17 AM, Thomas Zimmermann wrote:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so there's no
change in functionality or semantics.
Signed-off-by: Thomas Zimmermann
Cc: Neil Armstrong
Cc: Jessica Zhang
Reviewed-by
On 7/31/2024 5:17 AM, Thomas Zimmermann wrote:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so there's no
change in functionality or semantics.
Signed-off-by: Thomas Zimmermann
Cc: Neil Armstrong
Cc: Jessica Zhang
Reviewed-by
On 7/31/2024 5:17 AM, Thomas Zimmermann wrote:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so there's no
change in functionality or semantics.
Signed-off-by: Thomas Zimmermann
Cc: Neil Armstrong
Cc: Jessica Zhang
Reviewed-by
On 7/31/2024 5:17 AM, Thomas Zimmermann wrote:
Replace FB_BLANK_ constants with their counterparts from the
backlight subsystem. The values are identical, so there's no
change in functionality or semantics.
Signed-off-by: Thomas Zimmermann
Cc: Linus Walleij
Cc: Neil Armstrong
Cc: Jessica Z
On 8/1/24 22:34, Christophe JAILLET wrote:
If an error occurs after request_mem_region(), a corresponding
release_mem_region() should be called, as already done in the remove
function.
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Christophe JAILLET
I've applied it as-is (with the F
On 4/10/24 16:23, Niklas Schnelle wrote:
In a future patch HAS_IOPORT=n will disable inb()/outb() and friends at
compile time. We thus need to #ifdef functions and their callsites which
unconditionally use these I/O accessors. In the include/video/vga.h
these are conveniently all those functions
If an error occurs after request_mem_region(), a corresponding
release_mem_region() should be called, as already done in the remove
function.
Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
Signed-off-by: Christophe JAILLET
---
*Not* even compile tested only.
It is provided as-is
Changes in v2:
- App
On Fri, Jun 28, 2024 at 04:39:38PM GMT, Barnabás Czémán wrote:
> This patch series add dpu support for MSM8996/MSM8953 devices.
>
> Note, by default these platforms are still handled by the MDP5 driver
> unless the `msm.prefer_mdp5=false' parameter is provided.
Could you please provide a summary
On Thu, Aug 01, 2024 at 06:45:03PM GMT, Barnabás Czémán wrote:
> Should i resend this patch set?
No. It was the merge window.
>
> On June 28, 2024 4:39:38 PM GMT+02:00, "Barnabás Czémán"
> wrote:
> >This patch series add dpu support for MSM8996/MSM8953 devices.
> >
> >Note, by default these pl
Hi Huan,
> This patchset attempts to fix some errors in udmabuf and remove the
> upin_list structure.
>
> Some of this fix just gather the patches which I upload before.
>
> Patch1
> ===
> Try to remove page fault mmap and direct map it.
> Due to current udmabuf has already obtained and pinned t
Make sure that for external buffers mapping goes through the dma_buf
interface instead of trying to access pages directly.
External buffers might not provide direct access to readable/writable
pages so to make sure the bo's created from external dma_bufs can be
read dma_buf interface has to be use
The kms paths keep a persistent map active to read and compare the cursor
buffer. These maps can race with each other in simple scenario where:
a) buffer "a" mapped for update
b) buffer "a" mapped for compare
c) do the compare
d) unmap "a" for compare
e) update the cursor
f) unmap "a" for update
At
Fixed warning for the following:
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
'width' not described in 'drm_plane_size_hint'
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
Fixed warning for the following:
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
'width' not described in 'drm_plane_size_hint'
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
On Mon, Jul 29, 2024 at 10:15:55AM +0200, Ricard Wanderlof wrote:
>
> Hi,
>
> I submitted the patch below a while ago (two months) but as far as I can
> make out it has not been included. There was an initial concern from
> Dmitry Baryshkov which was subsequently addressed but no other objectio
https://bugzilla.kernel.org/show_bug.cgi?id=219117
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
https://bugzilla.kernel.org/show_bug.cgi?id=219118
Artem S. Tashkinov (a...@gmx.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
On Mon, Jul 29, 2024 at 11:36:24AM +0200, Philipp Stanner wrote:
> Hi everyone,
>
> Now that we've got the simplified PCI devres API available we can slowly
> start using it in drivers and step by step phase the more problematic
> API out.
>
> vboxvideo currently does not have a region request, s
Should i resend this patch set?
On June 28, 2024 4:39:38 PM GMT+02:00, "Barnabás Czémán"
wrote:
>This patch series add dpu support for MSM8996/MSM8953 devices.
>
>Note, by default these platforms are still handled by the MDP5 driver
>unless the `msm.prefer_mdp5=false' parameter is provided.
>
>S
https://bugzilla.kernel.org/show_bug.cgi?id=219118
Bug ID: 219118
Summary: Linux 6.10.x [drm:amdgpu_job_timedout [amdgpu]]
*ERROR* ring gfx timeout VM fault / GPU fault detected
Product: Drivers
Version: 2.5
Hardware: All
On Thu, Aug 1, 2024 at 3:26 PM Vladimir Lypak wrote:
>
> On Thu, Aug 01, 2024 at 01:52:32PM +0100, Connor Abbott wrote:
> > On Thu, Aug 1, 2024 at 1:25 PM Vladimir Lypak
> > wrote:
> > >
> > > On Mon, Jul 29, 2024 at 06:26:45PM +0100, Connor Abbott wrote:
> > > > On Thu, Jul 11, 2024 at 11:10 AM
While the sysfs entries for engines are added in intel_engines_init()
during driver load, the corresponding function intel_engines_release()
does not correctly get rid of them. This can lead to a UAF if, after
failed initialization (for example when gt is set wedged on init), we
try to access the e
We want to determine the size of the devcoredump before writing it out.
To that end, we will run the devcoredump printer with NULL data to get
the size, alloc data based on the generated offset, then run the
devcorecump again with a valid data pointer to print. This necessitates
not writing data t
The current algorithm to read out devcoredump is O(N*N) where N is the
size of coredump due to usage of the drm_coredump_printer in
xe_devcoredump_read. Switch to a O(N) algorithm which prints the
devcoredump into a readable format in snapshot work and update
xe_devcoredump_read to memcpy from the
Kernel BO's don't take a ref to the VM, we need the VM for the
delayed snapshot, so take a ref to the VM in delayed snapshot.
v2:
- Check for lrc_bo before taking a VM ref (CI)
- Check lrc_bo->vm before taking / dropping a VM ref (CI)
- Drop VM in xe_lrc_snapshot_free
v5:
- Fix commit message
Combine [1] [2] for complete series to speedup devcoredump and fix it.
[1] https://patchwork.freedesktop.org/series/136541/
[2] https://patchwork.freedesktop.org/series/136545/
Matthew Brost (3):
drm/xe: Take ref to VM in delayed snapshot
drm/printer: Allow NULL data in devcoredump printer
Hi Bjorn,
On 7/31/24 9:36 PM, Bjorn Helgaas wrote:
> On Mon, Jul 29, 2024 at 11:36:24AM +0200, Philipp Stanner wrote:
>> Hi everyone,
>>
>> Now that we've got the simplified PCI devres API available we can slowly
>> start using it in drivers and step by step phase the more problematic
>> API out.
Hi,
On 7/29/24 11:36 AM, Philipp Stanner wrote:
> Hi everyone,
>
> Now that we've got the simplified PCI devres API available we can slowly
> start using it in drivers and step by step phase the more problematic
> API out.
>
> vboxvideo currently does not have a region request, so it is a suitab
On 01/08/2024 04:25, Cristian Ciocaltea wrote:
> Driver makes use of the BIT() macro, but relies on the bits header being
> implicitly included.
>
> Explicitly pull the header in to avoid potential build failures in some
> configurations.
>
> While at it, reorder include directives alphabetically
ckchip,dw-hdmi-qp.yaml | 188
>>> +
>>> 1 file changed, 188 insertions(+)
>>>
>>
>> My bot found errors running 'make dt_binding_check' on your patch:
>
> This is because the referenced synopsys,dw-hdmi-qp.yaml is provided
-Original Message-
From: Brost, Matthew
Sent: Thursday, August 1, 2024 7:30 AM
To: Cavitt, Jonathan
Cc: intel...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
maarten.lankho...@linux.intel.com; Vivi, Rodrigo
Subject: Re: [PATCH v4 2/3] drm/printer: Allow NULL data in devcored
On Thu, Aug 01, 2024 at 08:00:21AM -0600, Cavitt, Jonathan wrote:
> -Original Message-
> From: Brost, Matthew
> Sent: Wednesday, July 31, 2024 5:03 PM
> To: Cavitt, Jonathan
> Cc: intel...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
> maarten.lankho...@linux.intel.com; Vivi,
On 2024-08-01, Jocelyn Falempe wrote:
> I think I can also register one console for each drm driver, which
> will simplify drm_log even further. (currently it would mean having a
> circular buffer and work function for each driver which is a bit too
> much).
Indeed.
> Do you know if there is a c
On Thu, Aug 01, 2024 at 11:05:21AM +0300, Jani Nikula wrote:
> On Wed, 31 Jul 2024, Matthew Brost wrote:
> > Useful to determine size of devcoreump before writing it out.
>
> I find it useful to have this special case documented, with an example,
> so it's easier to see how handy this really is.
On Thu, Aug 01, 2024 at 01:52:32PM +0100, Connor Abbott wrote:
> On Thu, Aug 1, 2024 at 1:25 PM Vladimir Lypak
> wrote:
> >
> > On Mon, Jul 29, 2024 at 06:26:45PM +0100, Connor Abbott wrote:
> > > On Thu, Jul 11, 2024 at 11:10 AM Vladimir Lypak
> > > wrote:
> > > >
> > > > On A5XX GPUs when pree
On 01/08/2024 11:29, Cristian Ciocaltea wrote:
> On 8/1/24 11:38 AM, Krzysztof Kozlowski wrote:> On 01/08/2024 04:05, Cristian
> Ciocaltea wrote:
>>> Add dt-binding schema containing the common properties for the Synopsys
>>> DesignWare HDMI QP TX controller.
>>>
>>> Note this is not a full dt-bin
n Ciocaltea ");
>>> +MODULE_DESCRIPTION("DW HDMI QP transmitter driver");
>>> +MODULE_LICENSE("GPL");
>>> +MODULE_ALIAS("platform:dw-hdmi-qp");
>>
>> That's not a platform driver. That does not look like driver at all,
&g
-Original Message-
From: Brost, Matthew
Sent: Wednesday, July 31, 2024 5:03 PM
To: Cavitt, Jonathan
Cc: intel...@lists.freedesktop.org; dri-devel@lists.freedesktop.org;
maarten.lankho...@linux.intel.com; Vivi, Rodrigo
Subject: Re: [PATCH v4 2/3] drm/printer: Allow NULL data in devcored
On 01/08/2024 12:51, John Ogness wrote:
On 2024-08-01, Jocelyn Falempe wrote:
* It uses a circular buffer so the console->write() callback is very
quick, and will never stall.
* Drawing is done asynchronously using a workqueue.
For CON_NBCON, neither of the above points are necessar
On Thu, Jul 11, 2024 at 10:00:19AM +, Vladimir Lypak wrote:
> Two fields of preempt_record which are used by CP aren't reset on
> resume: "data" and "info". This is the reason behind faults which happen
> when we try to switch to the ring that was active last before suspend.
> In addition those
For cloned outputs, don't pick a default resolution of 1024x768 as
most hardware can do better. Instead look through the modes of all
connectors to find a common mode for all of them.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/drm_client_modeset.c | 54 +---
1 f
On Thu, 01 Aug 2024, Thomas Zimmermann wrote:
> Hi
>
> Am 01.08.24 um 14:33 schrieb Jani Nikula:
>> On Mon, 01 Jul 2024, Xaver Hugl wrote:
>>> Am Do., 20. Juni 2024 um 22:22 Uhr schrieb Xaver Hugl
>>> :
Merging can only happen once a real world userspace application has
implemented sup
On Thu, Aug 1, 2024 at 1:25 PM Vladimir Lypak wrote:
>
> On Mon, Jul 29, 2024 at 06:26:45PM +0100, Connor Abbott wrote:
> > On Thu, Jul 11, 2024 at 11:10 AM Vladimir Lypak
> > wrote:
> > >
> > > On A5XX GPUs when preemption is used it's invietable to enter a soft
> > > lock-up state in which GPU
Hello everyone,
Hello, my name is Priyansu Rout I am from India. I am right now in my
second year of B. Tech in Computer Science and Engineering. I have been
developing in blockchain projects and now I would like to get experience in
X. Org, especially on the kernel level.
I am very much interest
Hi
Am 01.08.24 um 14:33 schrieb Jani Nikula:
On Mon, 01 Jul 2024, Xaver Hugl wrote:
Am Do., 20. Juni 2024 um 22:22 Uhr schrieb Xaver Hugl :
Merging can only happen once a real world userspace application has
implemented support for it. I'll try to do that sometime next week in
KWin
Here's th
On Mon, Jul 15, 2024 at 02:00:10PM -0700, Rob Clark wrote:
> On Thu, Jul 11, 2024 at 3:02 AM Vladimir Lypak
> wrote:
> >
> > Fine grain preemption (switching from/to points within submits)
> > requires extra handling in command stream of those submits, especially
> > when rendering with tiling (u
On Mon, 01 Jul 2024, Xaver Hugl wrote:
> Am Do., 20. Juni 2024 um 22:22 Uhr schrieb Xaver Hugl :
>> Merging can only happen once a real world userspace application has
>> implemented support for it. I'll try to do that sometime next week in
>> KWin
>
> Here's the promised implementation:
> https:/
On Thu, 01 Aug 2024, Martin Kepplinger-Novaković wrote:
> This makes debugging often easier.
>
> Signed-off-by: Martin Kepplinger-Novaković
>
> ---
> drivers/video/backlight/pwm_bl.c | 9 ++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
Please refrain from signing your mails like t
On Mon, Jul 29, 2024 at 06:26:45PM +0100, Connor Abbott wrote:
> On Thu, Jul 11, 2024 at 11:10 AM Vladimir Lypak
> wrote:
> >
> > On A5XX GPUs when preemption is used it's invietable to enter a soft
> > lock-up state in which GPU is stuck at empty ring-buffer doing nothing.
> > This appears as ful
https://bugzilla.kernel.org/show_bug.cgi?id=219117
Bug ID: 219117
Summary: amdgpu: amdgpu_device_ip_init failed
Product: Drivers
Version: 2.5
Kernel Version: 6.11.0-rc1
Hardware: All
OS: Linux
Status: NEW
Hi Dave, Sima,
here's the first PR for drm-misc-next for what will become Linux v6.12.
It's the ususal mix of new features and bug fixes. Nouveau got a larger
refactoring, there are some improvements within TTM, work on the panic
screen progresses, mgag200 now supports VBLANK interrupts.
Best reg
From: Yishai Hadas
Pass uverbs_attr_bundle as part of '.reg_user_mr_dmabuf' API instead of
udata.
This enables passing some new ioctl attributes to the drivers, as will
be introduced in the next patches for mlx5 driver.
Change the involved drivers accordingly.
Signed-off-by: Yishai Hadas
Sign
From: Yishai Hadas
Introduce the 'GET_DATA_DIRECT_SYSFS_PATH' ioctl to return the sysfs
path of the affiliated 'data direct' device for a given device.
Signed-off-by: Yishai Hadas
Signed-off-by: Leon Romanovsky
---
drivers/infiniband/hw/mlx5/std_types.c | 55 +++-
includ
From: Yishai Hadas
Add support for DMABUF MR registrations with Data-direct device.
Upon userspace calling to register a DMABUF MR with the data direct bit
set, the below algorithm will be followed.
1) Obtain a pinned DMABUF umem from the IB core using the user input
parameters (FD, offset, len
From: Yishai Hadas
Introduce the 'data direct' driver for a ConnectX-8 Data Direct device.
The 'data direct' driver functions as the affiliated DMA device for one
or more capable mlx5_ib devices. This DMA device, as the name suggests,
is used exclusively for DMA operations. It can be considered
From: Yishai Hadas
Add support for creating pinned DMABUF umem with a specified DMA device
instead of the DMA device of the given IB device.
This API will be utilized in the upcoming patches of the series when
multiple path DMAs are implemented.
Signed-off-by: Yishai Hadas
Signed-off-by: Leon
From: Yishai Hadas
Introduce an option to revoke DMABUF umem.
This option will retain the umem allocation while revoking its DMA
mapping. Furthermore, any subsequent attempts to map the pages should
fail once the umem has been revoked.
This functionality will be utilized in the upcoming patches
From: Yishai Hadas
Add the NET device initialization flow to utilize the 'data
direct' device.
When a NET mlx5_ib device is capable of 'data direct', the following
sequence of actions will occur:
- Find its affiliated 'data direct' VUID via a firmware command.
- Create its own private PD and 'da
From: Yishai Hadas
Add IFC related stuff for data direct.
Signed-off-by: Yishai Hadas
Signed-off-by: Leon Romanovsky
---
include/linux/mlx5/mlx5_ifc.h | 51 +++
1 file changed, 46 insertions(+), 5 deletions(-)
diff --git a/include/linux/mlx5/mlx5_ifc.h b/inclu
From: Leon Romanovsky
>From Yishai,
Overview
This patch series aims to enable multi-path DMA support, allowing an
mlx5 RDMA device to issue DMA commands through multiple paths. This
feature is critical for improving performance and reaching line rate
in certain environments where issuin
On Wed, 31 Jul 2024, Thomas Zimmermann wrote:
> Hi
>
> Am 31.07.24 um 14:56 schrieb Jani Nikula:
>> On Wed, 31 Jul 2024, Thomas Zimmermann wrote:
>>> Replace FB_BLANK_ constants with their counterparts from the
>>> backlight subsystem. The values are identical, so there's no
>>> change in functio
On 8/1/24 4:39 PM, Jani Nikula wrote:
> On Tue, 30 Jul 2024, Tejas Vipin wrote:
>> Add more functions that can benefit from being multi style and mark
>> older variants as deprecated to eventually convert all mipi_dsi functions
>> to multi style.
>
> What?
>
> Why would a lot of regular DSI c
On Thu, 01 Aug 2024, abid-sayyad wrote:
> Fixed warning for the following:
> ./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct
> member
> 'width' not described in 'drm_plane_size_hint'
> ./include/uapi/drm/drm_mode.h:869: warning: Function para
On Tue, 30 Jul 2024, Tejas Vipin wrote:
> Add more functions that can benefit from being multi style and mark
> older variants as deprecated to eventually convert all mipi_dsi functions
> to multi style.
What?
Why would a lot of regular DSI commands that are not exclusively used
for one time set
在 2024/8/1 18:50, Christian König 写道:
Am 01.08.24 um 12:45 schrieb Huan Yang:
The current udmabuf mmap uses a page fault mechanism to populate the
vma.
However, the current udmabuf has already obtained and pinned the folio
upon completion of the creation.This means that the physical memory h
Am Donnerstag, dem 01.08.2024 um 12:09 +0200 schrieb Uwe Kleine-König:
> Hello Martin,
>
> On Thu, Aug 01, 2024 at 09:52:01AM +, Kepplinger-Novakovic Martin
> wrote:
> > Am Donnerstag, dem 01.08.2024 um 11:26 +0200 schrieb Uwe Kleine-
> > König:
> > > On Thu, Aug 01, 2024 at 11:12:55AM +0200,
This makes debugging often easier.
Signed-off-by: Martin Kepplinger-Novaković
---
drivers/video/backlight/pwm_bl.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/video/backlight/pwm_bl.c b/drivers/video/backlight/pwm_bl.c
index f1005bd0c41e3..cc7e7af71891f
Am Donnerstag, dem 01.08.2024 um 11:26 +0200 schrieb Uwe Kleine-König:
> Hello Martin,
>
> On Thu, Aug 01, 2024 at 11:12:55AM +0200, Martin Kepplinger-Novaković
> wrote:
> > This makes debugging often easier.
> >
> > Signed-off-by: Martin Kepplinger-Novaković
> >
> > ---
> > drivers/video/backl
Fixed warning for the following:
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
'width' not described in 'drm_plane_size_hint'
./include/uapi/drm/drm_mode.h:869: warning: Function parameter or struct member
From: Marco Rodolfi
This patch also take account of the different resolution for the
aftermarket DeckHD panel, which hasn't been accounted for yet in kernel,
since these quirks are applied based on BIOS information + panel
resolution.
This patch correct that problem and make the panel oriented t
Am 01.08.24 um 12:45 schrieb Huan Yang:
Currently, there are three duplicate pieces of code that retrieve
sg_table and update uduf->sg.
Since the sgt is used to populate the page in both mmap and vmap.It is
necessary to ensure that ubuf->sg is set correctly.
That is a really bad idea. Why are
Hello,
syzbot found the following issue on:
HEAD commit:6342649c33d2 Merge tag 'block-6.11-20240726' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1443cb0398
kernel config: https://syzkaller.appspot.com/x/.config?x=5efb917b1462a973
das
Am 01.08.24 um 12:45 schrieb Huan Yang:
Currently vmap_udmabuf set page's array by each folio.
But, ubuf->folios is only contain's the folio's head page.
That mean we repeatedly mapped the folio head page to the vmalloc area.
This patch fix it, set each folio's page correct, so that pages ar
Am 01.08.24 um 12:45 schrieb Huan Yang:
When PAGE_SIZE 4096, MAX_PAGE_ORDER 10, 64bit machine,
page_alloc only support 4MB.
If above this, trigger this warn and return NULL.
udmabuf can change size limit, if change it to 3072(3GB), and then alloc
3GB udmabuf, will fail create.
[ 4080.876581] --
Hi Laurent Pinchart,
Thanks for the feedback.
> -Original Message-
> From: Laurent Pinchart
> Sent: Wednesday, July 31, 2024 2:47 PM
> Subject: Re: [PATCH v2 3/9] dt-bindings: display: renesas,rzg2l-du: Document
> RZ/G2UL DU bindings
>
> Hi Biju,
>
> On Mon, Jul 29, 2024 at 09:05:59AM
On 2024-08-01, Jocelyn Falempe wrote:
> * It uses a circular buffer so the console->write() callback is very
>quick, and will never stall.
> * Drawing is done asynchronously using a workqueue.
For CON_NBCON, neither of the above points are necessary. You can draw
directly from the write_thr
Am 01.08.24 um 12:45 schrieb Huan Yang:
The current udmabuf mmap uses a page fault mechanism to populate the vma.
However, the current udmabuf has already obtained and pinned the folio
upon completion of the creation.This means that the physical memory has
already been acquired, rather than bein
Currently, udmabuf handles folio by creating an unpin list to record
each folio obtained from the list and unpinning them when released. To
maintain this approach, many data structures have been established.
However, maintaining this type of data structure requires a significant
amount of memory a
This patchset attempts to fix some errors in udmabuf and remove the
upin_list structure.
Some of this fix just gather the patches which I upload before.
Patch1
===
Try to remove page fault mmap and direct map it.
Due to current udmabuf has already obtained and pinned the folio
upon completion of
Currently vmap_udmabuf set page's array by each folio.
But, ubuf->folios is only contain's the folio's head page.
That mean we repeatedly mapped the folio head page to the vmalloc area.
This patch fix it, set each folio's page correct, so that pages array
contains right page, and then map into vm
The current udmabuf mmap uses a page fault mechanism to populate the vma.
However, the current udmabuf has already obtained and pinned the folio
upon completion of the creation.This means that the physical memory has
already been acquired, rather than being accessed dynamically. The
current page f
When PAGE_SIZE 4096, MAX_PAGE_ORDER 10, 64bit machine,
page_alloc only support 4MB.
If above this, trigger this warn and return NULL.
udmabuf can change size limit, if change it to 3072(3GB), and then alloc
3GB udmabuf, will fail create.
[ 4080.876581] [ cut here ]
[ 4080.
Currently, there are three duplicate pieces of code that retrieve
sg_table and update uduf->sg.
Since the sgt is used to populate the page in both mmap and vmap.It is
necessary to ensure that ubuf->sg is set correctly.
This patch add a helper function, if ubuf->sg exist, just return it.
Or else,
On 2024-08-01, Jocelyn Falempe wrote:
> * I tried to use the new nbcon interface, but didn't get any message
> from the write_atomic() callback, but the goal is to use that when
> it's ready.
Be aware that the write_atomic() callback _must_ also print from NMI
context. write_thread() may be th
Hello Martin,
On Thu, Aug 01, 2024 at 09:52:01AM +, Kepplinger-Novakovic Martin wrote:
> Am Donnerstag, dem 01.08.2024 um 11:26 +0200 schrieb Uwe Kleine-König:
> > On Thu, Aug 01, 2024 at 11:12:55AM +0200, Martin Kepplinger-Novaković
> > wrote:
> > > diff --git a/drivers/video/backlight/pwm_bl
drm_log is a simple logger that uses the drm_client API to print the
kmsg boot log on the screen. This is not a full replacement to fbcon,
as it will only print the kmsg. It will never handle user input, or a
terminal because this is better done in userspace.
Design decisions:
* It uses the drm_c
Move the color conversions, blit and fill functions to drm_draw.c,
so that they can be re-used by drm_log.
drm_draw is internal to the drm subsystem, and shouldn't be used by
gpu drivers.
Signed-off-by: Jocelyn Falempe
---
drivers/gpu/drm/Kconfig | 5 +
drivers/gpu/drm/Makefile| 1 +
This is a squashed patch of:
https://patchwork.freedesktop.org/series/136377/
https://patchwork.freedesktop.org/series/135944/
This is to avoid to rebase when they are merged.
Signed-off-by: Jocelyn Falempe
---
drivers/gpu/drm/Kconfig | 31 +
drivers/gpu/drm/Makefile|
1 - 100 of 118 matches
Mail list logo
