Hi Philippe,
thanks for the patch.
Reviewed-by: Alain Volmat
Alain
On Thu, Jan 13, 2022 at 06:19:21PM +0100, Philippe Cornu wrote:
> Add Alain as sti maintainer for both drm/sti & cec/sti.
> Add Raphaël as stm maintainer for drm/stm.
>
> Signed-off-by: Philippe Cornu
> ---
> MAINTAINERS |
On Tue, Jan 11, 2022 at 09:21:51PM +0100, Tommaso Merciai wrote:
> On Sun, Jan 09, 2022 at 03:44:07PM -0300, Fabio Estevam wrote:
> > Hi Tommaso,
> >
> > On Sat, Jan 8, 2022 at 4:17 PM Tommaso Merciai
> > wrote:
> >
> > > Hi Fabio,
> > > If you need some test let me know. Whitch filesystem are
-ENOMEM is correct error code to return on a memory allocation failure
instead of -1.
Smatch Warning:
drivers/gpu/drm/udl/udl_connector.c:27 udl_get_edid_block() warn:
returning -1 instead of -ENOMEM is sloppy
Fixes: a51143001d9e ("drm/udl: Refactor edid retrieving in UDL driver (v2)")
On Sun, Jan 16, 2022 at 10:27:19AM -0300, Fabio Estevam wrote:
> Hi Tommaso,
>
> On Sat, Jan 15, 2022 at 8:23 PM Tommaso Merciai
> wrote:
>
> > Hi Fabio,
> > I'm working on bring up urt,umsh-8596md-20t lvds kit panel, but after enable
> > following node I get the following error:
>
> I assume
On 1/14/2022 10:03 AM, Daniel Vetter wrote:
Hi all,
On Wed, Jan 12, 2022 at 11:55:14AM -0800, Iouri Tarassov wrote:
> Implement the LX_DXCREATESYNCFILE IOCTL (D3DKMTCreateSyncFile).
>
> dxgsyncfile is built on top of the Linux sync_file object and
> provides a way for the user mode to
Hi Inki,
On Fri, Jan 14, 2022 at 11:08 AM Inki Dae wrote:
>
> Hi Lad Prabhakar,
>
> 21. 12. 23. 오전 4:01에 Lad Prabhakar 이(가) 쓴 글:
> > platform_get_resource(pdev, IORESOURCE_IRQ, ..) relies on static
> > allocation of IRQ resources in DT core code, this causes an issue
> > when using hierarchical
On a dual core group GPUs (such as T628) fragment shading can be
performed over all cores (because a fragment shader job doesn't
need coherency between threads), however vertex shading requires
to be run on the same core group as the tiler (which always lives
in core group 0).
As a first step to
Convert the encoders to bridge drivers in order to standardize on
a single API with built-in dumb encoder support for compatibility
with existing component drivers.
Driver bridge conversion will help to reuse the same bridge on
different platforms as exynos dsi driver can be used as a Samsung
Trigger hotplug event with drm_kms_helper_hotplug_event might fail if the
connector state pointer is NULL.
BUG observed in exynos dsi driver where drm_bridge_attach is trying to register
a connector in panel_bridge before the hotplug event is triggered,
WARNING: CPU: 1 PID: 1 at
Replace the manual panel handling code by a drm panel_bridge via
devm_drm_of_get_bridge().
Adding panel_bridge handling,
- Drops drm_connector and related operations as drm_bridge_attach
creates connector during attachment.
- Drops panel pointer and iterate the bridge, so-that it can operate
Host transfer in DSI master will invoke only when the DSI commands
sent from DSI devices like DSI Panel or DSI bridges and this host
transfer wouldn't invoke I2C based DSI bridge drivers.
Handling DSI host initialization in transfer calls might miss the
controller setup for I2C configured DSI
The new support drm bridges are moving towards atomic functions.
Replace atomic version of functions to continue the transition
to the atomic API.
Signed-off-by: Jagan Teki
---
Changes for v5, v4, v3:
- none
drivers/gpu/drm/exynos/exynos_drm_dsi.c | 25 -
1 file
platform_get_resource() may fail and return NULL, so check it's value
before using it.
Reported-by: Zou Wei
Signed-off-by: Kevin Tang
Reviewed-by: Javier Martinez Canillas
Acked-by: Thomas Zimmermann
v1 -> v2:
- new patch
---
drivers/gpu/drm/sprd/sprd_dpu.c | 5 +
Updated series about drm bridge conversion of exynos dsi.
Previous version can be accessible, here [1].
Patch 1: connector reset
Patch 2: panel_bridge API
Patch 3: bridge conversion
Patch 4: atomic functions
Patch 5: DSI init in pre_enable
Apply below patches to test on Exynos DSI:
-
The threshold value is used for AST2600 only.
Signed-off-by: KuoHsiang Chou
---
drivers/gpu/drm/ast/ast_mode.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c
index 1c7a57a03..7f2e248a6 100644
---
'drm' could be null in sprd_drm_shutdown, and drm_warn maybe dereference
it, remove this warning log.
Reported-by: Dan Carpenter
Signed-off-by: Kevin Tang
Reviewed-by: Javier Martinez Canillas
Acked-by: Thomas Zimmermann
v1 -> v2:
- Split checking platform_get_resource() return value to a
Am Montag, 17. Januar 2022, 08:44:37 CET schrieb Chen-Yu Tsai:
> On Sat, Jan 15, 2022 at 7:03 AM Brian Norris wrote:
> >
> > Commit b18c6c3c7768 ("ASoC: rockchip: cdn-dp sound output use spdif")
> > switched the platform to SPDIF, but we didn't fix up the device tree.
> >
> > Drop the pinctrl
Hi,
On Sat, Jan 15, 2022 at 7:03 AM Brian Norris wrote:
>
> Now that the cdn-dp driver supports plug-change callbacks, let's wire it
> up.
>
> Signed-off-by: Brian Norris
> ---
>
> (no changes since v1)
>
> sound/soc/rockchip/rk3399_gru_sound.c | 20
> 1 file changed, 20
v1:
remove the selected DRM_KMS_CMA_HELPER in kconfig
drm-sprd-fix-potential-NULL-dereference
v2:
fix commit comments long lines issue and drop "On linux-next" comments
Split checking platform_get_resource() return value to a separate patch
Use dev_warn() instead of removing the warning
On commit 43531edd53f0 ("drm/sprd: add Unisoc's drm kms master"),
adds the config DRM_SPRD, which selects DRM_KMS_CMA_HELPER.
However, commit 09717af7d13d ("drm: Remove CONFIG_DRM_KMS_CMA_HELPER
option") just removed the DRM_KMS_CMA_HELPER.
So the select DRM_KMS_CMA_HELPER refers to a
This series adds support for mt8192 h264/vp8/vp9 decoder drivers. Firstly,
refactor
power/clock/interrupt interfaces for mt8192 is lat and core architecture.
Secondly, add new functions to get frame buffer size and resolution according
to decoder capability from scp side. Then add callback
Lock, power and clock are highly coupled operations. Adds vdec
enable/disable hardware helpers and uses them.
Signed-off-by: Yunfei Dong
Reviewed-by: Tzung-Bi Shih
---
.../platform/mtk-vcodec/mtk_vcodec_dec_drv.c | 5 -
.../platform/mtk-vcodec/mtk_vcodec_dec_pm.c | 168 +++---
Hey Hsin-Yi,
On Thu, 13 Jan 2022 at 09:29, Hsin-Yi Wang wrote:
>
> Use devm_kzalloc instead of kzalloc and drop kfree(). Let the memory
> handled by driver detach.
>
> Signed-off-by: Hsin-Yi Wang
> Reviewed-by: Xin Ji
> ---
> v2->v3: remove kfree() in anx7625_i2c_remove().
> ---
>
Hi
Am 14.01.22 um 19:11 schrieb Helge Deller:
The fbdev layer is orphaned, but seems to need some care.
So I'd like to step up as new maintainer.
Signed-off-by: Helge Deller
First of all, thank you for stepping up to maintain the fbdev codebase.
It really needs someone actively looking
Hi Thomas,
On 1/17/22 12:16, Thomas Zimmermann wrote:
> Hi
>
> Am 14.01.22 um 19:11 schrieb Helge Deller:
>> The fbdev layer is orphaned, but seems to need some care.
>> So I'd like to step up as new maintainer.
>>
>> Signed-off-by: Helge Deller
>
> First of all, thank you for stepping up to
On Mon, 17 Jan 2022 at 06:22, Julian Braha wrote:
>
> When DRM_CHIPONE_ICN6211 is selected, and DRM_KMS_HELPER is not selected,
> Kbuild gives the following warning:
>
> WARNING: unmet direct dependencies detected for DRM_PANEL_BRIDGE
> Depends on [n]: HAS_IOMEM [=y] && DRM_BRIDGE [=y] &&
On Mon, Jan 17, 2022 at 9:34 AM Iouri Tarassov
wrote:
>
>
> On 1/14/2022 10:03 AM, Daniel Vetter wrote:
> > Hi all,
> >
> > On Wed, Jan 12, 2022 at 11:55:14AM -0800, Iouri Tarassov wrote:
> > > Implement the LX_DXCREATESYNCFILE IOCTL (D3DKMTCreateSyncFile).
> > >
> > > dxgsyncfile is built on top
On 15/01/2022 16:06, Alexey Sheplyakov wrote:
> On a dual core group GPUs (such as T628) fragment shading can be
> performed over all cores (because a fragment shader job doesn't
> need coherency between threads), however vertex shading requires
> to be run on the same core group as the tiler
Hey Neil,
On Thu, 13 Jan 2022 at 15:43, Neil Armstrong wrote:
>
> This adds support for DRM_BRIDGE_ATTACH_NO_CONNECTOR by adding the
> bridge get_edid() and detect() callbacks after refactoring the connector
> get_modes() and connector_detect() callbacks.
>
> In order to keep the bridge working,
From: Minghao Chi
Return value directly instead of taking this in another redundant variable.
Reported-by: Zeal Robot
Signed-off-by: Minghao Chi
Signed-off-by: CGEL ZTE
---
drivers/gpu/drm/vmwgfx/vmwgfx_execbuf.c | 13 +++--
1 file changed, 3 insertions(+), 10 deletions(-)
diff
Am 14.01.22 um 17:31 schrieb Daniel Vetter:
On Mon, Jan 03, 2022 at 12:13:41PM +0100, Christian König wrote:
Am 22.12.21 um 22:21 schrieb Daniel Vetter:
On Tue, Dec 07, 2021 at 01:33:51PM +0100, Christian König wrote:
Add a function to simplify getting a single fence for all the fences in
the
Hi Neil,
> Subject: Re: dw_hdmi is showing wrong colour after commit
> 7cd70656d1285b79("drm/bridge: display-connector: implement bus fmts
> callbacks")
>
> Hi again,
>
> On 14/01/2022 15:40, Neil Armstrong wrote:
> > Hi,
> >
> > On 14/01/2022 15:23, Biju Das wrote:
> >>
> >>
> >>> -Original
On Thu, 2022-01-13 at 17:10 +0100, Matthias Brugger wrote:
> Hi Hans,
>
> On 13/01/2022 11:15, Hans Verkuil wrote:
> > On 13/01/2022 11:11, AngeloGioacchino Del Regno wrote:
> > > Il 11/01/22 11:57, AngeloGioacchino Del Regno ha scritto:
> > > > Il 12/11/21 11:55, Yong Wu ha scritto:
> > > > >
Hi Inki,
On Fri, 14 Jan 2022 at 02:18, Inki Dae wrote:
>
> Hi Robert,
>
> 22. 1. 12. 오후 7:05에 Robert Foss 이(가) 쓴 글:
> > Thank you again for catching this and submitting a revert.
> >
> > Reviewed-by: Robert Foss >
> > Applied to drm-misc-next.
> >
>
> Trivial thing I think but just notice. With
Hi again,
On 14/01/2022 15:40, Neil Armstrong wrote:
> Hi,
>
> On 14/01/2022 15:23, Biju Das wrote:
>>
>>
>>> -Original Message-
>>> From: Neil Armstrong
>>> Sent: 14 January 2022 13:56
>>> To: Biju Das ; Fabio Estevam
>>>
>>> Cc: dan...@ffwll.ch; laurent.pinch...@ideasonboard.com;
>>>
Hello Jani,
On 1/17/22 11:49, Jani Nikula wrote:
> On Mon, 17 Jan 2022, Daniel Vetter wrote:
>> Hi Helge
>>
>> On Fri, Jan 14, 2022 at 7:18 PM Helge Deller wrote:
>>>
>>> The fbdev layer is orphaned, but seems to need some care.
>>> So I'd like to step up as new maintainer.
>>>
>>>
Hi Neil,
Quoting Neil Armstrong (2022-01-17 10:08:38)
> Hi again,
>
> On 14/01/2022 15:40, Neil Armstrong wrote:
> > Hi,
> >
> > On 14/01/2022 15:23, Biju Das wrote:
> >>
> >>
> >>> -Original Message-
> >>> From: Neil Armstrong
> >>> Sent: 14 January 2022 13:56
> >>> To: Biju Das ;
Hi Helge
On Fri, Jan 14, 2022 at 7:18 PM Helge Deller wrote:
>
> The fbdev layer is orphaned, but seems to need some care.
> So I'd like to step up as new maintainer.
>
> Signed-off-by: Helge Deller
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5d0cd537803a..ce47dbc467cc 100644
> ---
On Tue, Jan 11, 2022 at 5:06 PM Xin Ji wrote:
>
> Send DPCD command to downstream before anx7625 power down,
> let downstream monitor enter into standby mode.
>
> Signed-off-by: Xin Ji
> ---
> drivers/gpu/drm/bridge/analogix/anx7625.c | 42 +++
> 1 file changed, 35
Hi Helge
On Fri, Jan 14, 2022 at 7:18 PM Helge Deller wrote:
>
> The fbdev layer is orphaned, but seems to need some care.
> So I'd like to step up as new maintainer.
>
> Signed-off-by: Helge Deller
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 5d0cd537803a..ce47dbc467cc 100644
> ---
On Mon, 17 Jan 2022, Daniel Vetter wrote:
> Hi Helge
>
> On Fri, Jan 14, 2022 at 7:18 PM Helge Deller wrote:
>>
>> The fbdev layer is orphaned, but seems to need some care.
>> So I'd like to step up as new maintainer.
>>
>> Signed-off-by: Helge Deller
>>
>> diff --git a/MAINTAINERS
On 1/17/22 05:33, Linus Torvalds wrote:
> On Sun, Jan 16, 2022 at 9:32 PM Helge Deller wrote:
>>
>> This pull request contains only one single initial patch which adds
>> myself to the MAINTAINERS file for the FRAMBUFFER LAYER.
>
> I'll pull this
Thanks!
> (as my test builds for other things
hi Robert,
The second patch depends on "drm/bridge: anx7625: send DPCD command to
downstream"
(https://patchwork.kernel.org/project/dri-devel/patch/1f36f8bf0a48fb2bba17bacec23700e58c1d407d.1641891874.git@analogixsemi.com/).
But I'm waiting for Xin Ji's response for that patch.
Thanks
On
On 17/01/2022 11:27, AngeloGioacchino Del Regno wrote:
Il 17/01/22 08:04, Yong Wu ha scritto:
MediaTek IOMMU block diagram always like below:
M4U
|
smi-common
|
-
| | ...
| |
larb1 larb2
| |
vdec
Hello Daniel,
On 1/17/22 11:02, Daniel Vetter wrote:
> Hi Helge
>
> On Fri, Jan 14, 2022 at 7:18 PM Helge Deller wrote:
>>
>> The fbdev layer is orphaned, but seems to need some care.
>> So I'd like to step up as new maintainer.
>>
>> Signed-off-by: Helge Deller
>>
>> diff --git a/MAINTAINERS
Add support for VP8 decoding using the stateless API,
as supported by MT8192.
Signed-off-by: Yunfei Dong
---
drivers/media/platform/mtk-vcodec/Makefile| 1 +
.../mtk-vcodec/mtk_vcodec_dec_stateless.c | 24 +-
.../platform/mtk-vcodec/mtk_vcodec_drv.h | 1 +
Mt8192 can use some of common code with mt8183. Moves them to
a new file in order to reuse.
Signed-off-by: Yunfei Dong
---
drivers/media/platform/mtk-vcodec/Makefile| 1 +
.../mtk-vcodec/vdec/vdec_h264_req_common.c| 307 ++
.../mtk-vcodec/vdec/vdec_h264_req_common.h|
Add support for VP9 decoding using the stateless API,
as supported by MT8192. And the drivers is lat and core architecture.
Signed-off-by: Yunfei Dong
Signed-off-by: George Sun
---
drivers/media/platform/mtk-vcodec/Makefile|1 +
.../mtk-vcodec/mtk_vcodec_dec_stateless.c | 26 +-
Adds h264 lat and core architecture driver for mt8192,
and the decode mode is frame based for stateless decoder.
Signed-off-by: Yunfei Dong
---
drivers/media/platform/mtk-vcodec/Makefile| 1 +
.../mtk-vcodec/vdec/vdec_h264_req_multi_if.c | 599 ++
lat thread: output queue \
-> lat hardware -> lat trans buffer
lat trans buffer /
core thread: capture queue \
->core hardware -> capture queue
lat trans buffer /
Lat and core work in different
Supported output and capture format types for mt8192 are different
with mt8183. Needs to get format types according to decoder capability.
Signed-off-by: Yunfei Dong
---
.../platform/mtk-vcodec/mtk_vcodec_dec.c | 8 +-
.../mtk-vcodec/mtk_vcodec_dec_stateful.c | 13 +-
For lat and core decode in parallel, need to get capture buffer
when core start to decode and put capture buffer to display
list when core decode done.
Signed-off-by: Yunfei Dong
---
.../mtk-vcodec/mtk_vcodec_dec_stateless.c | 121 --
.../platform/mtk-vcodec/mtk_vcodec_drv.h
MT8173 platform use vpu firmware, mt8183/mt8192 will use scp
firmware instead, using chip name is not reasonable to separate
different firmware architecture. Using firmware type is much better.
Signed-off-by: Yunfei Dong
Reviewed-by: Tzung-Bi Shih
Reviewed-by: AngeloGioacchino Del Regno
---
Different capture buffer format has different buffer size, need to get
real buffer size according to buffer type from scp.
Signed-off-by: Yunfei Dong
---
.../media/platform/mtk-vcodec/vdec_ipi_msg.h | 36 ++
.../media/platform/mtk-vcodec/vdec_vpu_if.c | 49 +++
Need to use default pic info when get pic info fail.
Signed-off-by: Yunfei Dong
---
drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c
Needs to use mediatek compressed mode for mt8192 decoder.
Signed-off-by: Yunfei Dong
---
.../media/platform/mtk-vcodec/mtk_vcodec_dec_stateless.c | 7 ++-
drivers/media/platform/mtk-vcodec/mtk_vcodec_drv.h | 1 +
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git
For vp8 not support 4K, need to disable it.
Signed-off-by: Yunfei Dong
---
drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c
Supported max resolution for different platforms are not the same: 2K
or 4K, getting it according to dec_capability.
Signed-off-by: Yunfei Dong
Reviewed-by: Tzung-Bi Shih
---
.../platform/mtk-vcodec/mtk_vcodec_dec.c | 29 +++
.../platform/mtk-vcodec/mtk_vcodec_drv.h |
Capture queue format type is difference for different platform,
need to calculate capture buffer size according to capture queue
format type in scp.
Signed-off-by: Yunfei Dong
---
drivers/media/platform/mtk-vcodec/mtk_vcodec_dec.c | 2 ++
drivers/media/platform/mtk-vcodec/mtk_vcodec_drv.h | 2
On 1/17/22 11:02, Daniel Vetter wrote:
[snip]
>> FRAMEBUFFER LAYER
>> -L: dri-devel@lists.freedesktop.org
>> +M: Helge Deller
>> L: linux-fb...@vger.kernel.org
>> -S: Orphan
>
> Maybe don't rush maintainer changes in over the w/e without even bothering
> to get any input from
Il 17/01/22 08:04, Yong Wu ha scritto:
MediaTek IOMMU block diagram always like below:
M4U
|
smi-common
|
-
| | ...
| |
larb1 larb2
| |
vdec venc
All the consumer connect with smi-larb, then connect
Am 14.01.22 um 18:40 schrieb Felix Kuehling:
Am 2022-01-14 um 12:26 p.m. schrieb Christian König:
Am 14.01.22 um 17:44 schrieb Daniel Vetter:
Top post because I tried to catch up on the entire discussion here.
So fundamentally I'm not opposed to just close this fork() hole once and
for all.
Hi Matthias,
On 1/17/22 12:49, Matthias Brugger wrote:
>
>
> On 17/01/2022 11:27, AngeloGioacchino Del Regno wrote:
>> Il 17/01/22 08:04, Yong Wu ha scritto:
>>> MediaTek IOMMU block diagram always like below:
>>>
>>> M4U
>>> |
>>> smi-common
>>> |
>>>
Hi
Am 17.01.22 um 12:33 schrieb Helge Deller:
Hi Thomas,
On 1/17/22 12:16, Thomas Zimmermann wrote:
Hi
Am 14.01.22 um 19:11 schrieb Helge Deller:
The fbdev layer is orphaned, but seems to need some care.
So I'd like to step up as new maintainer.
Signed-off-by: Helge Deller
First of all,
Hi,
> b) to include new drivers (for old hardware) if they arrive (probably happens
> rarely but there can be).
>I know of at least one driver which won't be able to support DRM
Hmm? I seriously doubt that. There is always the option to use a
shadow framebuffer, then convert from
On 17/01/2022 13:13, Biju Das wrote:
> Hi Neil,
>> Subject: Re: dw_hdmi is showing wrong colour after commit
>> 7cd70656d1285b79("drm/bridge: display-connector: implement bus fmts
>> callbacks")
>>
>> Hi again,
>>
>> On 14/01/2022 15:40, Neil Armstrong wrote:
>>> Hi,
>>>
>>> On 14/01/2022 15:23,
Quoting Neil Armstrong (2022-01-17 13:53:47)
> On 17/01/2022 11:58, Kieran Bingham wrote:
> > Hi Neil,
> > This fixes the issue for me here on an H3 Salvator-XS.
> >
> > Could you add...
> >
> > Bisected-by: Kieran Bingham
> > Tested-by: Kieran Bingham
> >
> > alongside Biju's Reported-by:
Hi Thomas,
On Mon, Jan 17, 2022 at 2:51 PM Thomas Zimmermann wrote:
> Am 17.01.22 um 14:29 schrieb Geert Uytterhoeven:
> > On Mon, Jan 17, 2022 at 1:57 PM Gerd Hoffmann wrote:
> >>> b) to include new drivers (for old hardware) if they arrive (probably
> >>> happens rarely but there can be).
>
When the dw-hdmi bridge is in first place of the bridge chain, this
means there is now way to select an input format of the dw-hdmi HW
component.
Since introduction of display-connector, negociation was broken since
the dw-hdmi negociation code only worked when the dw-hdmi bridge was
in last
Am 2022-01-17 um 6:44 a.m. schrieb Christian König:
> Am 14.01.22 um 18:40 schrieb Felix Kuehling:
>> Am 2022-01-14 um 12:26 p.m. schrieb Christian König:
>>> Am 14.01.22 um 17:44 schrieb Daniel Vetter:
Top post because I tried to catch up on the entire discussion here.
So
I don't think fork() would work with userspace where all buffers are
shared. It certainly doesn't work now. The driver needs to be notified that
a buffer or texture is shared to ensure data coherency between processes,
and the driver must execute decompression and other render passes when a
buffer
If we are unlucky and can't allocate enough memory when splitting
blocks, where we temporarily end up with the given block and its buddy
on the respective free list, then we need to ensure we delete both
blocks, and no just the buddy, before potentially freeing them.
Fixes: 14d1b9a6247c
Hey Zhiming,
On Mon, 17 Jan 2022 at 16:42, Zhiming Liu wrote:
>
> drm/bridge: Remove extra device acquisition method of i2c client in lt9611
> driver.
The commit title is already in the email title, it doesn't need to be
sent twice, sorry if I was unclear about this.
>
> We have got the
On 1/17/22 08:56, Maarten Lankhorst wrote:
i915_gem_evict_vm will need to be able to evict objects that are
locked by the current ctx. By testing if the current context already
locked the object, we can do this correctly. This allows us to
evict the entire vm even if we already hold some
On Mon, Jan 17, 2022 at 3:48 PM Helge Deller wrote:
>
> On 1/17/22 15:10, Geert Uytterhoeven wrote:
> > Hi Thomas,
> >
> > On Mon, Jan 17, 2022 at 2:51 PM Thomas Zimmermann
> > wrote:
> >> Am 17.01.22 um 14:29 schrieb Geert Uytterhoeven:
> >>> On Mon, Jan 17, 2022 at 1:57 PM Gerd Hoffmann
On 17/01/2022 15:27, Biju Das wrote:
> Hi Neil,
>
> Thanks for the patch
>
>> Subject: [PATCH] drm/bridge: dw-hdmi: use safe format when first in bridge
>> chain
>>
>> When the dw-hdmi bridge is in first place of the bridge chain, this means
>> there is now way to select an input format of the
Hey Zhiming,
Again, I think the code is good, but let's fix some small stuff with
the patch submission and then I'll happily apply this.
On Thu, 13 Jan 2022 at 13:52, Zhiming Liu wrote:
>
> Signed-off-by: Zhiming Liu
The tags like Signed-off-by come after the body of the commit message.
>
>
On Mon, Jan 17, 2022 at 4:43 PM Helge Deller wrote:
>
> On 1/17/22 16:00, Daniel Vetter wrote:
> > On Mon, Jan 17, 2022 at 1:16 PM Helge Deller wrote:
> >>
> >> Hello Daniel,
> >>
> >> On 1/17/22 11:02, Daniel Vetter wrote:
> >>> Hi Helge
> >>>
> >>> On Fri, Jan 14, 2022 at 7:18 PM Helge Deller
On 17/01/2022 11:58, Kieran Bingham wrote:
> Hi Neil,
>
> Quoting Neil Armstrong (2022-01-17 10:08:38)
>> Hi again,
>>
>> On 14/01/2022 15:40, Neil Armstrong wrote:
>>> Hi,
>>>
>>> On 14/01/2022 15:23, Biju Das wrote:
> -Original Message-
> From: Neil Armstrong
>
Hi Neil,
Thanks for the patch
> Subject: [PATCH] drm/bridge: dw-hdmi: use safe format when first in bridge
> chain
>
> When the dw-hdmi bridge is in first place of the bridge chain, this means
> there is now way to select an input format of the dw-hdmi HW component.
>
> Since introduction of
Am 2022-01-17 um 9:21 a.m. schrieb Christian König:
> Am 17.01.22 um 15:17 schrieb Felix Kuehling:
>> Am 2022-01-17 um 6:44 a.m. schrieb Christian König:
>>> Am 14.01.22 um 18:40 schrieb Felix Kuehling:
Am 2022-01-14 um 12:26 p.m. schrieb Christian König:
> Am 14.01.22 um 17:44 schrieb
On 1/17/22 15:10, Geert Uytterhoeven wrote:
> Hi Thomas,
>
> On Mon, Jan 17, 2022 at 2:51 PM Thomas Zimmermann wrote:
>> Am 17.01.22 um 14:29 schrieb Geert Uytterhoeven:
>>> On Mon, Jan 17, 2022 at 1:57 PM Gerd Hoffmann wrote:
> b) to include new drivers (for old hardware) if they arrive
Hi
Am 17.01.22 um 15:10 schrieb Geert Uytterhoeven:
[...]
Which uses an DRM_FORMAT_XRGB intermediate, and
drm_fb_xrgb_to_gray8() and repaper_gray8_to_mono_reversed()
to convert from truecolor to monochrome. I guess that would work,
as this is a slow e-ink display. Have fun as a text
On Fri, Jan 14, 2022 at 11:30:36AM -0500, Eric Farman wrote:
> On Fri, 2022-01-14 at 20:28 +0800, Liu Yi L wrote:
> > Hi Eric,
> >
> > Hope you are back from new year holiday.:-) Have you got chane to
> > consider
> > this patch?
>
> Hi Yi Liu,
>
> It's coming up the list, but it's not there
On Mon, Dec 13, 2021 at 10:48 PM Maxime Ripard wrote:
>
> On Fri, Dec 10, 2021 at 04:47:08PM +0530, Jagan Teki wrote:
> > Some display panels would come up with a non-DSI output, those
> > can have an option to connect the DSI host by means of interface
> > bridge converter.
> >
> > This DSI to
On 17/01/2022 15:09, Andi Shyti wrote:
The GT has its own properties and in sysfs they should be grouped
in the 'gt/' directory.
Create a 'gt/' directory in sysfs which will contain gt0...gtN
directories related to each tile configured in the GPU. Move the
power management files inside those
On 1/17/22 16:00, Daniel Vetter wrote:
> On Mon, Jan 17, 2022 at 1:16 PM Helge Deller wrote:
>>
>> Hello Daniel,
>>
>> On 1/17/22 11:02, Daniel Vetter wrote:
>>> Hi Helge
>>>
>>> On Fri, Jan 14, 2022 at 7:18 PM Helge Deller wrote:
The fbdev layer is orphaned, but seems to need some
Hi
Am 17.01.22 um 16:42 schrieb Helge Deller:
> [...]
c) reintroduce the state where fbcon is fast on fbdev. This is important for
non-DRM machines,
either when run on native hardware or in an emulator.
d) not break DRM development
Especially regarding c) I complained in [1] and got no
Hi Thomas,
On 1/17/22 16:05, Thomas Zimmermann wrote:
> Hi
>
> Am 17.01.22 um 15:47 schrieb Helge Deller:
>> On 1/17/22 15:10, Geert Uytterhoeven wrote:
>> [...]
>>> Using an XRGB32 intermediate would kill the user experience on old
>>> machines, due to both increased memory usage and copy
Hi Gerd,
On Mon, Jan 17, 2022 at 1:57 PM Gerd Hoffmann wrote:
> > b) to include new drivers (for old hardware) if they arrive (probably
> > happens rarely but there can be).
> >I know of at least one driver which won't be able to support DRM
>
> Hmm? I seriously doubt that. There is
Hi
Am 17.01.22 um 14:29 schrieb Geert Uytterhoeven:
Hi Gerd,
On Mon, Jan 17, 2022 at 1:57 PM Gerd Hoffmann wrote:
b) to include new drivers (for old hardware) if they arrive (probably happens
rarely but there can be).
I know of at least one driver which won't be able to support DRM
On 17/01/2022 15:05, Kieran Bingham wrote:
> Quoting Neil Armstrong (2022-01-17 13:53:47)
>> On 17/01/2022 11:58, Kieran Bingham wrote:
>>> Hi Neil,
>
>
>
>>> This fixes the issue for me here on an H3 Salvator-XS.
>>>
>>> Could you add...
>>>
>>> Bisected-by: Kieran Bingham
>>> Tested-by:
Am 17.01.22 um 15:17 schrieb Felix Kuehling:
Am 2022-01-17 um 6:44 a.m. schrieb Christian König:
Am 14.01.22 um 18:40 schrieb Felix Kuehling:
Am 2022-01-14 um 12:26 p.m. schrieb Christian König:
Am 14.01.22 um 17:44 schrieb Daniel Vetter:
Top post because I tried to catch up on the entire
On Mon, Jan 17, 2022 at 1:16 PM Helge Deller wrote:
>
> Hello Daniel,
>
> On 1/17/22 11:02, Daniel Vetter wrote:
> > Hi Helge
> >
> > On Fri, Jan 14, 2022 at 7:18 PM Helge Deller wrote:
> >>
> >> The fbdev layer is orphaned, but seems to need some care.
> >> So I'd like to step up as new
Hi
Am 17.01.22 um 15:47 schrieb Helge Deller:
On 1/17/22 15:10, Geert Uytterhoeven wrote:
[...]
Using an XRGB32 intermediate would kill the user experience on old
machines, due to both increased memory usage and copy overhead.
Personally, I'd much appreciate if userspace would support more
The GT has its own properties and in sysfs they should be grouped
in the 'gt/' directory.
Create a 'gt/' directory in sysfs which will contain gt0...gtN
directories related to each tile configured in the GPU. Move the
power management files inside those directories.
The previous power management
From: Tvrtko Ursulin
On a multi-tile platform, each tile has its own registers + GGTT
space, and BAR 0 is extended to cover all of them.
Up to four gts are supported in i915->gt[], with slot zero
shadowing the existing i915->gt0 to enable source compatibility
with legacy driver paths. A
Hi,
This is the second series that prepares i915 to host multitile
platforms. It introduces the for_each_gt() macro that loops over
the tiles to perform per gt actions.
This patch is a combination of two patches developed originally
by Abdiel, who introduced some refactoring during probe, and
Hi Owen
On Mon, 17 Jan 2022 at 11:10, owen wrote:
>
> From: owen
>
> It will connect to the mipi dsi host and find the corresponding
> mipi dsi host node, but the node registered by the mipi dsi host
> has not been loaded yet. of_find_mipi_dsi_host_by_node() returns -EINVAL
> which causes the
On Mon, Dec 13, 2021 at 10:32 PM Maxime Ripard wrote:
>
> On Fri, Dec 10, 2021 at 04:47:06PM +0530, Jagan Teki wrote:
> > Existing host driver will keep looking for DRM pointer in
> > sun6i_dsi_attach and defers even if the particular DSI device
> > is found for the first time. Meanwhile it
1 - 100 of 225 matches
Mail list logo
