Set color_depth according to connector->bpc.
Changes since v1:
- Fixed min_bpc is effectively set but not used in
komeda_crtc_get_color_config().
Changes since v2:
- Align the code.
Signed-off-by: Lowry Li (Arm Technology China)
---
.../arm/display/komeda/d71/d71_component.c| 1 +
.../g
Set color_depth according to connector->bpc.
Changes since v1:
- Fixed min_bpc is effectively set but not used in
komeda_crtc_get_color_config().
Signed-off-by: Lowry Li (Arm Technology China)
---
.../arm/display/komeda/d71/d71_component.c| 1 +
.../gpu/drm/arm/display/komeda/komeda_crtc.
https://bugs.freedesktop.org/show_bug.cgi?id=111983
Andre Klapper changed:
What|Removed |Added
Component|General |Two
Status|NEW
Add dcumentation for auo,b101uan08.3, which is mipi dsi video panel
and resolution is 1200x1920.
Signed-off-by: Jitao Shi
---
.../display/panel/auo,b101uan08.3.yaml| 67 +++
1 file changed, 67 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/pa
Auo,auo,b101uan08.3's connector is same as boe,tv101wum-nl6.
The most codes can be reuse.
So auo,b101uan08.3 and boe,tv101wum-nl6 use one driver file.
Add the different parts in driver data.
Signed-off-by: Jitao Shi
---
.../gpu/drm/panel/panel-boe-tv101wum-nl6.c| 78 +++
1 fi
Add dcumentation for boe,tv101wum-n53, which is mipi dsi video panel
and resolution is 1200x1920.
Signed-off-by: Jitao Shi
---
.../display/panel/boe,tv101wum-n53.yaml | 67 +++
1 file changed, 67 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/p
Add documentation for auo kd101n80-45na panel.
Signed-off-by: Jitao Shi
Reviewed-by: Sam Ravnborg
---
.../display/panel/auo,kd101n80-45na.yaml | 67 +++
1 file changed, 67 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/panel/auo,kd101n80-45na.y
Add documentation for boe tv101wum-n16 panel.
Signed-off-by: Jitao Shi
Reviewed-by: Sam Ravnborg
---
.../display/panel/boe,tv101wum-nl6.yaml | 67 +++
1 file changed, 67 insertions(+)
create mode 100644
Documentation/devicetree/bindings/display/panel/boe,tv101wum-nl6.yam
Boe,tv101wum-n53's connector is same as boe,tv101wum-nl6.
The most codes can be reuse.
So boe,tv101wum-n53 and boe,tv101wum-nl6 use one driver file.
Add the different parts in driver data.
Signed-off-by: Jitao Shi
---
.../gpu/drm/panel/panel-boe-tv101wum-nl6.c| 31 +++
1 file
Auo,kd101n80-45na's connector is same as boe,tv101wum-nl6.
The most codes can be reuse.
So auo,kd101n80-45na and boe,tv101wum-nl6 use one driver file.
Add the different parts in driver data.
Signed-off-by: Jitao Shi
---
drivers/gpu/drm/panel/Kconfig | 6 +-
.../gpu/drm/panel/pan
Changes since v6:
- fix boe_panel_init err uninit.
- adjust the delay of backlight on.
Changes since v5:
- covert the documents to yaml
- fine tune boe, tv101wum-n53 panel video timine
Changes since v4:
- add auo,b101uan08.3 panel for this driver.
- add boe,tv101wum-n53 panel for this drive
Add driver for BOE tv101wum-nl6 panel is a 10.1" 1200x1920 panel.
Signed-off-by: Jitao Shi
Reviewed-by: Sam Ravnborg
---
drivers/gpu/drm/panel/Kconfig | 9 +
drivers/gpu/drm/panel/Makefile| 1 +
.../gpu/drm/panel/panel-boe-tv101wum-nl6.c| 713
https://bugs.freedesktop.org/show_bug.cgi?id=111983
Bug ID: 111983
Summary: quan ly
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: not set
Priority: not set
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #87 from Marko Popovic ---
All of the hangs are still present for me, so this patch changed nothing.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=201957
Matthias Heinz (m...@familie-heinz.name) changed:
What|Removed |Added
CC||m...@familie-he
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #86 from Shmerl ---
Looks stable so far, no hangs. I'll continue using it, and will post if it
occurs again.
--
You are receiving this mail because:
You are the assignee for the bug.___
d
a little late but: i915 does have this hack (or rather-possible_crtcs with MST
in i915 has been broken for a while and got fixed, but had to get reverted
because of this issue), it's where this originally came from.
On Wed, 2019-10-09 at 17:01 +0200, Daniel Vetter wrote:
> On Fri, Sep 27, 2019 at
https://bugzilla.kernel.org/show_bug.cgi?id=204241
--- Comment #23 from Alex Deucher (alexdeuc...@gmail.com) ---
Created attachment 285475
--> https://bugzilla.kernel.org/attachment.cgi?id=285475&action=edit
possible fix uvd7
Same fix for uvd7.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=204241
--- Comment #22 from Alex Deucher (alexdeuc...@gmail.com) ---
Created attachment 285473
--> https://bugzilla.kernel.org/attachment.cgi?id=285473&action=edit
possible fix uvd6
Nice work. I think the attached patch should fix it.
--
You are re
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #85 from Shmerl ---
(In reply to Shmerl from comment #84)
> Testing this patch now, using Firefox with nodma.
without* nodma.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #84 from Shmerl ---
Testing this patch now, using Firefox with nodma.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.f
https://bugs.freedesktop.org/show_bug.cgi?id=111980
--- Comment #2 from lei.p...@gmail.com ---
(In reply to Tim Cuthbertson from comment #1)
> My system does this, too, since kernel 5.3.5-arch1-1-ARCH on Arch Linux.
Can you test it without this commit? Same for me 5.3.5-arch1-1-ARCH introduced
th
https://bugzilla.kernel.org/show_bug.cgi?id=204241
--- Comment #21 from a...@tutanota.com ---
Created attachment 285471
--> https://bugzilla.kernel.org/attachment.cgi?id=285471&action=edit
Patch to prevent kernel NULL pointer dereferences
By the way, some of the kernel NULL pointer dereferences
https://bugzilla.kernel.org/show_bug.cgi?id=204241
a...@tutanota.com changed:
What|Removed |Added
Attachment #285349|0 |1
is obsolete|
On Fri, Oct 11, 2019 at 06:39:39AM -0700, Jeffrey Hugo wrote:
> On msm8998, vblank timeouts are observed because the DSI controller is not
> reset properly, which ends up stalling the MDP. This is because the reset
> logic is not correct per the hardware documentation.
>
> The documentation state
https://bugs.freedesktop.org/show_bug.cgi?id=111980
--- Comment #1 from Tim Cuthbertson ---
My system does this, too, since kernel 5.3.5-arch1-1-ARCH on Arch Linux.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
On 2019-10-09 03:47, Daniel Vetter wrote:
On Tue, Sep 24, 2019 at 10:28:48AM -0700, Jeykumar Sankaran wrote:
Reviving this thread from the context of the below conversion:
https://lore.kernel.org/linux-arm-msm/db26145b-3f64-a334-f698-76f972332881
@baylibre.com/T/#u
On 2018-10-05 01:19, Neil
+dri, +Daniel
On Thu, Oct 10, 2019 at 06:09:07PM -0700, Lucas De Marchi wrote:
Fixes: 83fa9842afe7 ("drm/dp-mst: Drop connection_mutex check")
Signed-off-by: Lucas De Marchi
---
drivers/gpu/drm/drm_dp_mst_topology.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_dp_mst_
Hi
Am 11.10.19 um 19:09 schrieb Daniel Stone:
Hi Rohan,
On Fri, 11 Oct 2019 at 15:30, Rohan Garg wrote:
DRM_IOCTL_DUMB_SET_LABEL lets you label GEM objects, making it
easier to debug issues in userspace applications.
I'm not sure if this was pointed out already, but dumb buffers != GEM
buff
Hello Rohan,
On Fri, 11 Oct 2019 16:30:09 +0200
Rohan Garg wrote:
> DRM_IOCTL_DUMB_SET_LABEL lets you label GEM objects, making it
> easier to debug issues in userspace applications.
>
> Changes in v2:
> - Hoist the IOCTL up into the drm_driver framework
>
> Changes in v3:
> - Introduce a
On Fri, Oct 11, 2019 at 12:56 PM Brian Starkey wrote:
>
> Hi,
>
> On Fri, Oct 11, 2019 at 11:14:43AM +0200, Neil Armstrong wrote:
> > Hi Brian,
> >
> > On 11/10/2019 10:41, Brian Starkey wrote:
> > > Are you sure the GPU supports other orders? I think any Arm driver
> > > will only be producing D
Hello, Daniel.
On Wed, Oct 09, 2019 at 06:06:52PM +0200, Daniel Vetter wrote:
> That's not the point I was making. For cpu cgroups there's a very well
> defined connection between the cpu bitmasks/numbers in cgroups and the cpu
> bitmasks you use in various system calls (they match). And that stuf
Hi Rohan,
On Fri, 11 Oct 2019 at 15:30, Rohan Garg wrote:
> DRM_IOCTL_DUMB_SET_LABEL lets you label GEM objects, making it
> easier to debug issues in userspace applications.
I'm not sure if this was pointed out already, but dumb buffers != GEM
buffers. GEM buffers _can_ be dumb, but might not b
> Just use Cc. We want all replies to go to the list(s) as well.
Sorry, I wasn't sure and wanted to err on the side of not spamming the
wrong people.
> Oct 10 12:53:30 scorpion kernel: RIP:
0010:dma_fence_signal_locked+0x30/0xe0
>
> Looks like it could be
> https://bugs.freedesktop.org/show_bug.c
* Tomi Valkeinen [191011 10:25]:
> On 10/10/2019 16:24, Tony Lindgren wrote:
>
> > Hmm so what register does this clock actually change?
> >
> > I'm seeing an increase of few tens of extra mW, which means at
> > least one day of standby time less for me :) It does not happen
> > always, maybe ha
Thanks for the patches.
I think for all of them we should just drop the REG_READ calls
completely. They look like leftovers from when we had a different
register update scheme that would read the register, then update or get
the field value. Now we just use the REG_ macros that will combine the
re
https://bugs.freedesktop.org/show_bug.cgi?id=111691
--- Comment #17 from Jaap Buurman ---
(In reply to takios+fdbugs from comment #16)
> I ran into the same issue but after installing linux kernel 5.4rc2 it was
> fixed.
That's good to hear! Does anyone know whether the fix will be backported to
https://bugs.freedesktop.org/show_bug.cgi?id=111691
--- Comment #16 from takios+fdb...@takios.de ---
I ran into the same issue but after installing linux kernel 5.4rc2 it was
fixed.
--
You are receiving this mail because:
You are the assignee for the bug._
The pull request you sent on Fri, 11 Oct 2019 14:36:03 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-10-11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/9892f9f6cf83e8ecaacc5ec7847cf5ba033119d2
Thank you!
--
Deet-doot-dot, I am a bot.
https://k
On Wed, Oct 09, 2019 at 02:27:41PM -0700, Matt Roper wrote:
> On Wed, Oct 09, 2019 at 05:01:20PM -0400, Daniele Castagna wrote:
> > On Wed, Oct 9, 2019 at 1:34 PM Matt Roper wrote:
> > >
> > > The previous version of this series was posted in February here:
> > >
> > > https://lists.freed
On Thu, Oct 10, 2019 at 03:24:28PM +0200, Boris Brezillon wrote:
> On Thu, 10 Oct 2019 16:11:59 +0300
> Ville Syrjala wrote:
>
> > From: Ville Syrjälä
> >
> > @swap@
> > identifier TEMP;
> > expression A,B;
> > @@
> > - TEMP = A;
> > - A = B;
> > - B = TEMP;
> > + swap(A, B);
> >
> > @@
> > ty
https://bugs.freedesktop.org/show_bug.cgi?id=111980
Bug ID: 111980
Summary: Rebbot and shutdown doesn't work on specific hardware
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Wed, Oct 02, 2019 at 06:06:30PM +0200, Krzysztof Kozlowski wrote:
> Convert Generic Power Domain bindings to DT schema format using
> json-schema. The consumer bindings are split to separate file.
>
> Signed-off-by: Krzysztof Kozlowski
>
> ---
>
> Changes since v1:
> 1. Select all nodes for
https://bugzilla.kernel.org/show_bug.cgi?id=204683
--- Comment #12 from Matthias Heinz (m...@familie-heinz.name) ---
My last update, because I have no way to go forward from here on.
This bug seems to go way back longer than I initially thought. I'm currently at
"drm-fixes-2018-08-31" in linux-dr
:u?wc??m5?^?㞾?}4-??z{b???r?+?׀u???ا#????ek
?W?J^?(???h}??-??z{b???r?Z+?jW.?\?oۊwb?
?v+)l?b?&??,?&??ξW???!jxw?ǫ?*'??+y?^??^?M:???r鞞֭???u??q?ky?ۊwb?
?v+)l?b?&??,?&?????uޮ?G???h
___
dri-devel m
DRM_IOCTL_DUMB_SET_LABEL lets you label GEM objects, making it
easier to debug issues in userspace applications.
Changes in v2:
- Hoist the IOCTL up into the drm_driver framework
Changes in v3:
- Introduce a drm_gem_set_label for drivers to use internally
in order to label a GEM object
On Fri, 11 Oct 2019 15:54:53 +0200
Andrzej Hajda wrote:
> On 26.08.2019 17:26, Boris Brezillon wrote:
> > The encoder->enable() can't report errors and is expected to always
> > succeed. If we call pm_runtime_put() in the exynos_dsi_enable() error
> > path (as currently done) we'll have unbalance
Hi,
On 08/10/2019 10:15, zhengbin wrote:
zhengbin (4):
drm/omap: Remove set but not used variable 'plane'
drm/omap: Remove set but not used variable 'tclk_trail'
drm/omap: Remove set but not used variable 'err' in hdmi5_audio_config
drm/omap: Remove set but not used variable 'err' in
On 10/10/2019 14:59, Jean-Jacques Hiblot wrote:
A first version of this work had been sent by Tomi Valkeinen in may 2017
(https://www.spinics.net/lists/dri-devel/msg140663.html).
This series adds a few new OMAP_BO flags to help the userspace manage
situations where it needs to use lots of buffer
https://bugs.freedesktop.org/show_bug.cgi?id=111763
--- Comment #11 from Marko Popovic ---
(In reply to takios+fdbugs from comment #10)
> (In reply to Marko Popovic from comment #9)
> > https://cgit.freedesktop.org/mesa/mesa/commit/
> > ?id=a2a68d551c1c2a4f13761ffa8f3f6f13fee7a384
> >
> > This m
On 26.08.2019 17:26, Boris Brezillon wrote:
> The encoder->enable() can't report errors and is expected to always
> succeed. If we call pm_runtime_put() in the exynos_dsi_enable() error
> path (as currently done) we'll have unbalanced get/put calls when
> encoder->disable() is called.
True
>
>
The vboxvideo driver provides its own implementation for fbdev emulation
and framebuffers. Both can be replaced by DRM's generic code.
All patches have been tested on VirtualBox 6.0.12.
Thomas Zimmermann (3):
drm/vboxvideo: Switch to generic fbdev emulation
drm/vboxvideo: Switch to drm_atomic
The vboxvideo driver provides struct drm_framebuffer_funcs.dirty_fb from
its own implementation. Switch over to drm_atomic_helper_dirty_fb() and
handle screen updates in the primary plane's atomic_update function.
With dirty_fb out of the way, we can further replace struct vbox_frammebuffer
with g
There's nothing special about vboxvideo's fbdev emulation that is
not provided by the generic implementation. Switch over and remove
the driver's code.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/vboxvideo/Makefile| 2 +-
drivers/gpu/drm/vboxvideo/vbox_drv.c | 14 +--
drivers/gp
The vboxvideo driver's struct vram_framebuffer stores a DRM framebuffer
with an assiciated GEM object. This functionality is also provided by
generic code. Switch vboxvideo over.
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/vboxvideo/vbox_drv.h | 14 ---
drivers/gpu/drm/vboxvideo/vb
On msm8998, vblank timeouts are observed because the DSI controller is not
reset properly, which ends up stalling the MDP. This is because the reset
logic is not correct per the hardware documentation.
The documentation states that after asserting reset, software should wait
some time (no indicat
https://bugs.freedesktop.org/show_bug.cgi?id=111763
--- Comment #10 from takios+fdb...@takios.de ---
(In reply to Marko Popovic from comment #9)
> https://cgit.freedesktop.org/mesa/mesa/commit/
> ?id=a2a68d551c1c2a4f13761ffa8f3f6f13fee7a384
>
> This might actually fix the ring_gfx type hangs or e
On Thu, Oct 10, 2019 at 02:17:44PM -0400, Sean Paul wrote:
> From: Sean Paul
>
> As Daniel mentions in his email [1], non-blocking commits don't hold the
> modeset locks, so we can safely access state as long as these functions
> are in the commit path. So remove the WARN_ON in dpu_kms_encoder_en
On Thu, Oct 10, 2019 at 02:55:02PM +0800, zhengbin wrote:
> zhengbin (4):
> drm/msm/mdp5: Remove set but not used variable 'fmt'
> drm/msm/mdp5: Remove set but not used variable 'hw_cfg' in blend_setup
> drm/msm/dsi: Remove set but not used variable 'lpx'
> drm/msm/dsi: Remove set but not u
On Wed, Oct 09, 2019 at 01:05:22PM +0100, Ben Dooks wrote:
> A number of the config structs are not exported so make
> them static to avoid the following sparse warnings:
>
> drivers/gpu/drm/msm/disp/mdp5/mdp5_cfg.c:17:26: warning: symbol
> 'msm8x74v1_config' was not declared. Should it be static
On Wed, Oct 09, 2019 at 09:44:06AM -0600, Jordan Crouse wrote:
> On Wed, Oct 09, 2019 at 12:46:07PM +0100, Ben Dooks wrote:
> > The a5xx_show and a5xx_gpu_state_put objects are not exported
> > outside of the file, so make them static to avoid the following
> > warnings from sparse:
> >
> > driver
Hi Inki,
On Mon, 26 Aug 2019 17:26:32 +0200
Boris Brezillon wrote:
> The encoder->enable() can't report errors and is expected to always
> succeed. If we call pm_runtime_put() in the exynos_dsi_enable() error
> path (as currently done) we'll have unbalanced get/put calls when
> encoder->disable(
On Fri, Oct 11, 2019 at 03:22:00PM +0200, Heiko Stübner wrote:
> Am Donnerstag, 10. Oktober 2019, 21:43:48 CEST schrieb Ezequiel Garcia:
> > New iteration, seems that we are finally converging.
> >
> > For this v5, we are only doing some changes on
> > the gamma_set implementation. As a result, th
On Fri, Oct 11, 2019 at 5:27 AM Hans de Goede wrote:
>
> Hi,
>
> On 10-10-2019 18:59, Daniel Vetter wrote:
> > On Thu, Oct 10, 2019 at 6:28 PM Hans de Goede wrote:
> >>
> >> Bail from the pci_driver probe function instead of from the drm_driver
> >> load function.
> >>
> >> This avoid /dev/dri/ca
Am Donnerstag, 10. Oktober 2019, 21:43:48 CEST schrieb Ezequiel Garcia:
> New iteration, seems that we are finally converging.
>
> For this v5, we are only doing some changes on
> the gamma_set implementation. As a result, the code
> is more readable. See the changelog in patch 2 for more
> inform
Convert the STM32 display binding to DT schema format using json-schema.
Split the original bindings in two yaml files:
- one for display controller (ltdc)
- one for DSI controller
Signed-off-by: Benjamin Gaignard
---
changes in v2:
- use BSD-2-Clause license
- add panel property
- fix identation
Already applied. thanks.
Alex
On Fri, Oct 11, 2019 at 2:48 AM Ben Dooks wrote:
>
> On 09/10/2019 13:14, Ben Dooks wrote:
> > The drm_sched_fence_ops_{scheduled,finished} are not exported
> > from the file so make them static to avoid the following
> > warnings from sparse:
> >
> > drivers/gpu/d
Hi Andrzej,
On Fri, Oct 11, 2019 at 01:21:43PM +0200, Andrzej Hajda wrote:
> On 11.10.2019 04:21, Xin Ji wrote:
> > The ANX7625 is an ultra-low power 4K Mobile HD Transmitter designed
> > for portable device. It converts MIPI to DisplayPort 1.3 4K.
> >
> > You can add support to your board with bi
On Thu, Oct 10, 2019 at 02:01:32PM -0700, Manasi Navare wrote:
> We no longer use the connection mutex and hence no need to
> define drm_device *dev, it causes a unused variable build warning
>
> Fixes: 83fa9842afe7 ("drm/dp-mst: Drop connection_mutex check")
> Cc: Sean Paul
Reviewed-by: Sean Pa
On 11/10/2019 12:56, Brian Starkey wrote:
> Hi,
>
> On Fri, Oct 11, 2019 at 11:14:43AM +0200, Neil Armstrong wrote:
>> Hi Brian,
>>
>> On 11/10/2019 10:41, Brian Starkey wrote:
>>> Hi Neil,
>>>
>>> On Thu, Oct 10, 2019 at 03:41:15PM +0200, Neil Armstrong wrote:
Hi Ayan,
On 10/10/201
Hi Andrzej,
On Fri, 11 Oct 2019 at 12:18, Andrzej Pietrasiewicz
wrote:
> @@ -32,6 +35,46 @@ rockchip_fb_alloc(struct drm_device *dev, const struct
> drm_mode_fb_cmd2 *mode_cm
> int ret;
> int i;
>
> + if (mode_cmd->modifier[0]) {
> + const struct drm_format_in
https://bugs.freedesktop.org/show_bug.cgi?id=111691
--- Comment #15 from Jaap Buurman ---
I am running into the same issue.
Arch
Kernel: 5.3.5
llvm: 9.0.0
Mesa: 19.2.0
xf86-video-amdgpu: 19.0.1
Linux-firmware: 20190923
Let me know if I can supply any additional information.
--
You are receivi
From: Michael Hennerich
For the special case when fbtft_mkdirty() is called with with -1 for the y
coordinate, the height is truncated by 1.
This isn't required, and causes the last line to not update.
Signed-off-by: Michael Hennerich
Signed-off-by: Alexandru Ardelean
---
drivers/staging/fbt
On 11.10.2019 04:21, Xin Ji wrote:
> The ANX7625 is an ultra-low power 4K Mobile HD Transmitter designed
> for portable device. It converts MIPI to DisplayPort 1.3 4K.
>
> You can add support to your board with binding.
>
> Example:
> anx7625_bridge: encoder@58 {
> compatible =
This patch adds support for afbc handling. afbc is a compressed format
which reduces the necessary memory bandwidth.
Co-developed-by: Mark Yao
Signed-off-by: Mark Yao
Signed-off-by: Andrzej Pietrasiewicz
---
drivers/gpu/drm/rockchip/Kconfig| 1 +
drivers/gpu/drm/rockchip/rockchip
This series adds AFBC support for Rockchip.
It is inspired by:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/refs/heads/factory-gru-9017.B-chromeos-4.4/drivers/gpu/drm/rockchip/rockchip_drm_vop.c
The first patch factors out some afbc helper functions from malidp,
as they are u
These are useful for other users of afbc, e.g. rockchip.
Signed-off-by: Andrzej Pietrasiewicz
---
drivers/gpu/drm/Kconfig | 4 ++
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/arm/Kconfig | 1 +
drivers/gpu/drm/arm/malidp_drv.c | 58 ++--
drivers/gpu/dr
Hi,
On Fri, Oct 11, 2019 at 11:14:43AM +0200, Neil Armstrong wrote:
> Hi Brian,
>
> On 11/10/2019 10:41, Brian Starkey wrote:
> > Hi Neil,
> >
> > On Thu, Oct 10, 2019 at 03:41:15PM +0200, Neil Armstrong wrote:
> >> Hi Ayan,
> >>
> >> On 10/10/2019 15:26, Ayan Halder wrote:
> >>> On Thu, Oct 10,
https://bugs.freedesktop.org/show_bug.cgi?id=111979
--- Comment #1 from udo ---
This is on AMD Ryzen 5 3400G with Radeon Vega Graphics, Fedora 30, git mesa,
git amdgpu, kernel.org kernel.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=111979
Bug ID: 111979
Summary: [5.2/5.3][drm:amdgpu_dm_atomic_commit_tail [amdgpu]]
*ERROR* Waiting for fences timed out or interrupted!
Product: DRI
Version: XOrg git
Hardware:
On Fri, Oct 11, 2019 at 02:20:47AM +, Xin Ji wrote:
> Hi all,
>
> The following series add initial support for the Slimport ANX7625
> transmitter, a
> ultra-low power Full-HD 4K MIPI to DP transmitter designed for portable
> device.
>
> This is the initial version, any mistakes, please let
On Friday, 11 October 2019 11:12:51 BST Lowry Li (Arm Technology China) wrote:
> Hi Mihail,
> On Fri, Oct 11, 2019 at 08:54:03AM +, Mihail Atanassov wrote:
> > Hi James, Lowry,
> >
> > On Friday, 11 October 2019 06:45:50 BST james qian wang (Arm Technology
> > China) wrote:
> > > From: "Lowry
On 10/10/2019 16:24, Tony Lindgren wrote:
Hmm so what register does this clock actually change?
I'm seeing an increase of few tens of extra mW, which means at
least one day of standby time less for me :) It does not happen
always, maybe half of the time.
I have no idea why this would affect p
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #83 from Pierre-Eric Pelloux-Prayer
---
Another kernel patch worth trying:
https://patchwork.freedesktop.org/patch/335077/
--
You are receiving this mail because:
You are the assignee for the bug.__
Hi Mihail,
On Fri, Oct 11, 2019 at 08:54:03AM +, Mihail Atanassov wrote:
> Hi James, Lowry,
>
> On Friday, 11 October 2019 06:45:50 BST james qian wang (Arm Technology
> China) wrote:
> > From: "Lowry Li (Arm Technology China)"
> >
> > Adds gamma and color-transform support for DOU-IPS.
> >
On Thu, Oct 10, 2019 at 01:15:09PM -0400, John Maguire wrote:
> Hi there,
>
> I wasn't sure which mailing list to use so I BCC'd
> intel-...@lists.freedesktop.org and dri-devel@lists.freedesktop.org
Just use Cc. We want all replies to go to the list(s) as well.
>
> I'm using a Lenovo Thinkpad T
https://bugs.freedesktop.org/show_bug.cgi?id=107877
Michel Dänzer changed:
What|Removed |Added
URL|https://www.monktech.us/|
--
You are receiving this mail becaus
Hi, james, ville syrjala, david,
在 2019/10/11 下午4:32, james qian wang (Arm Technology China) 写道:
On Fri, Oct 11, 2019 at 03:32:17PM +0800, sandy.huang wrote:
在 2019/10/11 下午3:22, james qian wang (Arm Technology China) 写道:
On Fri, Oct 11, 2019 at 03:07:22PM +0800, sandy.huang wrote:
在 2019/10/
On Thu, Oct 10, 2019 at 03:50:43PM +0200, Daniel Vetter wrote:
> On Thu, Oct 10, 2019 at 03:13:29PM +0200, Johan Hovold wrote:
> > Two old USB drivers had a bug in them which could lead to memory leaks
> > if an interrupted process raced with a disconnect event.
> >
> > Turns out we had a few more
Hi,
On 10-10-2019 18:59, Daniel Vetter wrote:
On Thu, Oct 10, 2019 at 6:28 PM Hans de Goede wrote:
Bail from the pci_driver probe function instead of from the drm_driver
load function.
This avoid /dev/dri/card0 temporarily getting registered and then
unregistered again, sending unwanted add
https://bugs.freedesktop.org/show_bug.cgi?id=107877
andrerushell changed:
What|Removed |Added
URL|https://www.monktech.us/Gma |https://www.monktech.us/
https://bugs.freedesktop.org/show_bug.cgi?id=107877
andrerushell changed:
What|Removed |Added
URL||https://www.monktech.us/Gma
Hi Brian,
On 11/10/2019 10:41, Brian Starkey wrote:
> Hi Neil,
>
> On Thu, Oct 10, 2019 at 03:41:15PM +0200, Neil Armstrong wrote:
>> Hi Ayan,
>>
>> On 10/10/2019 15:26, Ayan Halder wrote:
>>> On Thu, Oct 10, 2019 at 11:25:23AM +0200, Neil Armstrong wrote:
This adds all the OSD configuration
Hi James, Lowry,
On Friday, 11 October 2019 06:45:50 BST james qian wang (Arm Technology China)
wrote:
> From: "Lowry Li (Arm Technology China)"
>
> Adds gamma and color-transform support for DOU-IPS.
> Adds two caps members fgamma_coeffs and ctm_coeffs to komeda_improc_state.
> If color manage
Hi Neil,
On Thu, Oct 10, 2019 at 03:41:15PM +0200, Neil Armstrong wrote:
> Hi Ayan,
>
> On 10/10/2019 15:26, Ayan Halder wrote:
> > On Thu, Oct 10, 2019 at 11:25:23AM +0200, Neil Armstrong wrote:
> >> This adds all the OSD configuration plumbing to support the AFBC decoders
> >> path to display o
On Friday, 11 October 2019 06:45:42 BST james qian wang (Arm Technology China)
wrote:
> This function is for converting drm_color_ctm matrix to komeda hardware
> required required Q2.12 2's complement CSC matrix.
>
> v2:
> Move the fixpoint conversion function s31_32_to_q2_12() to drm core
>
On Fri, Oct 11, 2019 at 03:32:17PM +0800, sandy.huang wrote:
>
> 在 2019/10/11 下午3:22, james qian wang (Arm Technology China) 写道:
> > On Fri, Oct 11, 2019 at 03:07:22PM +0800, sandy.huang wrote:
> > > 在 2019/10/11 下午2:44, james qian wang (Arm Technology China) 写道:
> > > > On Fri, Oct 11, 2019 at 11
On Friday, 11 October 2019 06:45:35 BST james qian wang (Arm Technology China)
wrote:
> This function is used to convert drm 3dlut to komeda HW required 1d curve
> coeffs values.
>
> Signed-off-by: james qian wang (Arm Technology China)
>
> ---
> .../arm/display/komeda/komeda_color_mgmt.c|
https://bugs.freedesktop.org/show_bug.cgi?id=110361
--- Comment #6 from CI Bug Log ---
The CI Bug Log issue associated to this bug has been archived.
New failures matching the above filters will not be associated to this bug
anymore.
--
You are receiving this mail because:
You are the assignee
Hi James,
On Friday, 11 October 2019 06:45:27 BST james qian wang (Arm Technology China)
wrote:
> Add a new helper function drm_color_ctm_s31_32_to_qm_n() for driver to
> convert S31.32 sign-magnitude to Qm.n 2's complement that supported by
> hardware.
>
> Signed-off-by: james qian wang (Arm Te
1 - 100 of 118 matches
Mail list logo