https://bugs.freedesktop.org/show_bug.cgi?id=110371
--- Comment #2 from babblebo...@gmail.com ---
Created attachment 143957
--> https://bugs.freedesktop.org/attachment.cgi?id=143957&action=edit
Dmesg output from an affected kernel
Here is the issue, you can see
[1.335096] [drm:dc_link_detec
On Thu, Apr 11, 2019 at 10:49 PM Gerd Hoffmann wrote:
>
> On Thu, Apr 11, 2019 at 06:36:15PM -0700, Gurchetan Singh wrote:
> > On Wed, Apr 10, 2019 at 10:03 PM Gerd Hoffmann wrote:
> > >
> > > > > +/* VIRTIO_GPU_CMD_RESOURCE_CREATE_V2 */
> > > > > +struct virtio_gpu_cmd_resource_create_v2 {
> > >
Hi,
On Mon, Apr 8, 2019 at 9:26 AM Urja Rannikko wrote:
>
> Hi,
>
> On Mon, Apr 8, 2019 at 3:21 PM Doug Anderson wrote:
> >
> > Hi,
> >
> > On Sat, Apr 6, 2019 at 6:16 PM Urja Rannikko wrote:
> > >
> > > Hi,
>
> > >
> > > The difference would be in this format just setting hfront-porch = 87
>
Hi Bartlomiej,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.1-rc4 next-20190412]
[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
Hi,
I am still new to virgl, and missed the last round of discussion about
resource_create_v2.
>From the discussion below, semantically resource_create_v2 creates a host
resource object _without_ any storage; memory_create creates a host memory
object which provides the storage. Is that correct?
Hi Bartlomiej,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.1-rc4 next-20190412]
[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
https://bugs.freedesktop.org/show_bug.cgi?id=110355
--- Comment #9 from Diego Viola ---
I get the same problem with GNOME 3.32 on archlinux (Wayland and GNOME Xorg).
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-deve
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #80 from dwagner ---
(In reply to Jaap Buurman from comment #79)
> I am also running into the same issue. I have two questions that might help
> tracking down why we are having issues, but not all people that are running
> a Vega gra
https://bugs.freedesktop.org/show_bug.cgi?id=110214
--- Comment #78 from Diego Viola ---
Created attachment 143956
--> https://bugs.freedesktop.org/attachment.cgi?id=143956&action=edit
clinfo -A output
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #79 from Jaap Buurman ---
I am also running into the same issue. I have two questions that might help
tracking down why we are having issues, but not all people that are running a
Vega graphics card.
1)
What is the output of the fo
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #6 from Jaap Buurman ---
Another question: What is the output of the following command for you guys?
cat /sys/class/drm/card0/device/vbios_version
I am running the following version:
113-D0500100-103
According to the techpowerup
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #5 from Jaap Buurman ---
I have the exact same problem with my Vega 64. Crashes when playing games.
Happens with Vulkan games (RADV), OpenGL games (RadeonSI) and DirectX 9 games
via Wine (Gallium9). It happens only for some games, pr
On Fri, Apr 12, 2019 at 04:04:18PM +, Thomas Hellstrom wrote:
> This is basically apply_to_page_range with added functionality:
> Allocating missing parts of the page table becomes optional, which
> means that the function can be guaranteed not to error if allocation
> is disabled. Also passing
https://bugs.freedesktop.org/show_bug.cgi?id=108044
Chris Wilson changed:
What|Removed |Added
QA Contact|intel-gfx-bugs@lists.freede |
|sktop.org
Hi,
On Tue, Apr 2, 2019 at 4:38 AM Heiko Stuebner wrote:
>
> From: Vicente Bergas
>
> As explained by Robin Murphy:
> > the IOMMU shutdown disables paging, so if the VOP is still
> > scanning out then that will result in whatever IOVAs it was using now going
> > straight out onto the bus as phys
On Fri, Apr 12, 2019 at 12:05:29PM -0400, sunpeng...@amd.com wrote:
> From: Leo Li
>
> Hi all,
>
> This is a follup to this change made by Ville to add MST aux nodes:
> https://github.com/vsyrjala/linux/commit/cac63f799ee2f5fbbe4f0a375383f13e03d640a5
> Patch 2/2 describes what I added on top.
C
On Fri, Apr 12, 2019 at 5:56 AM Bartlomiej Zolnierkiewicz
wrote:
>
> 'default n' is the default value for any bool or tristate Kconfig
> setting so there is no need to write it explicitly.
>
> Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
> is not set' for visible symbols") th
From: Leo Li
In preparation for adding aux devices for DP MST:
1. A non-cyclic idr is used for the device minor version. That way,
hotplug cycling MST devices won't needlessly increment the minor
version index.
2. A suffix option is added to the aux device file name. It can be used
to i
From: Ville Syrjälä
Expose AUX devices for MST ports, similar to how they are exposed for
SST.
The registered device will have it's MST port path appended in order to
identify it. i.e. /dev/drm_dp_aux4_mst:0-2-1
So for a MST topology like so:
+-+
| ASIC
From: Leo Li
Hi all,
This is a follup to this change made by Ville to add MST aux nodes:
https://github.com/vsyrjala/linux/commit/cac63f799ee2f5fbbe4f0a375383f13e03d640a5
Patch 2/2 describes what I added on top.
Sending as an RFC since there are some items I'm not certain on:
1) Only expose au
Add a pointer to the struct vm_operations_struct in the bo_device, and
assign that pointer to the default value currently used.
The driver can then optionally modify that pointer and the new value
can be used for each new vma created.
Cc: "Christian König"
Signed-off-by: Thomas Hellstrom
---
d
Add two utilities to a) write-protect and b) clean all ptes pointing into
a range of an address space
The utilities are intended to aid in tracking dirty pages (either
driver-allocated system memory or pci device memory).
The write-protect utility should be used in conjunction with
page_mkwrite() a
Similar to write-coherent resources, make sure that from the user-space
point of view, GPU rendered contents is automatically available for
reading by the CPU.
Signed-off-by: Thomas Hellstrom
---
drivers/gpu/drm/ttm/ttm_bo_vm.c | 1 +
drivers/gpu/drm/vmwgfx/vmwgfx_drv.h
Add the callbacks necessary to implement emulated coherent memory for
surfaces. Add a flag to the gb_surface_create ioctl to indicate that
surface memory should be coherent.
Also bump the drm minor version to signal the availability of coherent
surfaces.
Signed-off-by: Thomas Hellstrom
---
.../d
This infrastructure will, for coherent resources, make sure that
from the user-space point of view, data written by the CPU is immediately
automatically available to the GPU at resource validation time.
Signed-off-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/Kconfig| 1 +
dr
With the vmwgfx dirty tracking, the default TTM fault handler is not
completely sufficient (vmwgfx need to modify the vma->vm_flags member,
and also needs to restrict the number of prefaults).
We also want to replicate the new ttm_bo_vm_reserve() functionality
So start turning the TTM vm code int
With emulated coherent memory we need to be able to quickly look up
a resource from the MOB offset. Instead of traversing a linked list with
O(n) worst case, use an RBtree with O(log n) worst case complexity.
Signed-off-by: Thomas Hellstrom
---
drivers/gpu/drm/vmwgfx/vmwgfx_bo.c | 5 ++--
This is basically apply_to_page_range with added functionality:
Allocating missing parts of the page table becomes optional, which
means that the function can be guaranteed not to error if allocation
is disabled. Also passing of the closure struct and callback function
becomes different and more in
Graphics APIs like OpenGL 4.4 and Vulkan require the graphics driver
to provide coherent graphics memory, meaning that the GPU sees any
content written to the coherent memory on the next GPU operation that
touches that memory, and the CPU sees any content written by the GPU
to that memory immediate
Driver fault callbacks are allowed to drop the mmap_sem when expecting
long hardware waits to avoid blocking other mm users. Allow the mkwrite
callbacks to do the same by returning early on VM_FAULT_RETRY.
In particular we want to be able to drop the mmap_sem when waiting for
a reservation object
Hi Maxime,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.1-rc4 next-20190412]
[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/commits
The DMFC is configured to supply a watermark signal that can be used to
temporarily increase channel priority if the FIFO runs low. Use it.
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/imx/ipuv3-plane.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/imx/ipuv3-plane.c
b/
From: Lucas Stach
Initialize the flow input colorspaces to unknown and reset to that value
when the channel gets disabled. This avoids the state getting mixed up
with a previous mode.
Also keep the CSC settings for the background flow intact when disabling
the foreground flow.
Root-caused-by: J
From: Lucas Stach
In order to make sure that the plane color space gets reset correctly.
Signed-off-by: Lucas Stach
Signed-off-by: Philipp Zabel
---
drivers/gpu/drm/imx/ipuv3-crtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/imx/ipuv3-crtc.c b/drivers/
Hi Ben,
On Fri, Apr 12, 2019 at 03:08:32PM +0100, Ben Davis wrote:
> The phase setting part of malidp_crtc_atomic_check_scaling is refactored
> to allow use in writeback scaling.
>
> Also the enable_memwrite function prototype is simplified by directly
> passing mw_state.
>
> Signed-off-by: Ben
On 4/12/19 3:39 AM, Christian König wrote:
> Am 11.04.19 um 18:03 schrieb Andrey Grodzovsky:
>> Also reject TDRs if another one already running.
>>
>> v2:
>> Stop all schedulers across device and entire XGMI hive before
>> force signaling HW fences.
>>
>> Signed-off-by: Andrey Grodzovsky
>> ---
>
The pull request you sent on Fri, 12 Apr 2019 14:04:12 +1000:
> git://anongit.freedesktop.org/drm/drm tags/drm-fixes-2019-04-12
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/58890f31f98db230e708905a7f0bd700756ebbed
Thank you!
--
Deet-doot-dot, I am a bot.
https://k
Hi Ben,
On Fri, Apr 12, 2019 at 03:08:28PM +0100, Ben Davis wrote:
> Add new properties to specify width and height for writeback.
>
> Signed-off-by: Ben Davis
> ---
> drivers/gpu/drm/drm_atomic_uapi.c | 8
> drivers/gpu/drm/drm_writeback.c | 28
> inclu
Acked-by: Tomeu Vizoso
Thanks!
Tomeu
On Fri, 12 Apr 2019 at 09:27, Alyssa Rosenzweig wrote:
>
> Acked-by: Alyssa Rosenzweig
> ___
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
_
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #4 from Rémi Verschelde ---
Pasting some relevant output from attachment 143951 so that relevant keywords
can be found by Bugzilla searches.
```
[ 325.087186] mce: CPU7: Core temperature above threshold, cpu clock throttled
(total
Acked-by: Tomeu Vizoso
On Tue, 9 Apr 2019 at 22:54, Rob Herring wrote:
>
> Similar to the single handle drm_gem_object_lookup(),
> drm_gem_objects_lookup() takes an array of handles and returns an array
> of GEM objects.
>
> v2:
> - Take the userspace pointer directly and allocate the array.
> -
Hi Biju,
On 12/04/2019 13:38, Biju Das wrote:
> Add support for the R8A774A1 DU (which is very similar to the R8A7796 DU
> except that it lacks TCON and CMM); it has one RGB output, one LVDS output
> and one HDMI output.
> > Signed-off-by: Biju Das
Thank you for the updated patch,
Reviewed-by:
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #3 from Rémi Verschelde ---
Created attachment 143953
--> https://bugs.freedesktop.org/attachment.cgi?id=143953&action=edit
/proc/config.gz from Mageia's kernel 5.0.7-desktop, used for custom
amd-staging-drm-next build
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #2 from Rémi Verschelde ---
Created attachment 143952
--> https://bugs.freedesktop.org/attachment.cgi?id=143952&action=edit
dmesg output after GPU crash in game For The King with kernel 5.0-rc1 built
from amd-staging-drm-next
Buil
On 10/04/2019 04:17, Alastair D'Silva wrote:
> From: Alastair D'Silva
>
> In order to support additional features in hex_dump_to_buffer, replace
> the ascii bool parameter with flags.
>
> Signed-off-by: Alastair D'Silva
> ---
> drivers/gpu/drm/i915/intel_engine_cs.c| 2 +-
> dr
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #1 from Rémi Verschelde ---
Created attachment 143951
--> https://bugs.freedesktop.org/attachment.cgi?id=143951&action=edit
dmesg output after GPU crash in game StarCrawlers with kernel 5.0.7-desktop
from Mageia 7
--
You are rece
https://bugs.freedesktop.org/show_bug.cgi?id=110413
Bug ID: 110413
Summary: GPU crash and failed reset leading to deadlock on
Polaris 22 XL [Radeon RX Vega M GL]
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
On Fri, 12 Apr 2019 11:06:13 -0300
Helen Koike wrote:
> Hi Boris,
>
> On 4/12/19 10:49 AM, Boris Brezillon wrote:
> > Hi Helen,
> >
> > On Fri, 12 Apr 2019 09:58:25 -0300
> > Helen Koike wrote:
> >
> >> Asynchronous update is the ability change the hw state at any time, not
> >> only during
On 4/12/19 3:40 AM, Christian König wrote:
> Am 11.04.19 um 18:03 schrieb Andrey Grodzovsky:
>> Patch '5edb0c9b Fix deadlock with display during hanged ring recovery'
>> was accidentaly removed during one of DALs code merges.
>>
>> Signed-off-by: Andrey Grodzovsky
>> ---
>> drivers/gpu/drm/amd/d
Quoting Gwan-gyeong Mun (2019-04-12 15:06:17)
> After suspend/resume process, hotplug detection is handled by
> i915_hpd_poll_init_work() workqueue. While intel_hdmi_detect() or
> intel_dp_detect() are called, intel_hdmi_set_edid() or intel_dp_set_edid()
> only update an internal detect_edid variab
The phase setting part of malidp_crtc_atomic_check_scaling is refactored
to allow use in writeback scaling.
Also the enable_memwrite function prototype is simplified by directly
passing mw_state.
Signed-off-by: Ben Davis
---
drivers/gpu/drm/arm/malidp_crtc.c | 49 --
drivers
Add new properties to specify width and height for writeback.
Signed-off-by: Ben Davis
---
drivers/gpu/drm/drm_atomic_uapi.c | 8
drivers/gpu/drm/drm_writeback.c | 28
include/drm/drm_connector.h | 4
include/drm/drm_mode_config.h | 10 +++
Add support for scaling on writeback. To do this add writeback_w and
writeback_h as writeback connector properties to specify the desired
output dimensions.
Then implement downscaling on writeback for Malidp-550 and Malidp-650
(upscaling on writeback is not supported on these devices).
v2: Use 0 a
This patch series fix missed detection of changing of edid on between
suspend and resume.
First patch fixes drm_helper_hdp_irq_event() in order to fix a below use
case.
Following scenario requires detection of changing of edid.
1) plug display device to a connector
2) system suspend
3)
The hotplug detection routine of drm_helper_hpd_irq_event() can detect
changing of status of connector, but it can not detect changing of edid.
Following scenario requires detection of changing of edid.
1) plug display device to a connector
2) system suspend
3) unplug 1)'s display device and p
Hi Boris,
On 4/12/19 10:49 AM, Boris Brezillon wrote:
> Hi Helen,
>
> On Fri, 12 Apr 2019 09:58:25 -0300
> Helen Koike wrote:
>
>> Asynchronous update is the ability change the hw state at any time, not
>> only during vblank.
>>
>> Amend mode is the ability to perform 1000 commits to be applied
After suspend/resume process, hotplug detection is handled by
i915_hpd_poll_init_work() workqueue. While intel_hdmi_detect() or
intel_dp_detect() are called, intel_hdmi_set_edid() or intel_dp_set_edid()
only update an internal detect_edid variable of intel_connector.
A missed update of edid propert
Hi Helen,
On Fri, 12 Apr 2019 09:58:25 -0300
Helen Koike wrote:
> Asynchronous update is the ability change the hw state at any time, not
> only during vblank.
>
> Amend mode is the ability to perform 1000 commits to be applied as soon
> as possible without waiting for 1000 vblanks.
>
> async
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #80 from Garrett ---
well...even better solution: install Radeon-Profile
sudo su
cd /usr/bin
radeon-profile
boom...manual control with the radeon-profile GUI...something i've not once
seen mentioned in any tutorials. as long as you
On 4/12/19 9:58 AM, Helen Koike wrote:
> Add atomic_async_{check,update} hooks in drm_plane_helper_funcs.
> These hooks are called when userspace requests asyncronous page flip in
> the atomic api through the flag DRM_MODE_PAGE_FLIP_ASYNC.
>
> Update those hooks in the drivers that implement asy
Hello Helen,
On Fri, 12 Apr 2019 09:58:24 -0300
Helen Koike wrote:
> add a brief description of the flags used in an atomic commit
>
> Signed-off-by: Helen Koike
> ---
>
> Changes in v3: None
> Changes in v2: None
> Changes in v1: None
>
> include/uapi/drm/drm_mode.h | 18 +-
https://bugs.freedesktop.org/show_bug.cgi?id=110229
--- Comment #35 from Laurent ---
(In reply to Andre Klapper from comment #34)
> Right. And we cannot waste time going through your custom code if you do not
> provide a minimal self-contained test case.
Ok next time I'll provide a test case, an
add a brief description of the flags used in an atomic commit
Signed-off-by: Helen Koike
---
Changes in v3: None
Changes in v2: None
Changes in v1: None
include/uapi/drm/drm_mode.h | 18 +-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/include/uapi/drm/drm_mode.
Hi,
This patch series is an attempt to clarify some concepts and how things
are hooked inside drm.
There are two main concepts that are similar but different and are
causing some confusion:
- Asynchronous update: is the ability change the hw state at any time, not
only during vblank.
This flag tells core to jump ahead the queued update if the conditions
in drm_atomic_amend_check() are met. That means we are only able to do an
amend update if no modeset is pending and update for the same plane is
not queued.
It uses the already in place infrastructure for amend updates.
It is
Add atomic_async_{check,update} hooks in drm_plane_helper_funcs.
These hooks are called when userspace requests asyncronous page flip in
the atomic api through the flag DRM_MODE_PAGE_FLIP_ASYNC.
Update those hooks in the drivers that implement async functions, except
for amdgpu who handles the fla
Asynchronous update is the ability change the hw state at any time, not
only during vblank.
Amend mode is the ability to perform 1000 commits to be applied as soon
as possible without waiting for 1000 vblanks.
async updates can be seen as amend, but the opposite is not true.
&drm_plane_helper_fu
Hello,
On Fri, Apr 12, 2019 at 12:59:53PM +0200, Bartlomiej Zolnierkiewicz wrote:
> Add COMPILE_TEST support to imxfb driver for better compile
> testing coverage.
>
> Signed-off-by: Bartlomiej Zolnierkiewicz
> ---
> drivers/video/fbdev/Kconfig |2 +-
> 1 file changed, 1 insertion(+), 1 del
On 12.04.2019 13:53, Jyri Sarha wrote:
> On 12/04/2019 11:52, Andrzej Hajda wrote:
>> On 22.03.2019 09:06, Jyri Sarha wrote:
>>> Implement HDMI audio support by using ASoC HDMI codec. The commit
>>> implements the necessary callbacks and configuration for the HDMI
>>> codec and registers a virtual
Hi Biju,
On 11/04/2019 15:34, Biju Das wrote:
> The LVDS encoders on RZ/G2M SoC is similar to R-Car M3-W. Add support for
> RZ/G2M (R8A774A1) SoC to the LVDS encoder driver.
>
> Signed-off-by: Biju Das
This one seems to be ok using the gen3 as far as I can tell, the PLL
configuration and layout
Add COMPILE_TEST support to da8xx-fb driver for better compile
testing coverage.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/video/fbdev/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/drivers/video/fbdev/Kconfig
===
Add COMPILE_TEST support to gbefb driver for better compile
testing coverage.
While at it remove dead x86 specific code.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/video/fbdev/Kconfig |2 +-
drivers/video/fbdev/gbefb.c |9 ++---
2 files changed, 3 insertions(+), 8 deletion
On 12/04/2019 11:52, Andrzej Hajda wrote:
> On 22.03.2019 09:06, Jyri Sarha wrote:
>> Implement HDMI audio support by using ASoC HDMI codec. The commit
>> implements the necessary callbacks and configuration for the HDMI
>> codec and registers a virtual platform device for the codec to attach.
>>
>
Hi Biju,
On 11/04/2019 15:34, Biju Das wrote:
> Add support for the R8A774A1 DU (which is very similar to the R8A7796 DU);
> it has one RGB output, one LVDS output and one HDMI output.
>
> Signed-off-by: Biju Das
I see Figure 35.1b across the two datasheets does show some differences
between th
On Fri, Apr 12, 2019 at 12:46:44PM +0200, Lukas Wunner wrote:
> On Thu, Apr 11, 2019 at 11:02:26PM +0200, Noralf Trønnes wrote:
> > Den 11.04.2019 20.18, skrev Lukas Wunner:
> > > Note that spi_map_buf() already splits every transfer's sglist into
> > > segments that are smaller than ctlr->max_dma
Add COMPILE_TEST support to atmel_lcdfb driver for better compile
testing coverage.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/video/fbdev/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/drivers/video/fbdev/Kconfig
On Fri, Apr 12, 2019 at 01:16:15PM +0200, Lukas Wunner wrote:
> On Fri, Apr 12, 2019 at 12:09:34PM +0100, Mark Brown wrote:
> > On Fri, Apr 12, 2019 at 12:54:48PM +0200, Lukas Wunner wrote:
> > > My point was that the call to spi_split_transfers_maxsize() shouldn't
> > > be called on non-DMA-capab
On Fri, Apr 12, 2019 at 12:09:34PM +0100, Mark Brown wrote:
> On Fri, Apr 12, 2019 at 12:54:48PM +0200, Lukas Wunner wrote:
> > On Fri, Apr 12, 2019 at 10:47:21AM +0100, Mark Brown wrote:
> > > I *think* we managed to fix all the architectures to at least stub out
> > > the DMA interfaces, it's suc
On Fri, Apr 12, 2019 at 12:54:48PM +0200, Lukas Wunner wrote:
> On Fri, Apr 12, 2019 at 10:47:21AM +0100, Mark Brown wrote:
> > I *think* we managed to fix all the architectures to at least stub out
> > the DMA interfaces, it's such a pointless thing to have conditional -
> > it really only makes
On Thu, Apr 11, 2019 at 6:19 PM megous via linux-sunxi
wrote:
>
> From: Ondrej Jirman
>
> This series implements support for Xunlong Orange Pi 3 board.
>
> Unfortunately, this board needs some small driver patches, so I have
> split the boards DT patch into chunks that require patches for drivers
On Fri, Apr 12, 2019 at 10:47:21AM +0100, Mark Brown wrote:
> On Thu, Apr 11, 2019 at 11:02:26PM +0200, Noralf Trønnes wrote:
> > Den 11.04.2019 20.18, skrev Lukas Wunner:
> > > On Thu, Apr 11, 2019 at 06:42:33PM +0200, Noralf Trønnes wrote:
> > > > @@ -1299,6 +1299,11 @@ static void __spi_pump_mes
Add COMPILE_TEST support to pxa168fb driver for better compile
testing coverage.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/video/fbdev/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/drivers/video/fbdev/Kconfig
===
Add COMPILE_TEST support to imxfb driver for better compile
testing coverage.
Signed-off-by: Bartlomiej Zolnierkiewicz
---
drivers/video/fbdev/Kconfig |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/drivers/video/fbdev/Kconfig
==
On Thu, Apr 11, 2019 at 11:02:26PM +0200, Noralf Trønnes wrote:
> Den 11.04.2019 20.18, skrev Lukas Wunner:
> > On Thu, Apr 11, 2019 at 06:42:33PM +0200, Noralf Trønnes wrote:
> >> @@ -1299,6 +1299,11 @@ static void __spi_pump_messages(struct
> >> spi_controller *ctlr, bool in_kthread)
> >>
> >>
https://bugs.freedesktop.org/show_bug.cgi?id=109461
--- Comment #3 from Hubert Kario ---
did you try to monitor temperature while running the game?
Did you try to reproduce it with something like glmark2 or FurMark?
see also bug 109466 comment 9
--
You are receiving this mail because:
You are
Hi Biju,
Thank you for the patch,
On 11/04/2019 15:34, Biju Das wrote:
> Document the RZ/G2M (R8A774A1) LVDS bindings.
>
> Signed-off-by: Biju Das
This looks good.
Reviewed-by: Kieran Bingham
> ---
> Documentation/devicetree/bindings/display/bridge/renesas,lvds.txt | 1 +
> 1 file changed
https://bugs.freedesktop.org/show_bug.cgi?id=109466
--- Comment #9 from Hubert Kario ---
I'm experiencing similar issues with R9 290X.
But after trying to reproduce it few times (crash in Witcher III, crash while
running glmark2) I'm getting convinced that it's actually a temperature problem
- th
On 4/1/19 9:15 PM, Jernej Skrabec wrote:
> All DW HDMI controllers used by Allwinner SoCs include CEC controller.
> However, due to additional logic put between CEC controller and pins,
> CEC communication doesn't work well on some of them.
>
> Based on observations, it seems that only outgoing me
On Fri, Apr 12, 2019 at 12:03:35PM +0200, ker...@martin.sperl.org wrote:
> > On 12.04.2019, at 11:47, Mark Brown wrote:
> >> In a previous version of this I suggested to Meghana to put this in the
> >> driver, but Mark wanted it in the core.
> > If we want to do this at a lower level the DMA cod
On Fri, Apr 12, 2019 at 11:41:30AM +0200, Noralf Trønnes wrote:
> This let SPI clients check if the controller supports a particular word
> width. drivers/gpu/drm/tinydrm/mipi-dbi.c will use this to determine if
> the controller supports 16-bit for RGB565 pixels. If it doesn't it will
> swap the by
Hi Jernej,
On 4/1/19 9:15 PM, Jernej Skrabec wrote:
> It turns out that additional logic between HDMI CEC controller and
> pins on PHY on some Allwinner SoCs prevents proper communication.
> It might be possible to fix it, but it's much easier and less error
> prone to just directly drive pins usi
On Fri, 12 Apr 2019, Bartlomiej Zolnierkiewicz wrote:
> 'default n' is the default value for any bool or tristate Kconfig
> setting so there is no need to write it explicitly.
>
> Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
> is not set' for visible symbols") the Kconfig beh
/Maxime-Ripard/drm-modes-Rewrite-the-command-line-parser/20190412-122837
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
d
'default n' is the default value for any bool or tristate Kconfig
setting so there is no need to write it explicitly.
Also since commit f467c5640c29 ("kconfig: only write '# CONFIG_FOO
is not set' for visible symbols") the Kconfig behavior is the same
regardless of 'default n' being present or not
Enable advance gamma modes based on client
caps.
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_color.c | 16 +---
1 file changed, 9 insertions(+), 7 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_color.c
b/drivers/gpu/drm/i915/intel_color.c
index edf5ff8..36604c16
Introduced a client cap for advance cap mode
capability. Userspace should set this to get
to be able to use the new gamma_mode property.
If this is not set, driver will work in legacy
mode.
Suggested-by: Ville Syrjälä
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/drm_atomic_uapi.c | 3 +++
dr
From: Ville Syrjälä
Add a gamma mode property to enable various kind of
gamma modes supported by platforms like: Interpolated, Split,
Multi Segmented etc. Userspace can get this property and
should be able to get the platform capabilties wrt various
gamma modes possible and the possible ranges.
Gen11 introduced a new gamma mode i.e, multi segmented
gamma mode. Added support for the same.
v2: Aligned to just 1 property interface as suggested by
Ville. Fixed Ville's review comments.
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_color.c | 166 +
Attach the gamma mode property to allow userspace
set the gamma mode and provide the luts for the
same.
v2: Enabled just 1 property interface for gamma_mode,
as suggested by Ville.
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_color.c | 3 +++
drivers/gpu/drm/i915/intel_display.c
From: Ville Syrjälä
This defines the color lut ranges for 10bit and multi
segmented gamma range for ICL.
v2: Defined and advertise the gamma modes supported on
various platforms as suggested by Ville.
Signed-off-by: Ville Syrjälä
Signed-off-by: Uma Shankar
---
drivers/gpu/drm/i915/intel_colo
1 - 100 of 151 matches
Mail list logo
