This adds support for the VK_GOOGLE_display timing extension, which
provides two things:
1) Detailed information about when frames are displayed, including
slack time between GPU execution and display frame.
2) Absolute time control over swapchain queue processing. This allows
the
This extension is required to support EXT_display_control as it offers
a way to query whether the vblank counter is supported.
v2: Thanks to kisak
Fix spelling of VkSurfaceCapabilities2EXT in wsi_common_wayland.c,
it was using ext instead of EXT.
Fix spelling of
Add support for the EXT_direct_mode_display extension. This just
provides the vkReleaseDisplayEXT function.
Signed-off-by: Keith Packard
---
src/amd/vulkan/radv_extensions.py | 1 +
src/amd/vulkan/radv_wsi_display.c | 11 +++
src/intel/vulkan/anv_extensions.py |
This extension adds a single function to query the current GPU
timestamp, just like glGetInteger64v(GL_TIMESTAMP, ). This
function is needed to complete the implementation of
GOOGLE_display_timing, which needs to be able to coorelate GPU and CPU
timestamps.
Signed-off-by: Keith Packard
This adds support for the KHR_display extension to the anv and radv
Vulkan drivers. The drivers now attempt to open the master DRM node
when the KHR_display extension is requested so that the common winsys
code can perform the necessary operations.
Signed-off-by: Keith Packard
This extension adds the ability to borrow an X RandR output for
temporary use directly by a Vulkan application. For DRM, we use the
Linux resource leasing mechanism.
Signed-off-by: Keith Packard
---
configure.ac | 25 ++
meson.build
Here's a series of extensions necessary to perform reasonable direct
display operations, either directly through DRM with no window system,
or using RandR and Linux leases.
There's one new extension, MESA_query_timestamp which performs the
same operation as glGetInteger64v(GL_TIMESTAMP, ) -- it
This extension provides fences and frame count information to direct
display contexts. It uses new kernel ioctls to provide 64-bits of
vblank sequence and nanosecond resolution.
v2: Remove DRM_CRTC_SEQUENCE_FIRST_PIXEL_OUT flag. This has
been removed from the proposed kernel API.
Add
https://bugs.freedesktop.org/show_bug.cgi?id=104963
--- Comment #8 from Will ---
After triple checking, nomodeset or radeon.dpm=0 prevents boot loops on my
hardware.
--
You are receiving this mail because:
You are the assignee for the
This patch adds new formats needed by Xilinx IP. Pixels are not
byte-aligned in these formats, and the drm_format_info for these
formats has macro-pixel information.
Signed-off-by: Jeffrey Mouroux
Signed-off-by: Hyun Kwon
---
v3
- Update entries for
Hi,
Following up on v1 [1] and v2 [2], this series is to address non-byte aligned
formats in drm. Based on the comments, the set is getting simplified, and
any further comment would be appreciated. Brief description:
Patch 1 just changes comment style for change in patch 2
Patch 2 adds
drm_format_plane_width_bytes() calculates and returns the number of bytes
for given width of specified format. The calculation uses @cpp
in drm format info for byte-aligned formats. If the format isn't
byte-aligned, @cpp should 0, and the macro pixel information is used.
This avoids bit level
Multiple pixels can be grouped as a single unit and form a 'macro-pixel'.
This is to model formats where multiple non-byte aligned pixels are stored
together in a byte-aligned way. For example, if 3 - 10 bit
pixels are stored in 32 bit, the 32 bit stroage can be treated as
a single macro-pixel
This adds packed YUV and grey scale format fourccs.
Signed-off-by: Hyun Kwon
---
v3
- Update entries for changes
- Squash fourcc patch into this
- Note these don't have any reference in mainline
v2
- Split from the previous patch
---
---
drivers/gpu/drm/drm_fourcc.c | 5
Use the inline kern-doc style for struct drm_format_info for better
readability. This is just a preliminary change for further table update.
Signed-off-by: Hyun Kwon
---
v3
- This is added
---
---
include/drm/drm_fourcc.h | 45 +
Use drm_format_width_bytes() to support non-byte aligned formats.
Signed-off-by: Hyun Kwon
---
v3
- 2 patches are squashed
---
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git
On Thu, 2018-02-08 at 23:39 -0800, Rodrigo Vivi wrote:
> Rodrigo Vivi writes:
>
> > "Pandiyan, Dhinakaran" writes:
> >
> >> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
> >>> Hi Andy,
> >>>
> >>> thanks for getting involved with
The initialization of 'result' is unnecessary, the variable is assigned
unconditionally a few lines below. Removing the initialization also fixes
the following warning when building with clang:
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link_dp.c:1931:26:
error: implicit conversion from
https://bugs.freedesktop.org/show_bug.cgi?id=96868
--- Comment #33 from Mike Bendel ---
I'm also experiencing the same issues, but on much lower refresh rates. I have
a 3840x1600 monitor (LG 38UC99) and when running at 75Hz, display corruption is
observed on both AMD GPUs I
El Fri, Feb 09, 2018 at 04:55:57PM -0500 Harry Wentland ha dit:
> On 2018-02-09 04:28 PM, Matthias Kaehlcke wrote:
> > dce_clock_set_min_clocks_state() assigns (intentionally) a value of type
> > 'enum dm_pp_clocks_state' to a variable of type 'enum dm_pp_power_level'
> > without an explicit
https://bugs.freedesktop.org/show_bug.cgi?id=104963
--- Comment #7 from NickForum ---
Hi
Some problem after 4.15 update.
Radeon HD 5770 Evergreen
kernel 4.15.2-2-ARCH
disable dpm is a workaround
--
You are receiving this mail because:
You are the assignee for the
On 2018-02-09 04:28 PM, Matthias Kaehlcke wrote:
> dce_clock_set_min_clocks_state() assigns (intentionally) a value of type
> 'enum dm_pp_clocks_state' to a variable of type 'enum dm_pp_power_level'
> without an explicit cast. This causes clang to raise the following
> warning:
>
>
dce_clock_set_min_clocks_state() assigns (intentionally) a value of type
'enum dm_pp_clocks_state' to a variable of type 'enum dm_pp_power_level'
without an explicit cast. This causes clang to raise the following
warning:
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dce_clocks.c:308:4: error:
Sorry, I unintentionally 'recycled' git send-email parameters, please
ignore this patch :(
El Fri, Feb 09, 2018 at 01:22:13PM -0800 Matthias Kaehlcke ha dit:
> From: KaiChieh Chuang
>
> This fix a bug in dapm_widget_power_read_file(),
> where it may sent opposite
From: KaiChieh Chuang
This fix a bug in dapm_widget_power_read_file(),
where it may sent opposite order of source/sink widget
into the p->connected().
for example,
static int connected_check(source, sink);
{"w_sink", NULL, "w_source", connected_check}
the
https://bugs.freedesktop.org/show_bug.cgi?id=105026
Bug ID: 105026
Summary: glxgears asserts with pp_jimenezmlaa=1
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=105005
--- Comment #9 from Dmitry ---
I will not be able to do, not enough skill.
Tried to drag through TV files, TV breaks after the loss of the signal on the
main machine. Also tried to register in the console dmesg creation
Am 09.02.2018 um 19:19 schrieb Tom St Denis:
On 09/02/18 01:17 PM, Christian König wrote:
Am 09.02.2018 um 18:28 schrieb Tom St Denis:
On 09/02/18 12:27 PM, Tom St Denis wrote:
From: Christian König
Oops, I'll remove this from the commit message before
https://bugs.freedesktop.org/show_bug.cgi?id=104963
--- Comment #6 from Will ---
That's my bad, my hardware is more different than I thought AND I spelled it
wrong, it's an A88XM-E45. I'll have to check again later tonight if
radeon.dpm=0 worked on its own, I'm having a hard
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.17-wip
head: 9778e0d1a858869180a199844c578b199040271b
commit: b5d7df79439443dc493cbad1ccf800b0801fcbb6 [284/304] drm/amd/powerplay:
implement set_mmhub_powergating_by_smu for Raven
config: x86_64-randconfig-s5-02092347 (attached
On 09/02/18 01:17 PM, Christian König wrote:
Am 09.02.2018 um 18:28 schrieb Tom St Denis:
On 09/02/18 12:27 PM, Tom St Denis wrote:
From: Christian König
Oops, I'll remove this from the commit message before pushing :-)
I did give you credit below though.
Am 09.02.2018 um 18:28 schrieb Tom St Denis:
On 09/02/18 12:27 PM, Tom St Denis wrote:
From: Christian König
Oops, I'll remove this from the commit message before pushing :-)
I did give you credit below though.
The patch before this one isn't merged yet
On Fri, Feb 9, 2018 at 7:39 AM, Rodrigo Vivi wrote:
> Rodrigo Vivi writes:
>
>> "Pandiyan, Dhinakaran" writes:
>>
>>> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
Hi Andy,
thanks for getting
On 09/02/18 12:27 PM, Tom St Denis wrote:
From: Christian König
Oops, I'll remove this from the commit message before pushing :-)
I did give you credit below though.
Tom
This allows access to pages allocated through the driver with optional
IOMMU
From: Christian König
This allows access to pages allocated through the driver with optional
IOMMU mapping.
v2: Fix number of bytes copied and add write method
Original-by: Christian König
Signed-off-by: Tom St Denis
On Fri, Feb 09, 2018 at 06:30:08PM +0200, Oleksandr Andrushchenko wrote:
> -- OFFTOP --
> BTW, what is the right branch should I use
> for a new DRM driver and the patch like the above?
> I am lost a bit :)
Usual recommendation is to use:
git://anongit.freedesktop.org/drm-tip drm-tip
But note
On 02/09/2018 06:24 PM, Ville Syrjälä wrote:
On Fri, Feb 09, 2018 at 06:09:09PM +0200, Oleksandr Andrushchenko wrote:
On 02/09/2018 05:53 PM, Ville Syrjälä wrote:
On Thu, Feb 08, 2018 at 11:53:30AM +0200, Oleksandr Andrushchenko wrote:
Hello, Ville!
On 02/06/2018 06:04 PM, Ville Syrjälä
On Fri, Feb 09, 2018 at 06:09:09PM +0200, Oleksandr Andrushchenko wrote:
> On 02/09/2018 05:53 PM, Ville Syrjälä wrote:
> > On Thu, Feb 08, 2018 at 11:53:30AM +0200, Oleksandr Andrushchenko wrote:
> >> Hello, Ville!
> >>
> >> On 02/06/2018 06:04 PM, Ville Syrjälä wrote:
> >>> On Tue, Feb 06, 2018
On 09/02/18 09:56 AM, Christian König wrote:
Am 09.02.2018 um 15:51 schrieb Tom St Denis:
On 09/02/18 09:12 AM, Christian König wrote:
No, there is simply no need to initialize the system domain. What are
the values of p->mapping and adev->mman.bdev.dev_mapping when they
don't match? Maybe we
On 02/09/2018 05:53 PM, Ville Syrjälä wrote:
On Thu, Feb 08, 2018 at 11:53:30AM +0200, Oleksandr Andrushchenko wrote:
Hello, Ville!
On 02/06/2018 06:04 PM, Ville Syrjälä wrote:
On Tue, Feb 06, 2018 at 11:59:37AM +0200, Oleksandr Andrushchenko wrote:
Hello, Ville!
Thank you very much for
On Thu, Feb 1, 2018 at 9:13 PM, Chris Chiu wrote:
> On Thu, Feb 1, 2018 at 12:08 AM, Harry Wentland
> wrote:
>> On 2018-01-31 09:31 AM, Chris Chiu wrote:
>>> Hi,
>>> We are working with new laptops that have the AMD Ravenl Ridge
>>> chipset with
dev->struct_mutex is the Big DRM Lock and the only bit where
it’s mandatory is serializing GEM buffer object destruction.
Which unfortunately means drivers have to keep track of that
lock and either call unreference or unreference_locked
depending upon context. Core GEM doesn’t have a need for
qcom,smmu-v2 is an arm,smmu-v2 implementation with specific
clock and power requirements. This smmu core is used with
multiple masters on msm8996, viz. mdss, video, etc.
Add bindings for the same.
Signed-off-by: Vivek Gautam
Reviewed-by: Rob Herring
On Thu, Feb 08, 2018 at 11:53:30AM +0200, Oleksandr Andrushchenko wrote:
> Hello, Ville!
>
> On 02/06/2018 06:04 PM, Ville Syrjälä wrote:
> > On Tue, Feb 06, 2018 at 11:59:37AM +0200, Oleksandr Andrushchenko wrote:
> >> Hello, Ville!
> >>
> >> Thank you very much for such a comprehensive answer.
https://bugs.freedesktop.org/show_bug.cgi?id=105021
--- Comment #4 from arne_woer...@yahoo.com ---
Created attachment 137247
--> https://bugs.freedesktop.org/attachment.cgi?id=137247=edit
amdgpu related interrupt count
Michel Dänzer asked:
> When it's slow, do the numbers on the amdgpu line in
Am 09.02.2018 um 15:51 schrieb Tom St Denis:
On 09/02/18 09:12 AM, Christian König wrote:
No, there is simply no need to initialize the system domain. What are
the values of p->mapping and adev->mman.bdev.dev_mapping when they
don't match? Maybe we are allocating memory before initializing
On 09/02/18 09:12 AM, Christian König wrote:
No, there is simply no need to initialize the system domain. What are
the values of p->mapping and adev->mman.bdev.dev_mapping when they don't
match? Maybe we are allocating memory before initializing
adev->mman.bdev.dev_mapping.
In my test setup
On 2/9/2018 7:17 AM, Jani Nikula wrote:
On Thu, 08 Feb 2018, Joe Moriarty wrote:
The Parfait (version 2.1.0) static code analysis tool found multiple NULL
pointer derefernce problems.
Thanks for the patch. Multiple problems requires multiple patches to fix
them, one
On Thu, Feb 08, 2018 at 07:34:11PM -0500, Ilia Mirkin wrote:
> On Wed, Feb 7, 2018 at 12:01 PM, Ville Syrjälä
> wrote:
> > On Wed, Feb 07, 2018 at 06:28:42PM +0200, Ville Syrjälä wrote:
> >> On Sun, Feb 04, 2018 at 06:50:45PM -0500, Ilia Mirkin wrote:
> >> > In case
Am 09.02.2018 um 15:02 schrieb Tom St Denis:
On 09/02/18 08:56 AM, Christian König wrote:
Am 09.02.2018 um 14:32 schrieb Tom St Denis:
On 02/02/18 02:09 PM, Christian König wrote:
[SNIP]
+ if (p->mapping != adev->mman.bdev.dev_mapping)
+ return -EPERM;
This comparison
Hi Linus,
Please pull fbdev fix for v4.16 (just a single fix to make
omapfb driver build again).
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R Institute Poland
Samsung Electronics
The following changes since commit f1517df8701c9f12dae9ce7f43a5d300a6917619:
Merge tag 'nfsd-4.16' of
On 09/02/18 08:56 AM, Christian König wrote:
Am 09.02.2018 um 14:32 schrieb Tom St Denis:
On 02/02/18 02:09 PM, Christian König wrote:
[SNIP]
+ if (p->mapping != adev->mman.bdev.dev_mapping)
+ return -EPERM;
This comparison fails for both IOMMU and non-IOMMU devices in my
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #25 from Christian König ---
(In reply to Andreas Kilgus from comment #24)
> (In reply to Christian König from comment #23)
> > Take a look at /proc/pagetypeinfo. There must at least be pages at
Am 09.02.2018 um 14:32 schrieb Tom St Denis:
On 02/02/18 02:09 PM, Christian König wrote:
[SNIP]
+ if (p->mapping != adev->mman.bdev.dev_mapping)
+ return -EPERM;
This comparison fails for both IOMMU and non-IOMMU devices in my
carrizo+polaris10 box.
The address being
On 02/02/18 02:09 PM, Christian König wrote:
This allows access to pages allocated through the driver with optional
IOMMU mapping.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 57 -
1 file changed, 35
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #24 from Andreas Kilgus ---
(In reply to Christian König from comment #23)
> Take a look at /proc/pagetypeinfo. There must at least be pages at order 9
> or higher for an 2MB swiotlb allocation to succeed.
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #23 from Christian König ---
(In reply to Andreas Kilgus from comment #22)
> I am getting these messsages on my machine right now, too.
>
> total used free shared
Am 09.02.2018 um 11:00 schrieb Roger He:
the free mem space and the lower limit both include two parts:
system memory and swap space.
For the OOM triggered by TTM, that is the case as below:
first swap space is full of swapped out pages and soon
system memory also is filled up with ttm pages.
Quoting Shreeya Patel (2018-02-09 12:10:56)
> dev->struct_mutex is the Big DRM Lock and the only bit where
> it’s mandatory is serializing GEM buffer object destruction.
> Which unfortunately means drivers have to keep track of that
> lock and either call unreference or unreference_locked
>
On Thu, 08 Feb 2018, Joe Moriarty wrote:
> The Parfait (version 2.1.0) static code analysis tool found multiple NULL
> pointer derefernce problems.
Thanks for the patch. Multiple problems requires multiple patches to fix
them, one patch per problem. Please split up the
Am 09.02.2018 um 11:00 schrieb Roger He:
set TTM_OPT_FLAG_FORCE_ALLOC when we are servicing for page
fault routine.
for ttm_mem_global_reserve if in page fault routine, allow the gtt
pages reservation always. because page fault routing already grabbed
system memory and the allowance of this
Dylan Baker writes:
> Which is used in wraps.
Reviewed-by: Eric Anholt
signature.asc
Description: PGP signature
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
Hi Gerd and Stefan,
can we reach agreement on whether vsock should be involved in this?
Thanks,
Tomeu
On 02/07/2018 10:49 AM, Tomeu Vizoso wrote:
On 02/06/2018 03:23 PM, Gerd Hoffmann wrote:
Hi,
Hmm? I'm assuming the wayland client (in the guest) talks to the
wayland proxy, using the
https://bugs.freedesktop.org/show_bug.cgi?id=104963
--- Comment #5 from VF ---
And my MoBo is not the same : A88XM-E35
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=104963
--- Comment #4 from VF ---
radeon.dpm=0 was the only workaround for me (or nomodeset)
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
On Fri, Feb 9, 2018 at 4:40 AM, Maxime Ripard wrote:
> On Wed, Feb 07, 2018 at 01:49:59PM +0100, Giulio Benetti wrote:
>> Hi,
>>
>> Il 07/02/2018 11:39, Maxime Ripard ha scritto:
>> > On Wed, Jan 24, 2018 at 08:37:28PM +0100, Giulio Benetti wrote:
>> > Also, how was
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #22 from Andreas Kilgus ---
(In reply to Christian König from comment #21)
> (In reply to Stratos Zolotas from comment #20)
> > Maybe it is a coincidence, for sure I'm not running out of memory when it is
> >
Am Freitag, 9. Februar 2018, 11:06:49 CET schrieb Andrzej Hajda:
> On 09.02.2018 10:24, Heiko Stuebner wrote:
> > Hi Martin,
> >
> > Am Montag, 5. Februar 2018, 22:32:08 CET schrieb Martin Cerveny:
> >> On Mon, 5 Feb 2018, Heiko Stuebner wrote:
> >>> From: Zheng Yang
>
On 09.02.2018 10:24, Heiko Stuebner wrote:
> Hi Martin,
>
> Am Montag, 5. Februar 2018, 22:32:08 CET schrieb Martin Cerveny:
>> On Mon, 5 Feb 2018, Heiko Stuebner wrote:
>>> From: Zheng Yang
>>>
>>> Add a driver for the Innosilicon hdmi phy used on rk3228/rk3229
>>> and
the free mem space and the lower limit both include two parts:
system memory and swap space.
For the OOM triggered by TTM, that is the case as below:
first swap space is full of swapped out pages and soon
system memory also is filled up with ttm pages. and then
any memory allocation request will
Because ttm_bo_force_list_clean() is only called on two occasions:
1. By ttm_bo_evict_mm() during suspend.
2. By ttm_bo_clean_mm() when the driver unloads.
On both cases we absolutely don't want any memory allocation failure.
Signed-off-by: Roger He
---
set TTM_OPT_FLAG_FORCE_ALLOC when we are servicing for page
fault routine.
for ttm_mem_global_reserve if in page fault routine, allow the gtt
pages reservation always. because page fault routing already grabbed
system memory and the allowance of this exception is harmless.
Otherwise, it will
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #21 from Christian König ---
(In reply to Stratos Zolotas from comment #20)
> Maybe it is a coincidence, for sure I'm not running out of memory when it is
> happening and started with kernel 4.15
Ok. please ignore patch3 since I have some minor changes.
Will send out later.
Thanks
Roger(Hongbo.He)
-Original Message-
From: Koenig, Christian
Sent: Friday, February 09, 2018 5:38 PM
To: He, Roger ; dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/ttm:
Am 09.02.2018 um 08:30 schrieb Roger He:
if it is true, allocate TTM pages regardless of zone global memory
account limit. For example suspend, We should avoid TTM memory
allocate failure to lead to whole process fail.
Signed-off-by: Roger He
---
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #20 from Stratos Zolotas ---
(In reply to Michel Dänzer from comment #19)
>
> That's either simply coincidence, or means the kernel ran out of memory. The
> messages this report is about are triggered by transient
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #19 from Michel Dänzer ---
(In reply to Stratos Zolotas from comment #18)
> I can say that it is not completely harmless. I'm using virtualbox on my KDE
> plasma desktop and I have several crashes on windows VMs
Hi Martin,
Am Montag, 5. Februar 2018, 22:32:08 CET schrieb Martin Cerveny:
> On Mon, 5 Feb 2018, Heiko Stuebner wrote:
> > From: Zheng Yang
> >
> > Add a driver for the Innosilicon hdmi phy used on rk3228/rk3229
> > and rk3328 socs from Rockchip.
> >
> > Signed-off-by:
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Michel Dänzer changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #18 from Stratos Zolotas ---
(In reply to Michel Dänzer from comment #17)
> The swiotlb messages this report is about are harmless (though a fix is on
> the way anyway), the other issues you mention are probably
https://bugs.freedesktop.org/show_bug.cgi?id=105021
Michel Dänzer changed:
What|Removed |Added
Component|Driver/AMDgpu |DRM/AMDgpu
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #17 from Michel Dänzer ---
(In reply to Matthew Scheirer from comment #16)
> I get this as well with a 290 on 4.15 ONLY when DC is enabled. Its a dirty
> enough taint to leave btrfs volumes in inconsistent states
On 2018-02-09 03:44 AM, Chunming Zhou wrote:
> it will be used to check if the driver needs swiotlb
> v2: Don't use inline, instead, move function to drm_memory.c (Mechel Daenzer
> )
Typo in my first name. With that fixed,
Reviewed-by: Michel Dänzer
Am 09.02.2018 um 08:30 schrieb Roger He:
set TTM_OPT_FLAG_FORCE_ALLOC when we are servicing for page
fault routine.
for ttm_mem_global_reserve if in page fault routine, allow the gtt
pages reservation always. because page fault routing already grabbed
system memory and the allowance of this
This adds the required infrastructure for manually
updated displays, such as DSI command mode panels.
While those panels often support partial updates
we currently always do a full refresh. Display
will be refreshed when something calls the dirty
callback, such as libdrm's drmModeDirtyFB().
This
This is a workaround for a hardware bug occuring on OMAP3
with manually updated panels. Details about the HW bug are
unknown to me, but without this fix the panel refresh does
not work at all on Nokia N950. This is not the case for the
OMAP4 based Droid 4, which works perfectly fine with default
Introduce new "orientation" property for describing in which
orientation a panel has been mounted to the device. This can
be used by the operating system to automatically rotate the
display correctly.
Signed-off-by: Sebastian Reichel
---
On 02/08/2018 03:44 AM, Ulf Magnusson wrote:
> The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove
> support for AVR32 architecture").
You forgot the Signed-off-by tag.
> ---
> Changes in v2:
> Remove the AVR32 reference from the help text too.
>
> drivers/spi/Kconfig | 4
Hi,
These are the remaining patches from my previous patchset to get
Droid 4 (omap4) display working. The patches have been rebased to
current master branch from Torvalds (581e400ff935). Since N950
(omap3) is broken even with the workaround I moved it to the end,
so that it can be skipped.
The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove
support for AVR32 architecture").
Signed-off-by: Ulf Magnusson
---
Changes in v3:
Add Signed-off-by tag
Changes in v2:
Remove the AVR32 reference from the help text too.
drivers/spi/Kconfig | 4 ++--
1
* Sebastian Reichel [180208 10:31]:
> Hi,
>
> These are the remaining patches from my previous patchset to get
> Droid 4 (omap4) display working. The patches have been rebased to
> current master branch from Torvalds (581e400ff935). Since N950
> (omap3) is
Hi,
On Thu, Feb 08, 2018 at 12:53:16PM +0200, Tomi Valkeinen wrote:
> On 08/02/18 11:41, Pavel Machek wrote:
> >> I've also picked patches 7-12.
> >
> > It seems that part of the support made it to v4.16. Is it supposed to
> > be complete?
> >
> > I still have these in my tree, and result works
Benjamin,
On Wed, Jan 24, 2018 at 9:57 AM, Benjamin Gaignard
wrote:
> 2018-01-24 0:32 GMT+01:00 Laurent Pinchart
> :
>> Hi Philippe,
>>
>> On Tuesday, 23 January 2018 12:25:51 EET Philippe CORNU wrote:
>>> On 01/23/2018 12:30 AM,
On Thu, Feb 8, 2018 at 3:58 PM, Philippe Cornu wrote:
> Add SPDX identifiers to the Synopsys DesignWare MIPI DSI
> host controller driver.
>
> Signed-off-by: Philippe Cornu
> ---
> Changes in v2: Update to "GPL-2.0+" following comments from Laurent
>
In preparation for manually updated display support, such as DSI
command mode panels, this adds a simple helper to see if a connector
is manually updated.
Signed-off-by: Sebastian Reichel
---
drivers/gpu/drm/omapdrm/omap_connector.c | 8
The affected system (0x0813) is pretty similar to another one (0x0812),
it also needs to use ATPX power control.
Signed-off-by: Kai-Heng Feng
---
drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c | 1 +
1 file changed, 1 insertion(+)
diff --git
This adds a LCD panel orientation hint to the Droid 4. If the
display is rotated this way the keyboard can be used properly.
Signed-off-by: Sebastian Reichel
---
arch/arm/boot/dts/omap4-droid4-xt894.dts | 3 +++
1 file changed, 3 insertions(+)
diff --git
This adds support for setting DRM panel orientation property
based on information from the display driver.
Signed-off-by: Sebastian Reichel
---
drivers/gpu/drm/omapdrm/dss/omapdss.h| 2 ++
drivers/gpu/drm/omapdrm/omap_connector.c | 10 +-
2 files
On 02/08/2018 08:11 AM, Bartlomiej Zolnierkiewicz wrote:
Hi,
[ dri-devel ML & arch/[score,um] Maintainers added to Cc: ]
On Friday, February 02, 2018 08:59:57 AM Christian Borntraeger wrote:
On 02/01/2018 07:41 PM, Farhan Ali wrote:
The 'commit e25df1205f37 ("[S390] Kconfig: menus with
This prepares framedone interrupt handling for
manual display update support.
Signed-off-by: Sebastian Reichel
---
drivers/gpu/drm/omapdrm/omap_crtc.c | 48 +
drivers/gpu/drm/omapdrm/omap_crtc.h | 1 +
1 - 100 of 101 matches
Mail list logo