https://bugs.freedesktop.org/show_bug.cgi?id=105076
--- Comment #4 from Marta Löfstedt ---
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3779/shard-glkb1/igt@kms_...@pipe-b-bad-aux-stride.html
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=105076
--- Comment #3 from Marta Löfstedt ---
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4258/shard-glkb1/igt@drm_vma_limiter_cached.html
run.log has finished
--
You are receiving this mail because:
You are the assignee for the bug.___
Am Mittwoch, 14. Februar 2018, 21:08:59 CET schrieb Jernej Skrabec:
> dw_hdmi shouldn't set drvdata since some drivers might need to store
> it's own data there. Rework dw_hdmi in a way to return struct dw_hdmi
> instead to store it in drvdata. This way drivers are responsible to
> store and pass s
https://bugs.freedesktop.org/show_bug.cgi?id=104597
--- Comment #12 from gloriouseggr...@gmail.com ---
(In reply to Mario Kleiner from comment #5)
> Can you try what happens if you add the following snippet
> inside the section of your /etc/drirc and restart compton?
>
>
>
>
>
> The outp
https://bugs.freedesktop.org/show_bug.cgi?id=104597
--- Comment #11 from gloriouseggr...@gmail.com ---
(In reply to Mario Kleiner from comment #10)
> Created attachment 137087 [details] [review]
> Possible fix, tested against server 1.19 branch.
>
> This patch fixes the problem with compton, as t
Hi Linus,
One nouveau regression fix, one AMD quirk and a full set of i915 fixes.
The i915 fixes are mostly for things caught by their CI system, main
ones being DSI panel fixes and GEM fixes.
Pretty quiet overall.
Dave.
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1
On Thursday 15 February 2018 01:38 AM, Jernej Skrabec wrote:
dw_hdmi shouldn't set drvdata since some drivers might need to store
it's own data there. Rework dw_hdmi in a way to return struct dw_hdmi
instead to store it in drvdata. This way drivers are responsible to
store and pass structure wh
On Thursday 15 February 2018 01:38 AM, Jernej Skrabec wrote:
Parts of PHY code could be useful also for custom PHYs. For example,
Allwinner A83T has custom PHY which is probably Synopsys gen2 PHY
with few additional memory mapped registers, so most of the Synopsys PHY
related code could be reus
On Thursday 15 February 2018 01:38 AM, Jernej Skrabec wrote:
Allwinner SoCs have dw hdmi controller v1.32a which exhibits same
magenta line issue as i.MX6Q and i.MX6DL. Enable workaround for it.
Tests show that one iteration is enough.
Acked-by: Laurent Pinchart
Reviewed-by: Archit Taneja
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: ec96f6ceed1d387de0b264c59d31120c15888546 [3366/3830] drm/ttm: use an
operation ctx for ttm_tt_populate in ttm_bo_driver
config: sparc64-allyesconfig (attached as .co
On Tue, Feb 13, 2018 at 1:18 PM, Sean Paul wrote:
> Hi dri-devel,
> Qualcomm has been working for the past few weeks on forward porting their
> downstream drm driver from 4.14 to mainline. Please consider this PR as a
> request for review, rather than an attempt at mainlining the code as it
> curr
Ion is designed to be a framework used by other clients who perform
operations on the buffer. Use the DRM vgem client as a simple consumer.
In conjunction with the dma-buf sync ioctls, this tests the full attach/map
path for the system heap.
Signed-off-by: Laura Abbott
---
tools/testing/selftest
Hi,
Ion hasn't had much in the way of unit tests and fixing that is
something that needs to happen before it can move out of staging. The
difficult part of testing parts of Ion is that it relies on having a
kernel driver to actually make some of the dma_buf calls. The vgem
DRM driver exists mostly
There's no need to print messages each time we alloc and free. Remove them.
Signed-off-by: Laura Abbott
---
tools/testing/selftests/android/ion/ionutils.c | 6 --
1 file changed, 6 deletions(-)
diff --git a/tools/testing/selftests/android/ion/ionutils.c
b/tools/testing/selftests/android/i
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: 7f7a03f8049d505d450f27973d5c96af13bc8fe6 [2525/3830] drm/ttm: add
operation ctx to ttm_bo_validate v2
reproduce:
# apt-get install sparse
git checkou
On Fri, Feb 16, 2018 at 2:14 AM, Robin Murphy wrote:
> On 15/02/18 04:17, Tomasz Figa wrote:
> [...]
>>>
>>> Could you elaborate on what kind of locking you are concerned about?
>>> As I explained before, the normally happening fast path would lock
>>> dev->power_lock only for the brief moment of
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: 3f74ea1e32064cd589f8dd71cbb8fa4282c2 [2529/3830] drm/ttm: add
context to driver move callback as well
config: i386-allmodconfig (attached as .config)
compiler: g
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: d3d63af4863b870bb0153c8fe24b41218d232b10 [3809/3830] drm/amdgpu: Remove
unnecessary includes
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: 704c0ec9102104fba7fa522a1dac5c0f7f166a31 [3469/3830] drm/amdkcl: Update
pci_enable_atomic_ops_to_root for upstreaming
config: x86_64-allmodconfig (attached as .confi
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: ac9c689b72b5f0fdb7bfecc427d0aa4b2a5eccf5 [3810/3830] drm/amdgpu: Remove
unused definitions, functions and interfaces
config: i386-randconfig-a0-201806 (attached as .
https://bugs.freedesktop.org/show_bug.cgi?id=105046
--- Comment #6 from Michael Zapf ---
Created attachment 137386
--> https://bugs.freedesktop.org/attachment.cgi?id=137386&action=edit
dmesg output after turning the monitor back on (2nd system)
This is another dmesg output, created on my offic
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: d08b4d092e33c348cb01367e02e5dd2dd8104a46 [3272/3830] drm/ttm: use an
ttm operation ctx for ttm_bo_move_xxx
config: i386-randconfig-a0-201806 (attached as .config)
co
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: c30b9ce3a991b4531329cad536b3d7681acb6108 [3177/3830] amd/amdkfd: Remove
write_vmid_invalidate_request() from kfd2kgd interface
config: i386-randconfig-a0-201806 (att
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: ac9c689b72b5f0fdb7bfecc427d0aa4b2a5eccf5 [3810/3830] drm/amdgpu: Remove
unused definitions, functions and interfaces
config: i386-randconfig-i1-201806 (attached as .
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-dkms-4.13
head: 7bde112fab15c0a28c1d056959167cd4393bf538
commit: 7f7a03f8049d505d450f27973d5c96af13bc8fe6 [2525/3830] drm/ttm: add
operation ctx to ttm_bo_validate v2
config: i386-randconfig-a0-201806 (attached as .config)
compile
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Ainola changed:
What|Removed |Added
CC||b...@i--b.com
--- Comment #19 from Ainola ---
Hi Dave,
Just one fix for a hybrid laptop for 4.16.
The following changes since commit 94fc27ac487a80daf42f97b1a0503d029f3c1325:
Merge tag 'drm-intel-next-fixes-2018-02-07' of
git://anongit.freedesktop.org/drm/drm-intel into drm-next (2018-02-08 08:21:37
+1000)
are available in the git repo
Remove unused code from dpu_io_util.c. The functions are only
used inside of the msm driver so remove the EXPORT_SYMBOL
tags and move the header dpu_io_util.h from include/linux.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/msm/dp/dp_parser.h | 2 +-
drivers/gpu/drm/msm/dp
On Thu, Feb 15, 2018 at 9:19 AM, Christian König
wrote:
> amdgpu needs to verify if userspace sends us valid addresses and the simplest
> way of doing this is to check if the buffer object is locked with the ticket
> of the current submission.
>
> Clean up the access to the ww_mutex internals by p
On Thu, Feb 15, 2018 at 2:56 PM, Harry Wentland wrote:
> On 2018-02-15 11:40 AM, Daniel Stone wrote:
>> Hi Harry,
>>
>> On 15 February 2018 at 16:28, Harry Wentland wrote:
>>> This threw me for a loop when I read the docs. I imagine this is the
>>> intended definition:
>>> http://www.dict
Eric Engestrom writes:
> Can be simplified a bit:
>
> _xlib_lease = get_option('xlib-lease')
> if _xlib_lease == 'auto'
> with_xlib_lease = with_platform_x11 and with_platform_display
> else
> with_xlib_lease = _xlib_lease == 'true'
> endif
>
> (We also usually try to avoid changi
On Tue, Feb 13, 2018 at 02:18:13PM -0500, Sean Paul wrote:
> Hi dri-devel,
> Qualcomm has been working for the past few weeks on forward porting their
> downstream drm driver from 4.14 to mainline. Please consider this PR as a
> request for review, rather than an attempt at mainlining the code as i
On 2018-02-15 11:40 AM, Daniel Stone wrote:
> Hi Harry,
>
> On 15 February 2018 at 16:28, Harry Wentland wrote:
>> This threw me for a loop when I read the docs. I imagine this is the
>> intended definition:
>> http://www.dictionary.com/browse/nerf
>
> Yeah. I'm quite sure it was intende
Dave Airlie writes:
> On 6 February 2018 at 06:32, Rodrigo Vivi wrote:
>> On Sat, Feb 03, 2018 at 08:14:48AM +, Keith Packard wrote:
>>> Dhinakaran Pandiyan writes:
>>>
>>> > From: "Pandiyan, Dhinakaran"
>>> >
>>> > drm_vblank_count() has an u32 type returning what is a 64-bit vblank
>>>
Errors will be reported in /sys/kernel/debug/tracing/trace,
still not noisy enough, but better than silently ignoring them.
E.g:
-0 [000] d.h1 183.851864: malidp_de_irq: error occurred DE_STATUS
is 0x0001
surfaceflinger-803 [000] d.h1 197.993003: malidp_de_irq: error occurred
DE_ST
On 2018-02-15 12:32 AM, Daniele Castagna wrote:
> From: "uma.shankar at intel.com (Uma Shankar)"
>
> Add plane gamma as blob property and size as a
> range property.
>
Plane degamma & CTM make sense to me but I'm not sure why gamma would be on a
per-plane basis. That said, HW sometimes has the
Before returning, call of_node_put() for the device node returned by
of_parse_phandle().
Fixes: d2a34232580a ("gpu: ipu-v3: add driver for Prefetch Resolve Engine")
Signed-off-by: Tobias Jordan
---
drivers/gpu/ipu-v3/ipu-pre.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/ip
Hi Oded,
On 02/15/2018 04:08 AM, Oded Gabbay wrote:
Hi Gustavo,
The patch is queued for the merge window of kernel 4.17 (opens in
about 7 weeks from now).
Awesome.
Thanks for the info.
--
Gustavo
Oded
On Wed, Feb 14, 2018 at 11:30 PM, Gustavo A. R. Silva
wrote:
Hi all,
I was just wonde
Before returning, call of_node_put() for the device node returned by
of_parse_phandle().
Fixes: ea9c260514c1 ("gpu: ipu-v3: add driver for Prefetch Resolve Gasket")
Signed-off-by: Tobias Jordan
---
drivers/gpu/ipu-v3/ipu-prg.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/ip
On 02/15/2018 03:13 AM, Jani Nikula wrote:
On Wed, 14 Feb 2018, "Gustavo A. R. Silva" wrote:
Fix inconsistent IS_ERR and PTR_ERR in shrink_boom.
The proper pointer to use is _explode_ instead of _purge_.
This issue was detected with the help of Coccinelle.
Fixes: fe215c8bc426 ("drm/i915/sel
On 02/15/2018 06:32 AM, Christian König wrote:
Am 15.02.2018 um 06:20 schrieb Gustavo A. R. Silva:
Currently, if amdgpu_vm_bo_update() fails, the returned error
is being ignored.
Fix this by properly checking _r_ after calling amdgpu_vm_bo_update.
Also, remove redundant code just before label
Hi,
Il 08/02/2018 21:40, Maxime Ripard ha scritto:
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 it tested? This seems quite weird that we haven'
Differently from other Lcd signals, HSYNC and VSYNC signals
result inverted if their bits are cleared to 0.
Invert their settings of IO_POL register.
Signed-off-by: Giulio Benetti
---
drivers/gpu/drm/sun4i/sun4i_tcon.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/driv
Jason Ekstrand writes:
> It seems a little odd to me to default to opening the master node and then
> fall back to the render node if it doesn't work. I suppose that's probably
> ok so long as we ensure that vkGetPhysicalDeviceDisplayPropertiesKHR
> returns no displays if we're on the render nod
On 15/02/18 04:17, Tomasz Figa wrote:
[...]
Could you elaborate on what kind of locking you are concerned about?
As I explained before, the normally happening fast path would lock
dev->power_lock only for the brief moment of incrementing the runtime
PM usage counter.
My bad, that's not even it.
Hi Harry,
On 15 February 2018 at 16:28, Harry Wentland wrote:
> This threw me for a loop when I read the docs. I imagine this is the
> intended definition:
> http://www.dictionary.com/browse/nerf
Yeah. I'm quite sure it was intended to be 'nerfed', but replacing it
with something more cl
Quoting Gustavo A. R. Silva (2018-02-15 16:09:09)
>
>
> On 02/15/2018 03:13 AM, Jani Nikula wrote:
> > On Wed, 14 Feb 2018, "Gustavo A. R. Silva" wrote:
> >> Fix inconsistent IS_ERR and PTR_ERR in shrink_boom.
> >> The proper pointer to use is _explode_ instead of _purge_.
> >>
> >> This issue w
This threw me for a loop when I read the docs. I imagine this is the
intended definition:
http://www.dictionary.com/browse/nerf
Signed-off-by: Harry Wentland
---
drivers/gpu/drm/drm_ioctl.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/drm_ioct
https://bugs.freedesktop.org/show_bug.cgi?id=105113
Vedran Miletić changed:
What|Removed |Added
CC||arse...@gmail.com
Summary|[
https://bugs.freedesktop.org/show_bug.cgi?id=105113
--- Comment #1 from Vedran Miletić ---
Same story with
tests/cl/program/execute/calls-struct.cl
tests/cl/program/execute/calls-workitem-id.cl
tests/cl/program/execute/calls.cl
tests/cl/program/execute/tail-calls.cl
while
tests/cl/program/exec
Hey Rob,
Thanks for ironing out the kinks, and the new helper.
If you need reviews for any of the related changes, CC me.
This all looks good to me. Feel free to add my r-b.
Rob.
On 02/15/2018 02:59 PM, Rob Herring wrote:
The recently committed gralloc handle definition has a few issues like
On 02/12/2018 12:45 PM, Gerd Hoffmann wrote: 4. QEMU pops
data+buffers from the virtqueue, looks up shmem FD for each
resource, sends data + FDs to the compositor with SCM_RIGHTS
>>>
>>> BTW: Is there a 1:1 relationship between buffers and shmem blocks? Or
>>> does the wayland protocol
On 15.02.2018 13:14, Krzysztof Kozlowski wrote:
> On Thu, Feb 15, 2018 at 11:39 AM, Andrzej Hajda wrote:
>> OF graph describes MHL data lanes between MHL and respective USB
>> connector.
>>
>> Signed-off-by: Andrzej Hajda
>> ---
>> .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 31
>>
https://bugs.freedesktop.org/show_bug.cgi?id=105113
Bug ID: 105113
Summary: [hawaii] Running Piglit
cl/program/execute/calls-struct.cl causes GPU VM error
and ring stalled GPU lockup
Product: Mesa
Version: git
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
Product|DRI |Mesa
Component|DRM/Radeon
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #30 from Bong Cosca ---
Created attachment 137374
--> https://bugs.freedesktop.org/attachment.cgi?id=137374&action=edit
Gnome desktop
The situation has improved somehow - but screen is still unusable. I tried to
patch si_state.c wi
On Tue, Feb 13, 2018 at 09:34:26PM +0800, Qiang Yu wrote:
> Hi guys,
>
> I'm working on the Lima project for ARM mali400/450 GPU. Now lima
> kernel driver uses CMA for all buffers, but mali400/450 GPU has MMU
> for each vertex/fragment shader processor, so I want to refine the lima
> kernel driver
This avoids problems when BOs are evicted but directly moved back into
the domain from other threads.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 37 +
1 file changed, 29 insertions(+), 8 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm
This solves the problem that when we swapout a BO from a domain we
sometimes couldn't make room for it because holding the lock blocks all
other BOs with this reservation object.
Signed-off-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 33 -
1 file change
amdgpu needs to verify if userspace sends us valid addresses and the simplest
way of doing this is to check if the buffer object is locked with the ticket
of the current submission.
Clean up the access to the ww_mutex internals by providing a function
for this and extend the check to the thread ow
On Wed, Feb 14, 2018 at 11:09 PM, Tomasz Figa wrote:
> On Thu, Feb 15, 2018 at 1:12 AM, Rob Clark wrote:
>> On Wed, Feb 14, 2018 at 10:48 AM, Jordan Crouse
>> wrote:
>>> On Wed, Feb 14, 2018 at 12:31:29PM +0900, Tomasz Figa wrote:
- When submitting commands to the GPU, the GPU driver
Hi Kieran,
On Thursday, 15 February 2018 10:45:33 EET Kieran Bingham wrote:
> On 15/02/18 08:38, Kieran Bingham wrote:
> > From: Kieran Bingham
> >
> > The D3 supports two LVDS channels. Extend the binding to support them.
> >
> > Signed-off-by: Kieran Bingham
> > ---
> >
> > Documentation/d
Hi Kieran,
Thank you for the patch.
On Thursday, 15 February 2018 10:38:18 EET Kieran Bingham wrote:
> From: Kieran Bingham
>
> The D3 supports two LVDS channels. Extend the binding to support them.
>
> Signed-off-by: Kieran Bingham
> ---
> Documentation/devicetree/bindings/display/bridge/re
Clients frequently need to convert a buffer_handle_t (aka
native_handle_t *) to a gralloc_handle_t ptr. This is a simple cast, but
add an inline function to do the conversion.
Signed-off-by: Rob Herring
---
android/gralloc_handle.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/android
There's a number of problems with gralloc_handle_create starting with it
doesn't even compile. More importantly, it doesn't really create (i.e.
allocate) a handle. It allocates a native_handle_t, copies it to a
struct gralloc_handle_t on the stack and returns the struct (not a ptr).
So the caller s
Const members are problematic for dynamically allocating struct
gralloc_handle_t, so just drop the const modifier.
Signed-off-by: Rob Herring
---
android/gralloc_handle.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/android/gralloc_handle.h b/android/gralloc_handle.h
i
Fix a typo where alloc_handle_t should be gralloc_handle_t. One still
remains in gralloc_handle_create, but a subsequent commit will fix that
along with other problems in gralloc_handle_create.
Signed-off-by: Rob Herring
---
android/gralloc_handle.h | 2 +-
1 file changed, 1 insertion(+), 1 dele
The recently committed gralloc handle definition has a few issues like
not actually compiling. This series fixes those issues. I now have
things working with these fixes and switching mesa, gbm_gralloc, and
drm_hwcomposer to use this header.
Rob
Rob Herring (4):
android: revert making handle
Hi Kieran,
Thank you for the patch.
On Thursday, 15 February 2018 10:38:17 EET Kieran Bingham wrote:
> From: Kieran Bingham
>
> Document the D3 (r8a77995) SoC in the R-Car DU bindings.
>
> Signed-off-by: Kieran Bingham
Reviewed-by: Laurent Pinchart
and applied to my tree.
> ---
> Documen
On Wed, 14 Feb 2018, Anusha Srivatsa wrote:
> Forward Error Correction is supported on DP 1.4.
> This patch adds corresponding DPCD register definitions.
>
> v2: Add dri-devel mailing list to the CC list(Jani)
>
> v3: Change names, add missing masks (Manasi)
>
> v4: Add missing shifts to mask (Man
On Wed, Feb 14, 2018 at 09:08:54PM +0100, Jernej Skrabec wrote:
> This patch series implements support for A83T DW HDMI and PHY. Contrary to
> v1 series, this one is based on latest linux-next, since all needed patches
> were merged.
>
> While exactly this combination of HDMI controller and PHY is
https://bugs.freedesktop.org/show_bug.cgi?id=100759
--- Comment #3 from Alex Deucher ---
Sorry, slipped off my radar. I just sent the revert out for review.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailin
https://bugs.freedesktop.org/show_bug.cgi?id=100759
--- Comment #2 from Nicola Mori ---
Is there any chance that this bug report will be addressed?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri
Am 15.02.2018 um 06:20 schrieb Gustavo A. R. Silva:
Currently, if amdgpu_vm_bo_update() fails, the returned error
is being ignored.
Fix this by properly checking _r_ after calling amdgpu_vm_bo_update.
Also, remove redundant code just before label _error_.
Addresses-Coverity-ID: 1464280 ("Unused
From: "Sharma, Shashank"
HDMI 2.0/CEA-861-F introduces two new aspect ratios:
- 64:27
- 256:135
This patch:
- Adds new DRM flags for to represent these new aspect ratios.
- Adds new cases to handle these aspect ratios while converting
from user->kernel mode or vise versa.
This patch was once
From: "Sharma, Shashank"
Current DRM layer functions don't parse aspect ratio information
while converting a user mode->kernel mode or vice versa. This
causes modeset to pick mode with wrong aspect ratio, eventually
causing failures in HDMI compliance test cases, due to wrong VIC.
This patch add
Quoting Chris Wilson (2018-02-15 11:36:51)
> When we descend the tree to find our slot, if we step to the right, we
> are no longer the leftmost node.
Fortunately, the cached leftmost node is unused here and no drm_mm API
exposes it. So probably doesn't make sense to send it to stable@ as no
bug e
From: Ankit Nautiyal
We parse the EDID and add all the modes in the connector's modelist.
This adds CEA modes with aspect ratio information too, regadless of
whether user space requested this information or not.
This patch prunes the modes with aspect-ratio information, from a
connector's modeli
From: Ankit Nautiyal
If the user-space does not support aspect-ratio, and requests for a
modeset with mode having aspect ratio bits set, then the given
user-mode must be rejected. Secondly, while preparing a user-mode from
kernel mode, the aspect-ratio info must not be given, if aspect-ratio
is n
From: Ville Syrjälä
Make mode matching less confusing by allowing the caller to specify
which parts of the modes should match via some flags.
Signed-off-by: Ville Syrjälä
Reviewed-by: Shashank Sharma
---
drivers/gpu/drm/drm_modes.c | 134 ++--
include/d
From: Ankit Nautiyal
To enable aspect-ratio support in DRM, blindly exposing the aspect
ratio information along with mode, can break things in existing
user-spaces which have no intention or support to use this aspect
ratio information.
To avoid this, a new drm client cap is required to enable a
From: Ankit Nautiyal
If the user space does not support aspect-ratio, then getblob called
with the blob id of a user mode, should clear the aspect ratio
information in the blob data.
Currently for a given blob id, there is no way to determine if the
blob stores user mode or not. This can only b
From: Ville Syrjälä
commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer")
cause us to not send out any VICs in the AVI infoframes. That commit
was since reverted, but if and when we add aspect ratio handing back
we need to be more careful.
Let's handle this by considering the aspect
From: Ville Syrjälä
Use drm_mode_equal_no_clocks_no_stereo() in
drm_match_hdmi_mode_clock_tolerance() for consistency as we
also use it in drm_match_hdmi_mode() and the cea mode matching
functions.
This doesn't actually change anything since the input mode
comes from detailed timings and we matc
From: Ankit Nautiyal
This patch series is a re-attempt to enable aspect ratio support in DRM layer.
Currently the aspect ratio information gets lost in translation during a
user->kernel mode or vice versa.
The old patch series (https://pw-emeril.freedesktop.org/series/10850/) had
4 patches, out
On Wed, Feb 07, 2018 at 01:41:18AM +, Pandiyan, Dhinakaran wrote:
> On Fri, 2018-02-02 at 21:12 -0800, Dhinakaran Pandiyan wrote:
> > 570e86963a51 ("drm: Widen vblank count to 64-bits [v3]") changed the
> > return type for drm_crtc_vblank_count() to u64. This could cause
> > potential problems
On Thu, Feb 15, 2018 at 11:39 AM, Andrzej Hajda wrote:
> OF graph describes MHL data lanes between MHL and respective USB
> connector.
>
> Signed-off-by: Andrzej Hajda
> ---
> .../boot/dts/exynos/exynos5433-tm2-common.dtsi | 31
> +++---
> 1 file changed, 28 insertions(+), 3
On 02/15/2018 12:57 PM, Thomas Huth wrote:
> On 15.02.2018 12:26, Geert Uytterhoeven wrote:
>> Hi Christian,
>>
>> On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
>> wrote:
>>> To enable the virtual terminal layer with virtio-gpu, we need to
>>> provide the dummy console. This console is
On 15.02.2018 12:26, Geert Uytterhoeven wrote:
> Hi Christian,
>
> On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
> wrote:
>> To enable the virtual terminal layer with virtio-gpu, we need to
>> provide the dummy console. This console is hidden behind CONFIG_IOMEM
>> via the graphics supp
Hi Ville,
I have addressed your review comments (including the policy regarding,
rejection of mode with aspect ratio, if no aspect ratio cap)
and other suggestions in the next patch-set. I will be sending the next
patch-set, shortly.
Regards,
Ankit
On 2/13/2018 10:15 PM, Ville Syrjälä wr
On 02/15/2018 12:26 PM, Geert Uytterhoeven wrote:
> Hi Christian,
>
> On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
> wrote:
>> To enable the virtual terminal layer with virtio-gpu, we need to
>> provide the dummy console. This console is hidden behind CONFIG_IOMEM
>> via the graphics s
When we descend the tree to find our slot, if we step to the right, we
are no longer the leftmost node.
Fixes: f808c13fd373 ("lib/interval_tree: fast overlap detection")
Signed-off-by: Chris Wilson
Cc: Davidlohr Bueso
Cc: Jérôme Glisse
Cc: Christian König
Cc: # v4.14+
---
drivers/gpu/drm/drm
Hi Laurent,
On Thu, Feb 15, 2018 at 12:03 PM, Laurent Pinchart
wrote:
> On Thursday, 15 February 2018 11:18:25 EET Geert Uytterhoeven wrote:
>> On Thu, Feb 15, 2018 at 1:04 AM, Laurent Pinchart wrote:
>> > The internal LVDS encoders now have their own DT bindings. Before
>> > switching the driver
Hi Geert,
On Thursday, 15 February 2018 11:20:22 EET Geert Uytterhoeven wrote:
> On Thu, Feb 15, 2018 at 1:04 AM, Laurent Pinchart wrote:
> > The internal LVDS encoder now has DT bindings separate from the DU. Port
> > the device tree over to the new model.
> >
> > Signed-off-by: Laurent Pinchart
Hi Christian,
On Thu, Feb 15, 2018 at 12:14 PM, Christian Borntraeger
wrote:
> To enable the virtual terminal layer with virtio-gpu, we need to
> provide the dummy console. This console is hidden behind CONFIG_IOMEM
> via the graphics support. Instead of fully enabling the graphic
> drivers lets
To enable the virtual terminal layer with virtio-gpu, we need to
provide the dummy console. This console is hidden behind CONFIG_IOMEM
via the graphics support. Instead of fully enabling the graphic
drivers lets just provide a Kconfig option for the dummy console.
Signed-off-by: Christian Borntrae
Hi Geert,
On Thursday, 15 February 2018 11:18:25 EET Geert Uytterhoeven wrote:
> On Thu, Feb 15, 2018 at 1:04 AM, Laurent Pinchart wrote:
> > The internal LVDS encoders now have their own DT bindings. Before
> > switching the driver infrastructure to those new bindings, implement
> > backward-comp
An even simpler approach would be:
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index cbe1d978693a..35b7aba4b6a0 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@ -952,6 +952,10 @@ config S390_HYPFS_FS
source "arch/s390/kvm/Kconfig"
+config DUMMY_CONSOLE
+ bool
+ def
From: Maciej Purski
Currently MHL chip must be turned on permanently to detect MHL cable. It
duplicates micro-USB controller's (MUIC) functionality and consumes
unnecessary power. Lets use extcon attached to MUIC to enable MHL chip
only if it detects MHL cable.
Signed-off-by: Maciej Purski
Sign
Since extcon property is not allowed in DT, extcon subsystem requires
another way to get extcon device. Lets try the simplest approach - get
edev by of_node.
Signed-off-by: Andrzej Hajda
Acked-by: Chanwoo Choi
---
v2: changed label to follow local convention (Chanwoo)
---
drivers/extcon/extcon.
1 - 100 of 147 matches
Mail list logo
