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| 52 +++
.../arm/display/komeda/komeda_color_mgmt.h| 9 +++-
2 files changed, 60
This function is used to convert drm_color_ctm S31.32 sign-magnitude
value to komeda required Q2.12 2's complement
Signed-off-by: james qian wang (Arm Technology China)
---
.../arm/display/komeda/komeda_color_mgmt.c| 27 +++
.../arm/display/komeda/komeda_color_mgmt.h| 1
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 management changed, set gamma and color-transform accordingly.
Signed-off-by: Lowry Li (Arm Technology China)
---
This series enable CRTC color-mgmt for komeda driver, for current komeda HW
which only supports color conversion and forward gamma for CRTC.
This series actually are regrouped from:
- drm/komeda: Enable layer/plane color-mgmt:
https://patchwork.freedesktop.org/series/60893/
- drm/komeda:
In function sii902x_connector_detect(), variable "status" could be
initialized if regmap_read() fails. However, "status" is used to
decide the return value, which is potentially unsafe.
Signed-off-by: Yizhuo
---
drivers/gpu/drm/bridge/sii902x.c | 2 +-
1 file changed, 1 insertion(+), 1
In fbtft_framebuffer_alloc the error handling path should take care of
releasing frame buffer after it is allocated via framebuffer_alloc, too.
Therefore, in two failure cases the goto destination is changed to
address this issue.
Fixes: c296d5f9957c ("staging: fbtft: core support")
https://bugzilla.kernel.org/show_bug.cgi?id=204181
--- Comment #61 from jamespharve...@gmail.com ---
It might look like I'm just ranting. That's not the reason I posted my
comment. I'm trying to give feedback to AMD about how bad so many customer
experiences are right now, and have been for
https://bugzilla.kernel.org/show_bug.cgi?id=204181
--- Comment #60 from jamespharve...@gmail.com ---
(In reply to Sergey Kondakov from comment #59)
>
> And how about instead of knowingly pushing untested code with known fatal
> errors you stop taking QA notes from FGLRX in the first place and do
https://bugzilla.kernel.org/show_bug.cgi?id=204181
--- Comment #59 from Sergey Kondakov (virtuous...@gmail.com) ---
(In reply to Andrey Grodzovsky from comment #57)
> Sergey, instead of throwing tantrums why can't you just do what you are
> asked ? You present an extremely convoluted set of
> Hello folks,
>
>
> could anybody please give me some more insight, how switching
> from X to console (ctrl+alt+f*) actually works ?
>
> Who catches the keypress event and initiates the VT switch ?
> The Xserver ? Could this be done in the kernel (eg. when Xserver
> is hanging) ?
The X server is
On 9/29/19 3:28 AM, jun.zh...@intel.com wrote:
From: zhang jun
we see tons of warning like:
[ 45.846872] x86/PAT: NDK MediaCodec_:3753 map pfn RAM range req
write-combining for [mem 0x1e7a8-0x1e7a87fff], got write-back
[ 45.848827] x86/PAT: .vorbis.decoder:4088 map pfn RAM range req
Hi,
> On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> > Currently the property docs don't specify whether it's okay for two planes
> > to
> > have the same zpos value and what user-space should expect in this case.
> >
> > The rule mentionned in the past was to disambiguate with
> v2: moved the released into goto error handlings
A better version comment should be moved below the triple dashes.
Will the tag “Fixes” be added?
> @@ -393,6 +395,16 @@ static int acp_hw_init(void *handle)
> val &= ~ACP_SOFT_RESET__SoftResetAud_MASK;
>
Hi Alex,
> -Original Message-
> From: Alex Williamson
> Sent: Tuesday, September 24, 2019 6:07 PM
> To: Jason Wang
> Cc: k...@vger.kernel.org; linux-s...@vger.kernel.org; linux-
> ker...@vger.kernel.org; dri-devel@lists.freedesktop.org; intel-
> g...@lists.freedesktop.org;
Fixes gcc '-Wunused-but-set-variable' warning:
rivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c: In function
‘amdgpu_gfx_graphics_queue_acquire’:
drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c:234:16: warning:
variable ‘pipe’ set but not used [-Wunused-but-set-variable]
It is never used, so can be removed.
dma_alloc_coherent has already zeroed the memory.
So memset is not needed.
Signed-off-by: Saurav Girepunje
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c
b/drivers/gpu/drm/amd/amdgpu/amdgpu_ih.c
index
Hello folks,
could anybody please give me some more insight, how switching
from X to console (ctrl+alt+f*) actually works ?
Who catches the keypress event and initiates the VT switch ?
The Xserver ? Could this be done in the kernel (eg. when Xserver
is hanging) ?
--mtx
--
Enrico Weigelt,
https://bugs.freedesktop.org/show_bug.cgi?id=110674
--- Comment #151 from line...@xcpp.org ---
Created attachment 145583
--> https://bugs.freedesktop.org/attachment.cgi?id=145583=edit
5.3.1 patched, xorg crash
And here is a dmesg of just an X session crashing
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=110674
line...@xcpp.org changed:
What|Removed |Added
Attachment #145581|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=110674
line...@xcpp.org changed:
What|Removed |Added
CC||line...@xcpp.org
--- Comment #149
https://bugs.freedesktop.org/show_bug.cgi?id=111747
--- Comment #13 from CI Bug Log ---
A CI Bug Log filter associated to this bug has been updated:
{- TGL: igt@* -incomplete - Abort requested by .* terminating children -}
{+ TGL: igt@* -incomplete - Abort requested by .* terminating children
https://bugzilla.kernel.org/show_bug.cgi?id=204181
Damian Nowak (s...@nowaker.net) changed:
What|Removed |Added
CC||s...@nowaker.net
---
https://bugs.freedesktop.org/show_bug.cgi?id=111747
--- Comment #12 from CI Bug Log ---
A CI Bug Log filter associated to this bug has been updated:
{- TGL: igt@* -incomplete - Abort requested by .* terminating children -}
{+ TGL: igt@* -incomplete - Abort requested by .* terminating children
>
> On Mon, Sep 23, 2019 at 1:28 PM Pintu Agarwal wrote:
> >
> > Dear Philipp,
> >
> > I have a iMX6dl custom board with custom Linux Kernel 4.8.
> > I have both LCD and HDMI connected to the board.
> > And we are using weston/wayland as the display interface.
> > In normal boot, both LCD and
Dear all,
(please Cc)
linux 5.3.1
Debian/sid
Lenovo X260
[2.472152] i915 :00:02.0: vgaarb: deactivate vga console
[2.473035] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[2.473037] [drm] Driver supports precise vblank timestamp query.
[2.473431] i915
On Sun, Sep 29, 2019 at 03:28:41PM +0800, jun.zh...@intel.com wrote:
> From: zhang jun
>
> we see tons of warning like:
> [ 45.846872] x86/PAT: NDK MediaCodec_:3753 map pfn RAM range req
> write-combining for [mem 0x1e7a8-0x1e7a87fff], got write-back
> [ 45.848827] x86/PAT:
From: zhang jun
we see tons of warning like:
[ 45.846872] x86/PAT: NDK MediaCodec_:3753 map pfn RAM range req
write-combining for [mem 0x1e7a8-0x1e7a87fff], got write-back
[ 45.848827] x86/PAT: .vorbis.decoder:4088 map pfn RAM range req
write-combining for [mem 0x1e7a58000-0x1e7a58fff],
Mark a job as secure, if and only if the command
submission flag has the secure flag set.
v2: fix the null job pointer while in vmid 0
submission.
v3: Context --> Command submission.
v4: filling cs parser with cs->in.flags
v5: move the job secure flag setting out of amdgpu_cs_submit()
https://bugs.freedesktop.org/show_bug.cgi?id=111729
--- Comment #2 from p...@phi-gamma.net ---
I can confirm this bug.
Same phenomenology here with 5.2.11, two screens, and a
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Lexa
PRO [Radeon RX 550/550X] (rev c7)
Sep 29
On Mon, Sep 23, 2019 at 10:10:26AM +, Mihail Atanassov wrote:
> When initially turning a crtc on, drm_reset_vblank_timestamp will
> set the vblank timestamp to 0 for any driver that doesn't provide
> a ->get_vblank_timestamp() hook.
>
> Unfortunately, the FLIP_COMPLETE event depends on that
On Mon, Sep 23, 2019 at 12:39:20PM +, Simon Ser wrote:
> Currently the property docs don't specify whether it's okay for two planes to
> have the same zpos value and what user-space should expect in this case.
>
> The rule mentionned in the past was to disambiguate with object IDs. However
>
On Fri, Sep 27, 2019 at 9:57 PM Steven Price wrote:
>
> On 27/09/2019 14:46, Qiang Yu wrote:
> > drm_gem_objects_lookup does not use user space bo handles
> > directly and left the user to kernel copy work to a new
> > interface drm_gem_objects_lookup_user.
> >
> > This is for driver like lima
32 matches
Mail list logo