Hi Dave,
On Fri, 22 Jun 2018 13:14:07 +1000 Dave Airlie wrote:
>
> drm-fixes is now in the same tree as drm-next
>
> git://git.freedesktop.org/git/drm/drm drm-fixes.
Hmmm, I have never had a drm-fixes tree ... but I have added it now, thanks.
Thanks for adding your subsystem tree as a
Hi Stephen,
drm-fixes is now in the same tree as drm-next
git://git.freedesktop.org/git/drm/drm drm-fixes.
Please update,
Thanks,
Dave.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On 21 June 2018 at 20:54, Gustavo Padovan wrote:
> drm-misc-next-2018-06-21:
> drm-misc-next for 4.19:
>
> Cross-subsystem Changes:
> - fix compile breakage on ION due to the dma-buf cleanups (Christian König)
> The following changes since commit daf0678c2036c918f01e4aa6035629d2debc2f30:
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=105725
higu...@gmx.net changed:
What|Removed |Added
CC||higu...@gmx.net
--- Comment #6 from
Acked-by: Chunming Zhou
-Original Message-
From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of
Andrey Grodzovsky
Sent: Thursday, June 21, 2018 11:33 PM
To: amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org
Cc: e...@anholt.net; Koenig, Christian ;
Hi Linus,
Just run of the mill fixes,
core: one regression fix in device unplug
qxl: one regression fix for might sleep in cursor handling
nouveau: one regression fix in multi-screen cursor handling
amdgpu: switch off DC by default on Kaveri and older and some minor fixes
i915: some GEM
On Fri, 2018-06-15 at 19:49 +0300, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Don't advertize non-exisiting crtcs in the encoder possible_crtcs
> bitmask.
>
How do we end up advertising non-existing CRTCs? encoder->crtc_mask
seems to be populated in the encoder init functions based on
On Fri, 2018-06-15 at 21:43 +0300, Ville Syrjälä wrote:
> On Fri, Jun 15, 2018 at 11:33:01AM -0700, Dhinakaran Pandiyan wrote:
> >
> > On Fri, 2018-06-15 at 19:49 +0300, Ville Syrjala wrote:
> > >
> > > From: Ville Syrjälä
> > >
> > > Each fake MST encoder is tied to a specific pipe. Fix the
>
Kevin Quigley writes:
> Hi,
>
> When we talk about control bus enable and video transfer enable for
> DSI, there is a mode in which control commands can be sent,
> interleaved with the video. This is often done at the end-of-frame
> and/or end of line. I've seen this handled in some other DSI
This allows panels or bridges that need to send DSI commands during
pre_enable() to successfully send them. We delay DISP0 (aka the
actual display) enabling until after pre_enable so that pixels aren't
streaming before then.
v2: Just clear out the encoder->bridge value to disable the midlayer
If a encoder name isn't specified for drm_encoder_init() it will try
to construct one based on the incoming encoder_type identifier. If the
caller passes an invalid encoder_type value the lookup could walk right
past the end of the table.
Signed-off-by: Jordan Crouse
---
The driver doesn't support scaling, but when an atomic test is done
it repeatedly spits out this warning which isn't particularly useful.
So just remove the error message.
Cc: Xinliang Liu
Cc: Rongrong Zou
Cc: Xinwei Kong
Cc: Chen Feng
Cc: David Airlie
Cc: Daniel Vetter
Cc: Peter Griffin
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #39 from fox...@ruin.net ---
(In reply to Michel Dänzer from comment #35)
> Created attachment 140257 [details] [review]
> drm/amdgpu: GPU vs CPU page size fixes in amdgpu_vm_bo_split_mapping
>
> Does this patch help?
Hi Michel,
https://bugs.freedesktop.org/show_bug.cgi?id=99851
--- Comment #59 from erhar...@mailbox.org ---
Tried kernel 4.17.2 and was surprised to see that this bug does not seem to
bother my G5 11,2 any longer! Now my HD 6450 passes all ring tests and I can
run X11 with glamor happily again. \o/
On Thu, Jun 21, 2018 at 11:16 PM, Daniel Vetter wrote:
> Hi all,
>
> The X.org board is soliciting proposals to host XDC in 2019. By the usual
> rotation a location in (North) America is preferred, but the board will also
> consider other locations, especially if there's an interesting
Hi all,
The X.org board is soliciting proposals to host XDC in 2019. By the usual
rotation a location in (North) America is preferred, but the board will also
consider other locations, especially if there's an interesting co-location
with another conference.
If you consider hosting XDC, we have
Jeykumar Sankaran writes:
> Qualcomm Snapdragon chipsets uses compressed format
> to optimize BW across multiple IP's. This change adds
> needed modifier support in drm for a simple 4x4 tile
> based compressed variants of base formats.
>
> Signed-off-by: Jeykumar Sankaran
This seems like a
This fixes a regression I accidentally reduced that was picked up by
kasan, where we were checking the CRTC atomic states after DRM's helpers
had already freed them. Example:
==
BUG: KASAN: use-after-free in
Linus Walleij writes:
> The Nomadik has a variant of the PL110 known as "Color LCD
> Controller" LCDC. This variant has the same bit ordering as
> the DRM subsystem (in difference from the other variants)
> and adds a few bits for the control of 5551, 565 etc in the
> control register. Notably
Drivers such as vc4 don't initialize mode_config.funcs until later in
initialization, but we know they're atomic since they've got the flag
set. This avoids oopsing on dereferencing funcs in the new atomic
methods sanity checks.
I moved the atomic check function down below the core flag check,
Hi Linus,
I love your patch! Perhaps something to improve:
[auto build test WARNING on tegra-drm/drm/tegra/for-next]
[also build test WARNING on v4.18-rc1 next-20180621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
https://bugs.freedesktop.org/show_bug.cgi?id=106957
Lukas Wunner changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
The TPO (Toppoly) TPG110 is a pretty generic display driver
similar in vein to the Ilitek 93xx devices. It is not a panel
per se but a driver used with several low-cost noname panels.
This is used on the Nomadik NHK15 combined with a OSD
OSD057VA01CT display for WVGA 800x480.
The driver is
The TPO TPG110 bindings were using the DPI bindings (popular
in the fbdev subsystem) but this misses the finer points
learned in the DRM subsystem.
We need to augment the bindings for proper DRM integration:
the timings are expressed by the hardware, not put into the
device tree.
Old device
The Nomadik has a variant of the PL110 known as "Color LCD
Controller" LCDC. This variant has the same bit ordering as
the DRM subsystem (in difference from the other variants)
and adds a few bits for the control of 5551, 565 etc in the
control register. Notably it also adds a packed RGB888
24BPP
Hi
Am 21.06.2018 um 18:29 schrieb Dieter Nützel:
> Am 21.06.2018 16:53, schrieb Christian König:
>> Am 21.06.2018 um 15:21 schrieb Thomas Zimmermann:
>>> TTM buffer objects provide ttm_bo_reference() and ttm_bo_unref() for
>>> managing reference counters. This patch set introduces ttm_bo_get()
Hi Ville,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.18-rc1 next-20180621]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Den 21.06.2018 09.14, skrev Daniel Vetter:
On Wed, Jun 20, 2018 at 05:28:10PM +0200, Noralf Trønnes wrote:
Den 20.06.2018 15.52, skrev Noralf Trønnes:
Den 20.06.2018 11.34, skrev Daniel Vetter:
On Mon, Jun 18, 2018 at 04:17:27PM +0200, Noralf Trønnes wrote:
This patchset adds generic fbdev
Daniel Vetter writes:
> On Wed, Jun 20, 2018 at 05:17:03PM -0700, Eric Anholt wrote:
>> This will be used by Mesa, and potentially other drivers in the
>> future, to describe tiled buffers.
>>
>> Signed-off-by: Eric Anholt
>> ---
>> include/uapi/drm/drm_fourcc.h | 21 +
>>
Am 21.06.2018 16:53, schrieb Christian König:
Am 21.06.2018 um 15:21 schrieb Thomas Zimmermann:
TTM buffer objects provide ttm_bo_reference() and ttm_bo_unref() for
managing reference counters. This patch set introduces ttm_bo_get()
and ttm_ot_put(), which follow Linux kernel conventions.
https://bugs.freedesktop.org/show_bug.cgi?id=106979
--- Comment #3 from Adam Williamson ---
Yup, confirmed, works fine with 4.18.0-0.rc1.git0.1.fc29. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugzilla.kernel.org/show_bug.cgi?id=199749
--- Comment #13 from Michel Dänzer (mic...@daenzer.net) ---
(In reply to notsyncing from comment #12)
> I updated to the current microcode files at linux-firmware.git.
Did you update the microcode files in the initrd as well?
--
You are
From: Ville Syrjälä
'psbfb' has been unused since commit c7cbed560ce2 ("drm/gma500:
Fix Medfield for drm_framebuffer move") so remove it entirely.
../drivers/gpu/drm/gma500/mdfld_intel_display.c: In function
‘mdfld__intel_pipe_set_base’:
../drivers/gpu/drm/gma500/mdfld_intel_display.c:170:26:
Hi Dave,
First feature request for 4.19. Highlights:
- Add initial amdgpu documentation
- Add initial GPU scheduler documention
- GPU scheduler fixes for dying processes
- Add support for the JPEG engine on VCN
- Switch CI to use powerplay by default
- EDC support for CZ
- More powerplay
Hi Dave,
First feature request for 4.19. Highlights:
- Add initial amdgpu documentation
- Add initial GPU scheduler documention
- GPU scheduler fixes for dying processes
- Add support for the JPEG engine on VCN
- Switch CI to use powerplay by default
- EDC support for CZ
- More powerplay
Am 21.06.2018 um 17:33 schrieb Andrey Grodzovsky:
Everything in the flush code path (i.e. waiting for SW queue
to become empty) names with *_flush()
and everything in the release code path names *_fini()
This patch also effect the amdgpu and etnaviv drivers which
use those functions.
v2:
Also
On Thu, Jun 21, 2018 at 03:24:49PM +0100, Emil Velikov wrote:
> Hi Jonathan,
>
> On 1 December 2016 at 04:18, Jonathan Gray wrote:
>
> > --- a/xf86drm.c
> > +++ b/xf86drm.c
> > @@ -3248,6 +3248,67 @@ drm_device_validate_flags(uint32_t flags)
> > */
> > int drmGetDevice2(int fd, uint32_t
Everything in the flush code path (i.e. waiting for SW queue
to become empty) names with *_flush()
and everything in the release code path names *_fini()
Signed-off-by: Andrey Grodzovsky
Suggested-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 2 +-
Everything in the flush code path (i.e. waiting for SW queue
to become empty) names with *_flush()
and everything in the release code path names *_fini()
This patch also effect the amdgpu and etnaviv drivers which
use those functions.
v2:
Also apply the change to vd3.
Signed-off-by: Andrey
Hi
>> This patch set introduces ttm_bo_get() and ttm_bo_put(), and converts
>> TTM to the new functions. The old functions remain in place until all
>> callers have been converted.
>
> Thanks, series is Reviewed-by: Christian König
> and I'm going to pick it up for our
> internal TTM branch.
>
>
Am 21.06.2018 um 15:21 schrieb Thomas Zimmermann:
TTM buffer objects provide ttm_bo_reference() and ttm_bo_unref() for
managing reference counters. This patch set introduces ttm_bo_get()
and ttm_ot_put(), which follow Linux kernel conventions.
A call to ttm_bo_unref() clears the supplied
Hi Jonathan,
On 1 December 2016 at 04:18, Jonathan Gray wrote:
> --- a/xf86drm.c
> +++ b/xf86drm.c
> @@ -3248,6 +3248,67 @@ drm_device_validate_flags(uint32_t flags)
> */
> int drmGetDevice2(int fd, uint32_t flags, drmDevicePtr *device)
> {
> +#ifdef __OpenBSD__
> +/*
> + * DRI
drm-misc-fixes-2018-06-21:
Fixes for v4.18-rc2:
- A reversion of a commit in drm/sun4i to fix a run-time fault.
- Various fixes to the sii8620 bridge.
- Small bugfix to correctly check stride in atmel-hlcdc.
The following changes since commit c32048d9e93a5ab925d745396c63e7b912147f0a:
https://bugs.freedesktop.org/show_bug.cgi?id=106993
Bug ID: 106993
Summary: general protection fault in mutex_lock /
drm_mode_object_unregister when unloading amdgpu
Product: DRI
Version: unspecified
Hardware: Other
On Wed, Jun 20, 2018 at 04:03:58PM +0300, Mikko Perttunen wrote:
> Here we are checking for the buffer length, not an offset for writing
> to, so using > is correct. The current code incorrectly rejects a
> command buffer ending at the memory buffer's end.
>
> Signed-off-by: Mikko Perttunen
>
https://bugzilla.kernel.org/show_bug.cgi?id=199749
--- Comment #12 from notsyncing (song...@gmail.com) ---
I updated to the current microcode files at linux-firmware.git. Today I
replicated the same workload, and my computer freezed in just 5 minutes! Even
sysrq does not work. I have to do a hard
A call to ttm_bo_unref() clears the supplied pointer to NULL, while
ttm_bo_put() does not. None of the converted call sites requires the
pointer to become NULL, so the respective assign operations has been
left out from the patch.
Signed-off-by: Thomas Zimmermann
---
Signed-off-by: Thomas Zimmermann
---
drivers/gpu/drm/ttm/ttm_bo_util.c | 3 ++-
drivers/gpu/drm/ttm/ttm_bo_vm.c | 10 ++
2 files changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
b/drivers/gpu/drm/ttm/ttm_bo_util.c
index
The TTM buffer-object interface provides ttm_bo_reference() and
ttm_bo_unref() for managing reference counts. Replacing them with
ttm_bo_get() and ttm_bo_put() aligns the API with conventions used
throughout the Linux kernel.
The implementation of ttm_bo_unref() clears the supplied pointer
to
TTM buffer objects provide ttm_bo_reference() and ttm_bo_unref() for
managing reference counters. This patch set introduces ttm_bo_get()
and ttm_ot_put(), which follow Linux kernel conventions.
A call to ttm_bo_unref() clears the supplied pointer to NULL. This is
unnecessary in most cases and
On Tue, Jun 19, 2018 at 04:43:37PM +0530, Kiran Gunda wrote:
> Restructure the qcom-wled bindings for the better readability.
>
> Signed-off-by: Kiran Gunda
Acked-by: Daniel Thompson
> ---
> .../bindings/leds/backlight/qcom-wled.txt | 110
> -
> 1 file changed,
On Thu, Jun 21, 2018 at 02:05:59PM +0100, Daniel Thompson wrote:
> On Tue, Jun 19, 2018 at 04:43:36PM +0530, Kiran Gunda wrote:
> > pm8941-wled.c driver is supporting the WLED peripheral
> > on pm8941. Rename it to qcom-wled.c so that it can support
> > WLED on multiple PMICs.
> >
> >
https://bugzilla.kernel.org/show_bug.cgi?id=199425
--- Comment #10 from mikita.lip...@amd.com (mikita.lip...@amd.com) ---
Johannes,
My patch wasn't merged into DRM, but Daniel Vetter proposed another patch that
might remove legacy code that causes the issue. Could you remove my patch from
your
On Tue, Jun 19, 2018 at 04:43:36PM +0530, Kiran Gunda wrote:
> pm8941-wled.c driver is supporting the WLED peripheral
> on pm8941. Rename it to qcom-wled.c so that it can support
> WLED on multiple PMICs.
>
> Signed-off-by: Kiran Gunda
With changes proposed for v4:
Acked-by: Daniel Thompson
>
[cc += dri-devel, cc -= alsa-devel]
On Wed, Jun 20, 2018 at 10:28:37PM +, p...@cooco.de wrote:
> On Wed, 20 Jun 2018 12:14:32 +0200, Takashi Iwai wrote:
> > I guess it would work with a quirk. The EPSS and CLKSTOP checks are
> > just to assure the modern codec PM, and GPU is always
https://bugs.freedesktop.org/show_bug.cgi?id=106992
Bug ID: 106992
Summary: Radeon Failed to create EGL context
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity:
This patch adds the struct drm_connector_helper_funcs with some
necessary hooks. Additionally, it also adds some missing hooks at
drm_connector_funcs.
Signed-off-by: Rodrigo Siqueira
---
drivers/gpu/drm/vkms/vkms_drv.c| 6 --
drivers/gpu/drm/vkms/vkms_drv.h| 9 +
This patch adds the struct drm_plane_helper_funcs and the required atomic
hooks.
Signed-off-by: Rodrigo Siqueira
---
drivers/gpu/drm/vkms/vkms_plane.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/gpu/drm/vkms/vkms_plane.c
b/drivers/gpu/drm/vkms/vkms_plane.c
This patch adds the basic hook required to create framebuffer which is
necessary for providing some of the vkms features.
Signed-off-by: Rodrigo Siqueira
---
drivers/gpu/drm/vkms/vkms_drv.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vkms/vkms_drv.c
Currently, we are trying to make VKMS pass in the kms_flip test (IGT).
As a result, we made a series of small changes in the module with the
goal to meet some of the necessary steps required by kms_flip. This
patchset comprises all the simple modifications used until now to make
the kms_flip
This patch adds the struct drm_crtc_helper_funcs with simple
atomic_check and atomic_enable functions.
Signed-off-by: Rodrigo Siqueira
---
drivers/gpu/drm/vkms/vkms_crtc.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/drivers/gpu/drm/vkms/vkms_crtc.c
VKMS currently does not handle dumb data, and as a consequence, it does
not provide mechanisms for handling gem. This commit adds the necessary
support for gem object/handler and the dumb functions.
Signed-off-by: Rodrigo Siqueira
---
drivers/gpu/drm/vkms/Makefile | 2 +-
Hi Dave, i915 fixes, nothing out of the ordinary.
drm-intel-fixes-2018-06-21:
drm/i915 fixes for v4.18-rc2:
- Mostly cc: stable display fixes, including a DBLSCAN regression fix
- GEM fixes for this merge window
BR,
Jani.
The following changes since commit
On 06/21, Daniel Vetter wrote:
> On Wed, Jun 20, 2018 at 02:43:03PM -0300, Rodrigo Siqueira wrote:
> > Currently, we are trying to make VKMS pass in the kms_flip test (IGT).
> > As a result, we made a series of small changes in the module with the
> > goal to meet some of the necessary steps
https://bugs.freedesktop.org/show_bug.cgi?id=106989
--- Comment #1 from Chris Wilson ---
The test doesn't do anything, all it was was a placeholder to show how to
reload i915 with gvt enabled. It was meant to be replaced by a suite of tests
for gvt, but that never happened and we still have no
https://bugs.freedesktop.org/show_bug.cgi?id=106989
Bug ID: 106989
Summary: [CI] igt@gvt_basic@invalid-placeholder-test is badly
named
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #38 from fox...@ruin.net ---
(In reply to Michel Dänzer from comment #37)
> (In reply to foxbat from comment #36)
> > It looks like the patch isn't fully applying (using tree 4.17):
>
> It should apply to 4.17. Did you revert Ben's
Am 21.06.2018 um 08:30 schrieb Daniel Vetter:
On Thu, Jun 21, 2018 at 8:26 AM, Daniel Vetter wrote:
On Wed, Jun 20, 2018 at 4:21 PM, Christian König
wrote:
Am 20.06.2018 um 16:04 schrieb Christian König:
Am 20.06.2018 um 14:52 schrieb Daniel Vetter:
On Wed, Jun 20, 2018 at 2:46 PM,
* Thomas Hellstrom wrote:
> On 06/19/2018 11:45 AM, Peter Zijlstra wrote:
> > I suspect you want this through the DRM tree? Ingo are you OK with that?
>
>
> Yes, I can ask Dave to pull this. Ingo?
Sure, no problem if it's tested and all:
Acked-by: Ingo Molnar
Thanks,
Ingo
drm-misc-next-2018-06-21:
drm-misc-next for 4.19:
Cross-subsystem Changes:
- fix compile breakage on ION due to the dma-buf cleanups (Christian König)
The following changes since commit daf0678c2036c918f01e4aa6035629d2debc2f30:
Merge branch 'drm-next-4.18' of
On 23.01.2018 12:17, Maciej Purski wrote:
> Currently packed pixel modes in MHL2 can't be displayed. The device
> automatically recognizes output format, so setting format other than
> RGB causes failure. Fix it by writing proper values to registers.
>
> Tested on MHL1 and MHL2 using various
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #37 from Michel Dänzer ---
(In reply to foxbat from comment #36)
> It looks like the patch isn't fully applying (using tree 4.17):
It should apply to 4.17. Did you revert Ben's debugging patches before applying
it?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #36 from fox...@ruin.net ---
(In reply to Michel Dänzer from comment #35)
> Created attachment 140257 [details] [review]
> drm/amdgpu: GPU vs CPU page size fixes in amdgpu_vm_bo_split_mapping
>
> Does this patch help?
It looks
Am 21.06.2018 um 08:34 schrieb Daniel Vetter:
On Wed, Jun 20, 2018 at 08:52:19PM +0200, Christian König wrote:
Fixup for "dma_buf: remove device parameter from attach callback v2".
I missed this driver, sorry for the noise. Patch is not even compile
tested.
Signed-off-by: Christian König
Hi Gustavo,
Am 21.06.2018 um 02:58 schrieb Gustavo Padovan:
Hi Dave,
our first pull for 4.19, over 90 patches here, probably the most important
ones are for the writeback connector support. Then we have a bunch of
fixes to drivers, some interesting core cleanups and new panel drivers.
This
https://bugs.freedesktop.org/show_bug.cgi?id=106258
--- Comment #35 from Michel Dänzer ---
Created attachment 140257
--> https://bugs.freedesktop.org/attachment.cgi?id=140257=edit
drm/amdgpu: GPU vs CPU page size fixes in amdgpu_vm_bo_split_mapping
Does this patch help?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=102666
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #2 from Christian
https://bugs.freedesktop.org/show_bug.cgi?id=106940
Michel Dänzer changed:
What|Removed |Added
Attachment #140251|text/x-log |text/plain
mime type|
On Wednesday, 20 June 2018 16:03:58 MSK Mikko Perttunen wrote:
> Here we are checking for the buffer length, not an offset for writing
> to, so using > is correct. The current code incorrectly rejects a
> command buffer ending at the memory buffer's end.
>
> Signed-off-by: Mikko Perttunen
> ---
On 06/20/2018 02:06 PM, Rodrigo Vivi wrote:
On Wed, Jun 20, 2018 at 08:31:00AM -0500, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1470102 ("Missing break in switch")
Any other
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
Addresses-Coverity-ID: 1470102 ("Missing break in switch")
Signed-off-by: Gustavo A. R. Silva
---
drivers/gpu/drm/i915/intel_dpll_mgr.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Dne sobota, 16. junij 2018 ob 07:48:38 CEST je Chen-Yu Tsai napisal(a):
> On Sat, Jun 16, 2018 at 1:33 AM, Jernej Škrabec
wrote:
> > Dne petek, 15. junij 2018 ob 19:13:17 CEST je Chen-Yu Tsai napisal(a):
> >> On Sat, Jun 16, 2018 at 12:41 AM, Jernej Škrabec
> >>
> >> wrote:
> >> > Hi,
> >> >
On Wednesday, 20 June 2018 13:10:07 MSK Daniel Vetter wrote:
> On Wed, Jun 20, 2018 at 11:33 AM, Russell King - ARM Linux
>
> wrote:
> > On Wed, Jun 20, 2018 at 11:17:50AM +0200, Daniel Vetter wrote:
> >> Yes -modesetting (or whichever other driver) would need to set up the
> >> properties
On 2018-06-21 00:35, Rob Herring wrote:
> On Tue, Jun 19, 2018 at 04:43:38PM +0530, Kiran Gunda wrote:
>
>> Update the bindings with the new properties used for
>> PMI8998.
>>
>> Signed-off-by: Kiran Gunda
>> ---
>> .../bindings/leds/backlight/qcom-wled.txt | 84
>>
In the quest to remove all stack VLA usage from the kernel[1], this
sets the buffer to maximum size and adds a sanity check.
[1]
https://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qpxydaacu1rq...@mail.gmail.com
Signed-off-by: Kees Cook
---
drivers/gpu/drm/i2c/tda9950.c | 5 -
1
On 2018-06-20 11:52, Bjorn Andersson wrote:
On Tue 19 Jun 04:13 PDT 2018, Kiran Gunda wrote:
The auto string detection algorithm checks if the current WLED
sink configuration is valid. It tries enabling every sink and
checks if the OVP fault is observed. Based on this information
it detects
On Wed, Jun 20, 2018 at 11:17:50AM +0200, Daniel Vetter wrote:
> Yes -modesetting (or whichever other driver) would need to set up the
> properties correctly for Xvideo color keying. Since default assumption for
> all other (generic) compositors is that planes won't do any color keying
> in the
On 2018-06-20 11:17, Vinod wrote:
On 19-06-18, 16:43, Kiran Gunda wrote:
struct wled {
const char *name;
struct device *dev;
struct regmap *regmap;
+ struct mutex lock; /* Lock to avoid race from ISR */
the comment is wrong as you avoid race with thread
On 2018-06-20 10:44, Bjorn Andersson wrote:
On Tue 19 Jun 04:13 PDT 2018, Kiran Gunda wrote:
WLED4 peripheral is present on some PMICs like pmi8998 and
pm660l. It has a different register map and configurations
are also different. Add support for it.
Signed-off-by: Kiran Gunda
---
In the quest to remove all stack VLA usage from the kernel[1], this
uses the maximum sane buffer size and removes copy/paste code.
[1]
https://lkml.kernel.org/r/CA+55aFzCG-zNmZwX4A2FQpadafLfEzK6CC=qpxydaacu1rq...@mail.gmail.com
Signed-off-by: Kees Cook
---
On Tuesday, 19 June 2018 20:40:12 MSK Russell King - ARM Linux wrote:
> On Tue, May 29, 2018 at 10:11:03AM +0300, Ville Syrjälä wrote:
> > On Tue, May 29, 2018 at 02:48:22AM +0300, Dmitry Osipenko wrote:
> > > Though maybe "color components replacement" and "replacement with a
> > > complete
On Wed, 20 Jun 2018, "Gustavo A. R. Silva" wrote:
> On 06/20/2018 02:06 PM, Rodrigo Vivi wrote:
>> On Wed, Jun 20, 2018 at 08:31:00AM -0500, Gustavo A. R. Silva wrote:
>>> In preparation to enabling -Wimplicit-fallthrough, mark switch cases
>>> where we are expecting to fall through.
>>>
>>>
On Wed, Jun 20, 2018 at 02:43:03PM -0300, Rodrigo Siqueira wrote:
> Currently, we are trying to make VKMS pass in the kms_flip test (IGT).
> As a result, we made a series of small changes in the module with the
> goal to meet some of the necessary steps required by kms_flip. This
> patchset
On Wed, Jun 20, 2018 at 05:28:10PM +0200, Noralf Trønnes wrote:
>
> Den 20.06.2018 15.52, skrev Noralf Trønnes:
> >
> > Den 20.06.2018 11.34, skrev Daniel Vetter:
> > > On Mon, Jun 18, 2018 at 04:17:27PM +0200, Noralf Trønnes wrote:
> > > > This patchset adds generic fbdev emulation for drivers
On Wed, Jun 20, 2018 at 05:17:03PM -0700, Eric Anholt wrote:
> This will be used by Mesa, and potentially other drivers in the
> future, to describe tiled buffers.
>
> Signed-off-by: Eric Anholt
> ---
> include/uapi/drm/drm_fourcc.h | 21 +
> 1 file changed, 21 insertions(+)
https://bugzilla.kernel.org/show_bug.cgi?id=198551
Alex (linux...@libero.it) changed:
What|Removed |Added
CC||linux...@libero.it
---
On Wed, Jun 20, 2018 at 08:52:19PM +0200, Christian König wrote:
> Fixup for "dma_buf: remove device parameter from attach callback v2".
>
> I missed this driver, sorry for the noise. Patch is not even compile
> tested.
>
> Signed-off-by: Christian König
Reviewed-by: Daniel Vetter
Also
On Thu, Jun 21, 2018 at 8:26 AM, Daniel Vetter wrote:
> On Wed, Jun 20, 2018 at 4:21 PM, Christian König
> wrote:
>> Am 20.06.2018 um 16:04 schrieb Christian König:
>>>
>>> Am 20.06.2018 um 14:52 schrieb Daniel Vetter:
On Wed, Jun 20, 2018 at 2:46 PM, Christian König
wrote:
>
On Wed, Jun 20, 2018 at 4:21 PM, Christian König
wrote:
> Am 20.06.2018 um 16:04 schrieb Christian König:
>>
>> Am 20.06.2018 um 14:52 schrieb Daniel Vetter:
>>>
>>> On Wed, Jun 20, 2018 at 2:46 PM, Christian König
>>> wrote:
[SNIP]
>
> Go ahead, that's the point of commit
99 matches
Mail list logo
