Decomposing fence containers don't seem to make any sense here.
So just remove the function entirely and call dma_fence_wait() directly.
Signed-off-by: Christian König
Cc: VMware Graphics
Cc: Zack Rusin
---
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 2 +-
It's a reoccurring pattern that we need to extract the fence
from a dma_fence_chain object. Add a helper for this.
Signed-off-by: Christian König
---
drivers/dma-buf/dma-fence-chain.c | 6 ++
include/linux/dma-fence-chain.h | 15 +++
2 files changed, 17 insertions(+), 4
Instead of manually messing with the data structures use the iterators
and extraction helpers provided by the framework.
This whole handling should essentially go away when boost handling is
implemented in the core dma-buf framework.
Signed-off-by: Christian König
---
Instead of manually extracting the fence.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_sync.c
index
Chaining of dma_fence_chain objects is only allowed through the prev
fence and not through the contained fence.
Warn about that when we create a dma_fence_chain.
v2: fix comment style
Signed-off-by: Christian König
Reviewed-by: Daniel Vetter
Reviewed-by: Thomas Hellström
---
From: Christian König
Add a helper to iterate over all fences in a dma_fence_array object.
v2 (Jason Ekstrand)
- Return NULL from dma_fence_array_first if head == NULL. This matches
the iterator behavior of dma_fence_chain_for_each in that it iterates
zero times if head == NULL.
-
It's not allowed to nest another dma_fence container into a dma_fence_array
or otherwise we can run into recursion.
Warn about that when we create a dma_fence_array.
v2: fix comment style and typo in the warning pointed out by Thomas
Signed-off-by: Christian König
Reviewed-by: Daniel Vetter
Drivers should not add containers as shared fences to the dma_resv
object, instead each fence should be added individually.
Signed-off-by: Christian König
Reviewed-by: Daniel Vetter
---
drivers/dma-buf/dma-resv.c | 5 +
1 file changed, 5 insertions(+)
diff --git
Consolidate the wrapper functions to check for dma_fence
subclasses in the dma_fence header.
This makes it easier to document and also check the different
requirements for fence containers in the subclasses.
Signed-off-by: Christian König
---
include/linux/dma-fence-array.h | 15 +
On Mon, 2022-01-24 at 03:08 +0200, Andi Shyti wrote:
> Replace "linux/slab.h" with "linux/sched/mm.h" header inclusion
> as the first is not required, while the second, if not included,
> prdouces the following error:
>
> drivers/gpu/drm/i915/i915_vma_resource.c: In function
>
pm_runtime_get_sync() will increase the rumtime PM counter
even when it returns an error. Thus a pairing decrement is needed
to prevent refcount leak. Fix this by replacing this API with
pm_runtime_resume_and_get(), which will not change the runtime
PM counter on error. Besides, a matching
Hi, Nancy:
On Mon, 2022-01-10 at 16:46 +0800, Nancy.Lin wrote:
> Add driver data of mt8195 vdosys1 to mediatek-drm.
>
> Signed-off-by: Nancy.Lin
> ---
> drivers/gpu/drm/mediatek/mtk_drm_drv.c | 18 ++
> 1 file changed, 18 insertions(+)
>
> diff --git
Hi Marek,
Thanks for fixing it.
Inki Dae.
22. 1. 21. 19:00에 Marek Szyprowski 이(가) 쓴 글:
> TE-gpio is optional and if it is not found then gpiod_get_optional()
> returns NULL. In such case the code will continue and try to convert NULL
> gpiod to irq what in turn fails. The failure is then
The D-PHY specification (v1.2) explicitly mentions that the T-CLK-PRE
parameter's unit is Unit Interval(UI) and the minimum value is 8. Also,
kernel doc of the 'clk_pre' member of struct phy_configure_opts_mipi_dphy
mentions that it should be in UI. However, the dphy core driver wrongly
sets
The D-PHY specification (v1.2) explicitly mentions that the T-CLK-PRE
parameter's unit is Unit Interval(UI) and the minimum value is 8. Also,
kernel doc of the 'clk_pre' member of struct phy_configure_opts_mipi_dphy
mentions that it should be in UI. However, the dphy core driver wrongly
sets
Hi Laurent,
On Mon, 2022-01-24 at 00:15 +0200, Laurent Pinchart wrote:
> Hi Liu,
>
> Thank you for the patch.
Thank you for your review.
>
> On Wed, Jan 19, 2022 at 10:37:14AM +0800, Liu Ying wrote:
> > The D-PHY specification (v1.2) explicitly mentions that the T-CLK-PRE
> > parameter's unit
From: Ira Weiny
The default case leaves the buffer object mapped in error.
Add radeon_bo_kunmap() to that case to ensure the mapping is cleaned up.
Signed-off-by: Ira Weiny
---
NOTE: It seems like this function could use a fair bit of refactoring
but this is the easiest way to fix the actual
From: Ira Weiny
kmap() is being deprecated and this usage is local to the thread. Use
kmap_local_page() instead.
Signed-off-by: Ira Weiny
---
drivers/gpu/drm/radeon/radeon_ttm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c
From: Ira Weiny
kmap() is being deprecated and these instances are easy to convert to
kmap_local_page().
Furthermore, in gma_crtc_cursor_set() use the memcpy_from_page() helper
instead of an open coded use of kmap_local_page().
Signed-off-by: Ira Weiny
---
From: Ira Weiny
kmap() is being deprecated. So this comment could be misleading in the
future.
Change this comment to point to using kmap_local_page(). While here
remove 'we' from the comment.
Signed-off-by: Ira Weiny
---
drivers/gpu/drm/msm/msm_gem_submit.c | 4 ++--
1 file changed, 2
From: Ira Weiny
kmap() is being deprecated. These maps are thread local and can be
replaced with kmap_local_page().
Replace kmap() with kmap_local_page()
Signed-off-by: Ira Weiny
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff
From: Ira Weiny
The default case leaves the buffer object mapped in error.
Add amdgpu_bo_kunmap() to that case to ensure the mapping is cleaned up.
Signed-off-by: Ira Weiny
---
NOTE: It seems like this function could use a fair bit of refactoring
but this is the easiest way to fix the actual
From: Ira Weiny
Changes from V1:
Use memcpy_to_page() where appropriate
Rebased to latest
The kmap() call may cause issues with work being done with persistent memory.
For this and other reasons it is being deprecated.
This series starts by converting the last easy kmap() uses
From: Ira Weiny
kmap() is being deprecated and these usages are all local to the thread
so there is no reason kmap_local_page() can't be used.
Replace kmap() calls with kmap_local_page().
Signed-off-by: Ira Weiny
---
Changes for V2:
From Christoph Helwig
Prefer the use of
Replace "linux/slab.h" with "linux/sched/mm.h" header inclusion
as the first is not required, while the second, if not included,
prdouces the following error:
drivers/gpu/drm/i915/i915_vma_resource.c: In function
‘i915_vma_resource_bind_dep_await’:
drivers/gpu/drm/i915/i915_vma_resource.c:381:9:
Hello Esaki-san,
On Fri, Jan 14, 2022 at 07:17:51PM +0900, Tomohito Esaki wrote:
> If only linear modifier is advertised, since there are many drivers that
> only linear supported, the DRM core should handle this rather than
> open-coding in every driver. However, there are legacy drivers such as
Hello Esaki-san,
Thank you for the patch.
On Fri, Jan 14, 2022 at 07:17:53PM +0900, Tomohito Esaki wrote:
> The allow_fb_modifiers flag is unnecessary since it has been replaced
> with cannot_support_modifiers flag.
The new flag is fb_modifiers_not_supported, not
cannot_support_modifiers.
>
Hello Esaki-san,
Thank you for the patch.
On Fri, Jan 14, 2022 at 07:17:52PM +0900, Tomohito Esaki wrote:
> The LINEAR modifier is advertised as default if a driver doesn't specify
> modifiers.
>
> Signed-off-by: Tomohito Esaki
> ---
> drivers/gpu/drm/drm_plane.c | 15 ---
>
On Sun, Jan 23, 2022 at 10:27:56PM +, Michael Kelley (LINUX) wrote:
> From: Wei Liu Sent: Sunday, January 23, 2022 1:56 PM
> >
> > On Sun, Jan 16, 2022 at 09:53:06PM +, Haiyang Zhang wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: Michael Kelley (LINUX)
> > > > Sent:
From: Wei Liu Sent: Sunday, January 23, 2022 1:56 PM
>
> On Sun, Jan 16, 2022 at 09:53:06PM +, Haiyang Zhang wrote:
> >
> >
> > > -Original Message-
> > > From: Michael Kelley (LINUX)
> > > Sent: Sunday, January 16, 2022 2:19 PM
> > > To: KY Srinivasan ; Haiyang Zhang
> ; Stephen
>
Hi Liu,
Thank you for the patch.
On Wed, Jan 19, 2022 at 10:37:14AM +0800, Liu Ying wrote:
> The D-PHY specification (v1.2) explicitly mentions that the T-CLK-PRE
> parameter's unit is Unit Interval(UI) and the minimum value is 8. Also,
> kernel doc of the 'clk_pre' member of struct
On Sun, Jan 16, 2022 at 09:53:06PM +, Haiyang Zhang wrote:
>
>
> > -Original Message-
> > From: Michael Kelley (LINUX)
> > Sent: Sunday, January 16, 2022 2:19 PM
> > To: KY Srinivasan ; Haiyang Zhang
> > ; Stephen
> > Hemminger ; wei@kernel.org; Wei Hu
> > ; Dexuan
> > Cui ;
On Sonntag, 23. Jänner 2022 21:43:23 CET Luca Weiss wrote:
> With CONFIG_DRM_PANEL_EDP=y and CONFIG_DRM_KMS_HELPER=m the compilation
> fails:
>
> drivers/gpu/drm/panel/panel-edp.c:843: undefined reference to
> `drm_panel_dp_aux_backlight'
>
> Add a dependency on DRM_KMS_HELPER to fix this.
>
With CONFIG_DRM_PANEL_EDP=y and CONFIG_DRM_KMS_HELPER=m the compilation
fails:
drivers/gpu/drm/panel/panel-edp.c:843: undefined reference to
`drm_panel_dp_aux_backlight'
Add a dependency on DRM_KMS_HELPER to fix this.
Signed-off-by: Luca Weiss
---
I briefly tried "select DRM_KMS_HELPER" but
Hi Yongzhi,
Thank you for the patch.
On Wed, Jan 19, 2022 at 07:36:00AM -0800, Yongzhi Liu wrote:
> pm_runtime_get_sync() will increase the rumtime PM counter
> even it returns an error. Thus a pairing decrement is needed
> to prevent refcount leak. Fix this by replacing this API with
>
i915_pmu_cpu_online() calls cpumask_weight() to check if any bit of a
given cpumask is set. We can do it more efficiently with cpumask_empty()
because cpumask_empty() stops traversing the cpumask as soon as it finds
first set bit, while cpumask_weight() counts all bits unconditionally.
smp_request_block() in drivers/gpu/drm/msm/disp/mdp5/mdp5_smp.c calls
bitmap_weight() to check if any bit of a given bitmap is set. It's
better to use bitmap_empty() in that case because bitmap_empty() stops
traversing the bitmap as soon as it finds first set bit, while
bitmap_weight() counts all
The two macros FBTFT_REGISTER_DRIVER and FBTFT_REGISTER_SPI_DRIVER
contain quite some duplication: Both define an spi driver and an of device
table and the differences are quite subtle.
So create two new macros and use both twice.
Link:
If registering the platform driver fails, the function must not return
without undoing the spi driver registration first.
Fixes: c296d5f9957c ("staging: fbtft: core support")
Link:
https://lore.kernel.org/r/20220118181338.207943-1-u.kleine-koe...@pengutronix.de
Signed-off-by: Uwe Kleine-König
From: Alexander Martinz
Add initial support for the SHIFT SHIFT6mq (axolotl) based on
the sdm845-mtp DT.
Currently supported features:
* Buttons (power, volume)
* Bluetooth, DSPs and modem
* Display and GPU
* Touch
* UART
* USB peripheral mode
* WLAN
Co-developed-by: Caleb Connolly
Add SHIFT vendor prefix, SHIFT make various devices such as the SHIF6mq
phone.
Signed-off-by: Caleb Connolly
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
Add support for another variant of the rm69299 panel. This panel is
1080x2160 and is found in the shift-axolotl (SHIFT6mq).
Signed-off-by: Caleb Connolly
---
.../gpu/drm/panel/panel-visionox-rm69299.c| 281 ++
1 file changed, 221 insertions(+), 60 deletions(-)
diff --git
Document a new compatible string for the second panel variant.
Signed-off-by: Caleb Connolly
---
.../devicetree/bindings/display/panel/visionox,rm69299.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
The focaltech FTS driver supports several variants of focaltech touch
screens found in ~2018 era smartphones including a variant of the
PocoPhone F1 and the SHIFT6mq. This driver is loosely based on the
original driver from Focaltech but has been simplified and largely
reworked.
Signed-off-by:
Add devicetree bindings for the Focaltech FTS touchscreen drivers.
Signed-off-by: Caleb Connolly
---
.../input/touchscreen/focaltech,fts.yaml | 78 +++
1 file changed, 78 insertions(+)
create mode 100644
This series adds initial support for the SHIFT6mq. SHIFT are a sustainably
oriented device manufacturer who aim to build repairable devices with long
lifespans.
The SHIFT6mq is a Snapdragon 845 based device, it features a 1080p OLED panel,
8GB of RAM, 128GB of UFS storage and display port alt
devm_drm_dev_alloc() can't allocate structures that embed a structure
which then again embeds drm_device. Workaround this by adding a
driver_private pointer to struct mipi_dbi_dev which the driver can use for
its additional state.
Signed-off-by: Noralf Trønnes
---
include/drm/drm_mipi_dbi.h | 2
Hi,
This patchset adds a driver that will work with most MIPI DBI compatible
SPI panels out there.
It's a follow up on 'drm/tiny/st7735r: Match up with staging/fbtft
driver'[1] which aimed at making the st7735r driver work with all panels
adding DT properties.
Maxime gave[2] a good overview of
Add a driver that will work with most MIPI DBI compatible SPI panels.
This avoids adding a driver for every new MIPI DBI compatible controller
that is to be used by Linux. The 'model' Device Tree property contains the
name of the display and will be used to load a firmware file that contains
the
Add binding for MIPI DBI compatible SPI panels.
Signed-off-by: Noralf Trønnes
---
.../display/panel/panel-mipi-dbi-spi.yaml | 69 +++
1 file changed, 69 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/panel/panel-mipi-dbi-spi.yaml
diff --git
On Fri, 14 Jan 2022 15:02:06 -0800, Brian Norris wrote:
> This series fixes DP/HDMI audio for RK3399 Gru systems.
>
> First, there was a regression with the switch to SPDIF. Patch 1 can be
> taken separately as a regression fix if desired. But it's not quite so
> useful (at least on Chrome OS
Add support for the Solomon Goldentek Display Model: GKTW70SDAD1SD
to panel-simple.
The panel spec from Variscite can be found at:
https://www.variscite.com/wp-content/uploads/2017/12/VLCD-CAP-GLD-RGB.pdf
Signed-off-by: Oliver Graute
Reviewed-by: Marco Felsch
Reviewed-by: Fabio Estevam
---
Hello,
Thanks for CC me Adam.
On Fri, Jan 21, 2022 at 11:24:09AM -0600, Adam Ford wrote:
> On Wed, Dec 29, 2021 at 10:19 PM Charles Stevens wrote:
> >
> > Hi All,
> >
> > I am working on a platform based on the Renesas RZ/G2 SoC family.
> > This chip uses the rcar-du driver for the display. I
This is a note to let you know that I've just added the patch titled
dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
to the 5.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
This is a note to let you know that I've just added the patch titled
dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
to the 5.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the
This is a note to let you know that I've just added the patch titled
dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
to the 5.16-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
This is a note to let you know that I've just added the patch titled
dma_fence_array: Fix PENDING_ERROR leak in dma_fence_array_signaled()
to the 5.15-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of
Hi Biju,
Thank you for the patch.
On Wed, Jan 12, 2022 at 05:46:00PM +, Biju Das wrote:
> RZ/G2L LCDC does not have DU group registers. This patch allows
> accessing DU group registers for SoC's with group feature bit is
> set.
>
> Signed-off-by: Biju Das
> ---
>
Hi Biju,
Thank you for the patch.
On Wed, Jan 12, 2022 at 05:45:55PM +, Biju Das wrote:
> Number of RPF's VSP is different on R-Car and RZ/G2L
> R-Car Gen3 -> 5 RPF's
> R-Car Gen2 -> 4 RPF's
> RZ/G2L -> 2 RPF's
>
> Add num_rpf to struct rcar_du_device_info to support later
> SoC without
https://bugzilla.kernel.org/show_bug.cgi?id=211277
kolAflash (kolafl...@kolahilft.de) changed:
What|Removed |Added
Status|NEW |RESOLVED
On Fri, Jan 14, 2022 at 11:17:19AM +0100, Geert Uytterhoeven wrote:
> On Wed, Jan 12, 2022 at 6:46 PM Biju Das wrote:
> > Increase buff size for compatible variable to avoid stack corruption
> > with RZ/G2L SoC's(renesas,du-r9a07g044l) which requires a buff size
> > more than the current
Hi Biju,
Thank you for the patch.
On Wed, Jan 12, 2022 at 05:46:06PM +, Biju Das wrote:
> This driver supports the MIPI DSI encoder found in the RZ/G2L
> SoC. It currently supports DSI mode only.
>
> Signed-off-by: Biju Das
> ---
> drivers/gpu/drm/rcar-du/Kconfig | 7 +
>
On Tue, Dec 28, 2021 at 11:10 AM Jani Nikula wrote:
>
> Improve non-desktop quirk logging if the EDID indicates non-desktop. If
> both are set, note about redundant quirk. If there's no quirk but the
> EDID indicates non-desktop, don't log non-desktop is set to 0.
>
> Cc: Philipp Zabel
>
Now that there is support for the Microsoft VSDB for HMDs, remove the
non-desktop quirk for two devices that are verified to contain it in
their EDID: HPN-3515 and LEN-B800.
Presumably most of the other Windows Mixed Reality headsets contain it
as well, but there are ACR-7FCE and SEC-5194 devices
Add minimal support for parsing VSDBs documented in Microsoft's "EDID
extension for head-mounted and specialized monitors" [1]. The version
field and the desktop usage flag can be used to set the non_desktop
connector property.
[1]
when acpi=off is provided in bootarg, kernel crash with
[1.252739] BUG: kernel NULL pointer dereference, address: 0018
[1.258308] Call Trace:
[1.258490] ? acpi_walk_namespace+0x147/0x147
[1.258770] acpi_get_devices+0xe4/0x137
[1.258921] ? drm_core_init+0xc0/0xc0
when acpi=off is provided in bootarg, kernel crash with
[1.252739] BUG: kernel NULL pointer dereference, address: 0018
[1.258308] Call Trace:
[1.258490] ? acpi_walk_namespace+0x147/0x147
[1.258770] acpi_get_devices+0xe4/0x137
[1.258921] ? drm_core_init+0xc0/0xc0
67 matches
Mail list logo
