On Sun, 23 Jan 2022, Yaroslav Bolyukin wrote:
> Per VESA DisplayID Standard v2.0: Type VII Timing – Detailed Timing Data
>
> Definitions were already provided as type I, but not used
>
> Signed-off-by: Yaroslav Bolyukin
Reviewed-by: Jani Nikula
> ---
> drivers/gpu/drm/drm_edid.c | 12
On Wed, Jan 19, 2022 at 11:36 PM Robert Foss wrote:
>
> Hey Hsin-Yi,
>
> While I can review this patch, I don't have the authority to merge it
> since it is outside the scope of my maintainership. Rob Herring,
> Daniel Vetter or David Airlie would have to Ack this patch.
hi Rob,
Can you help
Hello Laurent-san
Thank you for your reviews and advices.
I'll fix this patch series following your advice.
Thanks,
Esaki
On 2022/01/24 7:50, Laurent Pinchart wrote:
Hello Esaki-san,
On Fri, Jan 14, 2022 at 07:17:51PM +0900, Tomohito Esaki wrote:
If only linear modifier is advertised,
On Mon, Jan 24, 2022 at 03:24:09PM +0300, Dan Carpenter wrote:
> Smatch detected a divide by zero bug in check_overlay_scaling().
>
> drivers/gpu/drm/i915/display/intel_overlay.c:976 check_overlay_scaling()
> error: potential divide by zero bug '/ rec->dst_height'.
>
Hi, Bjorn,
Why this series still missing in 5.17-rc1? :(
Huacai
On Fri, Jan 7, 2022 at 12:21 AM Bjorn Helgaas wrote:
>
> On Thu, Jan 06, 2022 at 02:44:42PM +0800, Huacai Chen wrote:
> > On Thu, Jan 6, 2022 at 8:07 AM Bjorn Helgaas wrote:
> > > Previously we selected a device that owns the
On 13/01/2022 19:32, Rob Clark wrote:
From: Rob Clark
Reported-by: Danylo Piliaiev
Fixes: 3ab1c5cc3939 ("drm/msm: Add param for userspace to query suspend count")
Signed-off-by: Rob Clark
Reviewed-by: Dmitry Baryshkov
---
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 2 ++
1 file changed,
On 12/01/2022 15:33, Xianting Tian wrote:
For example, memory-region in .dts as below,
reg = <0x0 0x5000 0x0 0x2000>
We can get below values,
struct resource r;
r.start = 0x5000;
r.end = 0x6fff;
So the size should be:
size = r.end - r.start + 1 = 0x2000
On 16/01/2022 21:18, José Expósito wrote:
The function performs a check on the "phy" input parameter, however, it
is used before the check.
Initialize the "dev" variable after the sanity check to avoid a possible
NULL pointer dereference.
Fixes: 5c8290284402b ("drm/msm/dsi: Split PHY drivers
On 18/01/2022 23:38, Rajeev Nandan wrote:
Add support for MSM DSI PHY tuning configuration. Current design is
to support drive strength and drive level/amplitude tuning for
10nm PHY version, but this can be extended to other PHY versions.
Signed-off-by: Rajeev Nandan
Reviewed-by: Dmitry
On 18/01/2022 23:38, Rajeev Nandan wrote:
The clock and data lanes of the DSI PHY have a calibration circuitry
feature. As per the MSM DSI PHY tuning guidelines, the drive strength
tuning can be done by adjusting rescode offset for hstop/hsbot, and
the drive level tuning can be done by adjusting
Quoting Kuogee Hsieh (2022-01-24 14:44:52)
> DP driver is a generic driver which supports both eDP and DP.
> For debugging purpose it is required to have capabilities to
> differentiate message are generated from eDP or DP. This patch
> add connector type into debug messages for this purpose.
>
>
Some of DP link compliant test expects to return fail-safe mode
if prefer detailed timing mode can not be supported by mainlink's
lane and rate after link training. Therefore add fail-safe mode
into connector mode list as backup mode. This patch fixes test
case 4.2.2.1.
Changes in v2:
-- add
https://bugzilla.kernel.org/show_bug.cgi?id=201957
--- Comment #57 from Spencer (s...@nandre.com) ---
Created attachment 300315
--> https://bugzilla.kernel.org/attachment.cgi?id=300315=edit
Kernel config
OS: Gentoo
Kernel: 5.15.16, config attached, built with make -j12
Launch options:
Hi all,
Today's linux-next merge of the drm-intel-gt tree got a conflict in:
drivers/gpu/drm/i915/i915_drv.h
between commit:
2ef97818d3aa ("drm/i915: split out i915_gem_evict.h from i915_drv.h")
from the drm-intel tree and commit:
7e00897be8bf ("drm/i915: Add object locking to
https://bugzilla.kernel.org/show_bug.cgi?id=215436
--- Comment #28 from mario.limoncie...@amd.com ---
As this is now in 5.17-rc1:
https://github.com/torvalds/linux/commit/c4849f88164b13dd141885e28210f599741b304b
this issue can be closed.
--
You may reply to this email to add a comment.
You are
DP driver is a generic driver which supports both eDP and DP.
For debugging purpose it is required to have capabilities to
differentiate message are generated from eDP or DP. This patch
add connector type into debug messages for this purpose.
Signed-off-by: Kuogee Hsieh
---
On Mon, Jan 24, 2022 at 11:37:03PM +0100, Helge Deller wrote:
> On 1/24/22 23:19, Daniel Vetter wrote:
> > On Mon, Jan 24, 2022 at 10:03:17PM +0100, Helge Deller wrote:
> >> This series reverts two patches which disabled scrolling acceleration in
> >> fbcon/fbdev. Those patches introduced a
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/intel_pm.c
between commit:
cca084692394 ("drm/i915: Use per device iommu check")
from Linus' tree and commit:
8172375ea95a ("drm/i915: Remove zombie async flip vt-d w/a")
from the drm-intel
On 1/24/22 23:19, Daniel Vetter wrote:
> On Mon, Jan 24, 2022 at 10:03:17PM +0100, Helge Deller wrote:
>> This series reverts two patches which disabled scrolling acceleration in
>> fbcon/fbdev. Those patches introduced a regression for fbdev-supported
>> graphic
>> cards because of the
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/i915_reg.h
between commit:
77cdd054dd2c ("drm/i915/pmu: Connect engine busyness stats from GuC to pmu")
from Linus' tree and commit:
202b1f4c1234 ("drm/i915/gt: Move engine registers to their
On Mon, Jan 24, 2022 at 10:03:17PM +0100, Helge Deller wrote:
> This series reverts two patches which disabled scrolling acceleration in
> fbcon/fbdev. Those patches introduced a regression for fbdev-supported graphic
> cards because of the performance penalty by doing screen scrolling by software
On Mon, Jan 24, 2022 at 5:16 PM Daniel Vetter wrote:
>
> Also add notes that for atomic drivers it's really somewhere else and
> no longer in struct drm_crtc.
>
> Maybe we should put a bigger warning here that this is confusing,
> since the pixel format is a plane property, but the GAMMA_LUT
Also add notes that for atomic drivers it's really somewhere else and
no longer in struct drm_crtc.
Maybe we should put a bigger warning here that this is confusing,
since the pixel format is a plane property, but the GAMMA_LUT property
is on the crtc. But I think we can fix this if/when someone
Applied. Thanks!
Alex
On Mon, Jan 24, 2022 at 10:25 AM Harry Wentland wrote:
>
> On 2022-01-21 20:23, Randy Dunlap wrote:
> > Change a static function's comment from "/**" (indicating kernel-doc
> > notation) to "/*" (indicating a regular C language comment).
> > This prevents multiple
Applied. Thanks!
Alex
On Mon, Jan 24, 2022 at 3:21 PM Nick Desaulniers
wrote:
>
> On Wed, Jan 19, 2022 at 2:46 PM Colin Ian King wrote:
> >
> > The pointer reg is being assigned a value that is not read, the
> > exit path via label 'out' never accesses it. The assignment is
> > redundant and
Applied. Thanks!
Alex
On Mon, Jan 24, 2022 at 3:18 PM wrote:
>
> From: Tom Rix
>
> clang static analysis reports this represenative problem
> amdgpu_smu.c:144:18: warning: The left operand of '*' is a garbage value
> return clk_freq * 100;
> ^
>
> If there is
Quoting Kuogee Hsieh (2022-01-24 13:24:25)
>
> On 1/24/2022 1:04 PM, Stephen Boyd wrote:
> > Quoting Kuogee Hsieh (2022-01-24 12:46:10)
> >> Some of DP link compliant test expects to return fail-safe mode
> >> if prefer detailed timing mode can not be supported by mainlink's
> >> lane and rate
On 1/24/2022 1:04 PM, Stephen Boyd wrote:
Quoting Kuogee Hsieh (2022-01-24 12:46:10)
Some of DP link compliant test expects to return fail-safe mode
if prefer detailed timing mode can not be supported by mainlink's
lane and rate after link training. Therefore add fail-safe mode
into connector
From: Robin Murphy
[ Upstream commit 5566174cb10a5167d59b0793871cab7990b149b8 ]
Upon failure, dma_alloc_coherent() returns NULL. If that does happen,
passing some uninitialised stack contents to dma_mapping_error() - which
belongs to a different API in the first place - has precious little
This reverts commit b3ec8cdf457e5e63d396fe1346cc788cf7c1b578.
Revert the second (of 2) commits which disabled scrolling acceleration
in fbcon/fbdev. It introduced a regression for fbdev-supported graphic
cards because of the performance penalty by doing screen scrolling by
software instead of
This reverts commit 39aead8373b3c20bb5965c024dfb51a94e526151.
Revert the first (of 2) commits which disabled scrolling acceleration in
fbcon/fbdev. It introduced a regression for fbdev-supported graphic cards
because of the performance penalty by doing screen scrolling by software
instead of
This series reverts two patches which disabled scrolling acceleration in
fbcon/fbdev. Those patches introduced a regression for fbdev-supported graphic
cards because of the performance penalty by doing screen scrolling by software
instead of using existing 2D hardware acceleration.
This series
Quoting Kuogee Hsieh (2022-01-24 12:46:10)
> Some of DP link compliant test expects to return fail-safe mode
> if prefer detailed timing mode can not be supported by mainlink's
> lane and rate after link training. Therefore add fail-safe mode
> into connector mode list as backup mode. This patch
From: Thomas Hellström
commit 95d35838880fb040ccb9fe4a48816bd0c8b62df5 upstream.
If a dma_fence_array is reported signaled by a call to
dma_fence_is_signaled(), it may leak the PENDING_ERROR status.
Fix this by clearing the PENDING_ERROR status if we return true in
dma_fence_array_signaled().
On Mon, Jan 24, 2022 at 9:41 PM Laurent Pinchart
wrote:
>
> Hi Daniel,
>
> On Mon, Jan 24, 2022 at 09:28:09PM +0100, Daniel Vetter wrote:
> > On Mon, Jan 24, 2022 at 9:24 PM Laurent Pinchart wrote:
> > > On Mon, Jan 24, 2022 at 08:47:06PM +0100, Daniel Vetter wrote:
> > > > Also add notes that
Some of DP link compliant test expects to return fail-safe mode
if prefer detailed timing mode can not be supported by mainlink's
lane and rate after link training. Therefore add fail-safe mode
into connector mode list as backup mode. This patch fixes test
case 4.2.2.1.
Signed-off-by: Kuogee
Hi Daniel,
On Mon, Jan 24, 2022 at 09:28:09PM +0100, Daniel Vetter wrote:
> On Mon, Jan 24, 2022 at 9:24 PM Laurent Pinchart wrote:
> > On Mon, Jan 24, 2022 at 08:47:06PM +0100, Daniel Vetter wrote:
> > > Also add notes that for atomic drivers it's really somewhere else and
> > > no longer in
On Mon, Jan 24, 2022 at 9:24 PM Laurent Pinchart
wrote:
>
> Hi Daniel,
>
> Thank you for the patch.
>
> On Mon, Jan 24, 2022 at 08:47:06PM +0100, Daniel Vetter wrote:
> > Also add notes that for atomic drivers it's really somewhere else and
> > no longer in struct drm_crtc.
> >
> > Maybe we
Hi Daniel,
Thank you for the patch.
On Mon, Jan 24, 2022 at 08:47:06PM +0100, Daniel Vetter wrote:
> Also add notes that for atomic drivers it's really somewhere else and
> no longer in struct drm_crtc.
>
> Maybe we should put a bigger warning here that this is confusing,
> since the pixel
From: Robin Murphy
[ Upstream commit 5566174cb10a5167d59b0793871cab7990b149b8 ]
Upon failure, dma_alloc_coherent() returns NULL. If that does happen,
passing some uninitialised stack contents to dma_mapping_error() - which
belongs to a different API in the first place - has precious little
Am 24.01.22 um 17:36 schrieb Thomas Hellström (Intel):
On 1/24/22 14:03, Christian König wrote:
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
Am 24.01.22 um 17:33 schrieb Thomas Hellström:
On Mon, 2022-01-24 at 14:03 +0100, Christian König wrote:
Instead of calling the debug operation directly.
Signed-off-by: Christian König
Reviewed-by: Huang Rui
The first two patches seem unrelated to the series.
No idea what happened here,
From: Tom Rix
clang static analysis reports this represenative problem
amdgpu_smu.c:144:18: warning: The left operand of '*' is a garbage value
return clk_freq * 100;
^
If there is no get_dpm_ultimate_freq function,
smu_get_dpm_freq_range returns success without
From: Thomas Hellström
commit 95d35838880fb040ccb9fe4a48816bd0c8b62df5 upstream.
If a dma_fence_array is reported signaled by a call to
dma_fence_is_signaled(), it may leak the PENDING_ERROR status.
Fix this by clearing the PENDING_ERROR status if we return true in
dma_fence_array_signaled().
Applied. Thanks!
Alex
On Mon, Jan 24, 2022 at 12:05 PM Zhou Qingyang wrote:
>
> In amdgpu_dm_connector_add_common_modes(), amdgpu_dm_create_common_mode()
> is assigned to mode and is passed to drm_mode_probed_add() directly after
> that. drm_mode_probed_add() passes >head to list_add_tail(),
On Mon, Jan 24, 2022 at 7:27 PM Geert Uytterhoeven wrote:
>
> Hi Daniel et al,
>
> On Wed, Jan 19, 2022 at 4:39 PM Daniel Vetter wrote:
> > On Thu, Jan 13, 2022 at 10:46:03PM +0100, Sven Schnelle wrote:
> > > Helge Deller writes:
> > > > I may have missed some discussions, but I'm objecting
From: Robin Murphy
[ Upstream commit 5566174cb10a5167d59b0793871cab7990b149b8 ]
Upon failure, dma_alloc_coherent() returns NULL. If that does happen,
passing some uninitialised stack contents to dma_mapping_error() - which
belongs to a different API in the first place - has precious little
Also add notes that for atomic drivers it's really somewhere else and
no longer in struct drm_crtc.
Maybe we should put a bigger warning here that this is confusing,
since the pixel format is a plane property, but the GAMMA_LUT property
is on the crtc. But I think we can fix this if/when someone
From: Thomas Hellström
commit 95d35838880fb040ccb9fe4a48816bd0c8b62df5 upstream.
If a dma_fence_array is reported signaled by a call to
dma_fence_is_signaled(), it may leak the PENDING_ERROR status.
Fix this by clearing the PENDING_ERROR status if we return true in
dma_fence_array_signaled().
On Mon, Jan 24, 2022 at 7:51 PM Geert Uytterhoeven wrote:
>
> Hi Daniel,
>
> On Thu, Jan 20, 2022 at 1:33 PM Daniel Vetter wrote:
> > But reading code is too hard I guess, safer to assume it's just
> > broken and not supported.
>
> I confirm there's lots of documentation (and even more code ;-),
From: Thomas Hellström
commit 95d35838880fb040ccb9fe4a48816bd0c8b62df5 upstream.
If a dma_fence_array is reported signaled by a call to
dma_fence_is_signaled(), it may leak the PENDING_ERROR status.
Fix this by clearing the PENDING_ERROR status if we return true in
dma_fence_array_signaled().
Applied. Thanks!
Alex
On Mon, Jan 24, 2022 at 12:05 PM Zhou Qingyang wrote:
>
> In calculate_bandwidth(), the tag free_sclk and free_yclk are reversed,
> which could lead to a memory leak of yclk.
>
> Fix this bug by changing the location of free_sclk and free_yclk.
>
> This bug was found by a
Hi,
On Mon, Jan 24, 2022 at 10:16 AM Sankeerth Billakanti
wrote:
>
> Add eDP panel support for sc7280 CRD platform.
>
> Signed-off-by: Sankeerth Billakanti
> ---
> drivers/gpu/drm/panel/panel-edp.c | 11 +++
> 1 file changed, 11 insertions(+)
>
> diff --git
Hi
Am 24.01.22 um 19:38 schrieb Geert Uytterhoeven:
Hi Daniel,
On Fri, Jan 21, 2022 at 9:55 AM Daniel Vetter wrote:
Just to clarify, since we had lots of smaller and bigger
misunderstandings in the thread thus far: DRM_FORMAT_RGB332 exists, so
drm support that already. The fbdev emulation
Hi,
On Mon, Jan 24, 2022 at 10:15 AM Sankeerth Billakanti
wrote:
>
> Enable the eDP display panel support with backlight on sc7280 platform.
>
> Signed-off-by: Sankeerth Billakanti
> ---
> arch/arm64/boot/dts/qcom/sc7280-crd.dts | 127
>
> 1 file changed, 127
Hi Daniel,
On Thu, Jan 20, 2022 at 1:33 PM Daniel Vetter wrote:
> But reading code is too hard I guess, safer to assume it's just
> broken and not supported.
I confirm there's lots of documentation (and even more code ;-),
which is always great!
But both are intimidating to me, and most of the
On Mon, Jan 24, 2022 at 7:39 PM Geert Uytterhoeven wrote:
>
> Hi Daniel,
>
> On Fri, Jan 21, 2022 at 9:55 AM Daniel Vetter wrote:
> > Just to clarify, since we had lots of smaller and bigger
> > misunderstandings in the thread thus far: DRM_FORMAT_RGB332 exists, so
> > drm support that already.
Hi Daniel,
On Fri, Jan 21, 2022 at 9:55 AM Daniel Vetter wrote:
> Just to clarify, since we had lots of smaller and bigger
> misunderstandings in the thread thus far: DRM_FORMAT_RGB332 exists, so
> drm support that already. The fbdev emulation doesn't yet, but all
> that's needed for that is
Hi Daniel et al,
On Wed, Jan 19, 2022 at 4:39 PM Daniel Vetter wrote:
> On Thu, Jan 13, 2022 at 10:46:03PM +0100, Sven Schnelle wrote:
> > Helge Deller writes:
> > > I may have missed some discussions, but I'm objecting against this patch:
> > >
> > > b3ec8cdf457e5 ("fbdev: Garbage collect
On Mon, Jan 24, 2022 at 01:08:26PM +0100, Christian König wrote:
> Am 24.01.22 um 02:54 schrieb ira.we...@intel.com:
> > From: Ira Weiny
> >
> > Changes from V1:
> > Use memcpy_to_page() where appropriate
> > Rebased to latest
> >
> > The kmap() call may cause issues with work being
Add eDP panel support for sc7280 CRD platform.
Signed-off-by: Sankeerth Billakanti
---
drivers/gpu/drm/panel/panel-edp.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/panel/panel-edp.c
b/drivers/gpu/drm/panel/panel-edp.c
index 176ef0c..bb2e346 100644
---
Enable the eDP display panel support with backlight on sc7280 platform.
Signed-off-by: Sankeerth Billakanti
---
arch/arm64/boot/dts/qcom/sc7280-crd.dts | 127
1 file changed, 127 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/sc7280-crd.dts
Add support for the eDP panel on sc7280 CRD platform.
These changes are dependent on the following series:
https://patchwork.kernel.org/project/linux-arm-msm/list/?series=586263=both=*
https://patchwork.kernel.org/project/linux-arm-msm/list/?series=560587=%2A=both
Sankeerth Billakanti (2):
This makes sense given the other patches in your series, but it seems as
yet no one has anything to say about this. I don't have anything
specific to comment on other than it seems to make the correct changes
to komeda given the rest.
Reviewed-by: Carsten Haitzler
On 1/11/22 10:18, Kandpal,
Seems fine.
Reviewed-by: Carsten Haitzler
On 12/15/21 00:59, Javier Martinez Canillas wrote:
According to disable Documentation/admin-guide/kernel-parameters.txt, this
parameter can be used to disable kernel modesetting.
DRM drivers will not perform display-mode changes or accelerated
Seems fine.
Reviewed-by: Carsten Haitzler
On 12/15/21 00:59, Javier Martinez Canillas wrote:
According to disable Documentation/admin-guide/kernel-parameters.txt, this
parameter can be used to disable kernel modesetting.
DRM drivers will not perform display-mode changes or accelerated
Seems fine to me.
Reviewed-by: Carsten Haitzler
On 12/15/21 00:59, Javier Martinez Canillas wrote:
According to disable Documentation/admin-guide/kernel-parameters.txt, this
parameter can be used to disable kernel modesetting.
DRM drivers will not perform display-mode changes or accelerated
On Sat, Jan 22, 2022 at 11:44 AM Nick Lopez wrote:
>
> Bounds checking when parsing init scripts embedded in the BIOS reject
> access to the last byte. This causes driver initialization to fail on
> Apple eMac's with GeForce 2 MX GPUs, leaving the system with no working
> console.
>
> This is
Den 24.01.2022 17.42, skrev Rob Herring:
> On Mon, Jan 24, 2022 at 10:28 AM Noralf Trønnes wrote:
>>
>>
>>
>> Den 24.01.2022 17.08, skrev Rob Herring:
>>> On Sun, Jan 23, 2022 at 11:25 AM Noralf Trønnes wrote:
Add binding for MIPI DBI compatible SPI panels.
>>>
>>> I'm sure we
From: Chris Morgan
Add support for the VC4 DPI driver to utilize DPI mode 3. This is
defined here as xxxRxxGGxxxB:
https://www.raspberrypi.com/documentation/computers/raspberry-pi.html#parallel-display-interface-dpi
This mode is required to use the Geekworm MZP280 DPI display.
From: Chris Morgan
The Geekworm MZP280 panel is a 480x640 (portrait) panel with a
capacitive touch interface and a 40 pin header meant to interface
directly with the Raspberry Pi. The screen is 2.8 inches diagonally,
and there appear to be at least 4 distinct versions all with the same
panel
From: Chris Morgan
Add vendor prefix for Geekworm (https://geekworm.com).
Signed-off-by: Chris Morgan
---
Documentation/devicetree/bindings/vendor-prefixes.yaml | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.yaml
From: Chris Morgan
Add support for the Geekworm MZP280 Panel
Signed-off-by: Chris Morgan
Acked-by: Maxime Ripard
---
drivers/gpu/drm/panel/panel-simple.c | 29
1 file changed, 29 insertions(+)
diff --git a/drivers/gpu/drm/panel/panel-simple.c
From: Chris Morgan
Add the MEDIA_BUS_FMT_RGB565_1X24_CPADHI format used by the Geekworm
MZP280 panel for the Raspberry Pi.
Signed-off-by: Chris Morgan
---
include/uapi/linux/media-bus-format.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git
From: Chris Morgan
Add support for MEDIA_BUS_FMT_RGB565_1X24_CPADHI. This format is used
by the Geekworm MZP280 panel which interfaces with the Raspberry Pi.
Signed-off-by: Chris Morgan
---
.../media/v4l/subdev-formats.rst | 37 +++
1 file changed, 37
From: Chris Morgan
This patch series is to add support for the MZP280 panel for the
Raspberry Pi. This panel requires adding support for Mode 3 of the
Raspberry Pi DPI connector, which necessitates a new media bus format.
This patch series has been tested on my Raspberry Pi 4 with version 1
of
On 1/24/22 14:03, Christian König wrote:
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
Reviewed-by: Thomas Hellström
---
drivers/dma-buf/dma-fence-chain.c | 6 ++
On Mon, Jan 24, 2022 at 10:28 AM Noralf Trønnes wrote:
>
>
>
> Den 24.01.2022 17.08, skrev Rob Herring:
> > On Sun, Jan 23, 2022 at 11:25 AM Noralf Trønnes wrote:
> >>
> >> Add binding for MIPI DBI compatible SPI panels.
> >
> > I'm sure we already have MIPI DBI panels. What's this for?
> >
>
>
On 1/24/22 14:03, Christian König wrote:
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
Reviewed-by: Thomas Hellström
Is there any indication that this
On Mon, 2022-01-24 at 14:03 +0100, Christian König wrote:
> Instead of calling the debug operation directly.
>
> Signed-off-by: Christian König
> Reviewed-by: Huang Rui
The first two patches seem unrelated to the series. Also is there a
chance of a series cover-letter?
Thanks,
Thomas
> ---
On Mon, 2022-01-24 at 14:03 +0100, Christian König wrote:
> 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
Den 24.01.2022 17.08, skrev Rob Herring:
> On Sun, Jan 23, 2022 at 11:25 AM Noralf Trønnes wrote:
>>
>> Add binding for MIPI DBI compatible SPI panels.
>
> I'm sure we already have MIPI DBI panels. What's this for?
>
It aims to use one driver to cover all MIPI DBI panels where the
I sent an updated patch with the Fixes:
On 1/24/22 16:13, Steven Price wrote:
On 24/01/2022 15:13, carsten.haitz...@foss.arm.com wrote:
From: Carsten Haitzler
Without DRM_GEM_CMA_HELPER HDLCD won't build. This needs to be there too.
Signed-off-by: Carsten Haitzler
To add the context,
From: Carsten Haitzler
Without DRM_GEM_CMA_HELPER HDLCD won't build. This needs to be there too.
Fixes: 09717af7d13d ("drm: Remove CONFIG_DRM_KMS_CMA_HELPER option")
Signed-off-by: Carsten Haitzler
---
drivers/gpu/drm/arm/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
On 24/01/2022 15:13, carsten.haitz...@foss.arm.com wrote:
> From: Carsten Haitzler
>
> Without DRM_GEM_CMA_HELPER HDLCD won't build. This needs to be there too.
>
> Signed-off-by: Carsten Haitzler
To add the context, DRM_HDLCD used to select DRM_KMS_CMA_HELPER but that
was removed in commit
Hi
Am 24.01.22 um 16:50 schrieb Geert Uytterhoeven:
On Mon, Jan 24, 2022 at 12:33 PM Thomas Zimmermann wrote:
With fbdev emulation, every DRM driver is an fbdev driver too. So
Some are even without?
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c: ret = register_framebuffer(info);
Well, I counted
On Sun, Jan 23, 2022 at 11:25 AM Noralf Trønnes wrote:
>
> Add binding for MIPI DBI compatible SPI panels.
I'm sure we already have MIPI DBI panels. What's this for?
>
> Signed-off-by: Noralf Trønnes
> ---
> .../display/panel/panel-mipi-dbi-spi.yaml | 69 +++
> 1 file
On Sun, Jan 23, 2022 at 05:54:05PM -0800, ira.we...@intel.com wrote:
> 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
On Sun, 23 Jan 2022 17:37:27 +, Caleb Connolly wrote:
> 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
On Sun, 23 Jan 2022 18:25:18 +0100, Noralf Trønnes wrote:
> 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
>
On Mon, 2022-01-24 at 13:36 +0100, Thomas Zimmermann wrote:
> From: Javier Martinez Canillas
>
> The sysfb_create_simplefb() function requests a IO memory resource for
> the
> simple-framebuffer platform device, but it also marks it as busy which
> can
> lead to drivers requesting the same
On Mon, 2022-01-24 at 13:36 +0100, Thomas Zimmermann wrote:
> Hot-unplug all firmware-framebuffer devices as part of removing
> them via remove_conflicting_framebuffers() et al. Releases all
> memory regions to be acquired by native drivers.
>
> Firmware, such as EFI, install a framebuffer while
Sorry - I meant disregard THIS one - following patch is right.
On 1/24/22 14:58, carsten.haitz...@foss.arm.com wrote:
From: Carsten Haitzler
Without DRM_GEM_CMA_HELPER HDLCD won't build. This needs to be there too.
Signed-off-by: Carsten Haitzler
---
drivers/gpu/drm/arm/Kconfig | 1 +
1
On Mon, Jan 24, 2022 at 04:29:34PM +0100, Helge Deller wrote:
> On 1/24/22 12:50, Javier Martinez Canillas wrote:
> > On 1/24/22 12:33, Thomas Zimmermann wrote:
> >
> > [snip]
> >
> >>> Thoughts?
> >>
> >> I can't say I approve keeping fbdev alive, but...
> >>
> >> With fbdev emulation, every DRM
On Mon, Jan 24, 2022 at 12:33 PM Thomas Zimmermann wrote:
> With fbdev emulation, every DRM driver is an fbdev driver too. So
Some are even without?
drivers/gpu/drm/vmwgfx/vmwgfx_fb.c: ret = register_framebuffer(info);
Gr{oetje,eeting}s,
Geert
--
Geert
Hi Helge,
On Mon, Jan 24, 2022 at 4:30 PM Helge Deller wrote:
> On 1/24/22 12:50, Javier Martinez Canillas wrote:
> > On 1/24/22 12:33, Thomas Zimmermann wrote:
> >
> > [snip]
> >
> >>> Thoughts?
> >>
> >> I can't say I approve keeping fbdev alive, but...
> >>
> >> With fbdev emulation, every
On 1/24/22 14:02, Maarten Lankhorst wrote:
set_cache_level may unbind the object, which will result in the below
lockdep splat:
<6> [184.578145] [IGT] kms_addfb_basic: starting subtest
addfb25-framebuffer-vs-set-tiling
<4> [184.578220] [ cut here ]
<4> [184.578221]
Hi
Am 24.01.22 um 16:29 schrieb Helge Deller:
On 1/24/22 12:50, Javier Martinez Canillas wrote:
On 1/24/22 12:33, Thomas Zimmermann wrote:
[snip]
Thoughts?
I can't say I approve keeping fbdev alive, but...
With fbdev emulation, every DRM driver is an fbdev driver too. So
CONFIG_FB_DRIVER
On 1/24/22 12:50, Javier Martinez Canillas wrote:
> On 1/24/22 12:33, Thomas Zimmermann wrote:
>
> [snip]
>
>>> Thoughts?
>>
>> I can't say I approve keeping fbdev alive, but...
>>
>> With fbdev emulation, every DRM driver is an fbdev driver too. So
>> CONFIG_FB_DRIVER is somewhat misleading.
On Mon, 2022-01-24 at 14:03 +0100, Christian König wrote:
> 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
Looks good.
1 - 100 of 185 matches
Mail list logo
