On Mon, 16 Apr 2018, Clint Taylor wrote:
> On 04/16/2018 08:53 AM, Imre Deak wrote:
>> LSPCON adapters in low-power state may ignore the first I2C write during
>> TMDS output buffer enabling, resulting in a blank screen even with an
>> otherwise enabled pipe. Fix this
On Wed, Apr 18, 2018 at 05:49:58PM +0530, Sandeep Panda wrote:
> Changelog:
>
> v3 -> v4:
I didn't really bother to do a thorough review given that there are obvious
mistakes and ignored feedback, it's a waste of time, tbh. Please go through
the previous reviews and resend a more polished
Smatch complains that "area_free" could be used without being
initialized. This code is several years old and premusably works fine
so this can't be a very serious bug. But it's easy enough to silence
the warning. If "area_free" is false at the end of the function then
we return -ENOMEM.
On Wed, Apr 18, 2018 at 05:49:59PM +0530, Sandeep Panda wrote:
> Add support for TI's sn65dsi86 dsi2edp bridge chip.
> The chip converts DSI transmitted signal to eDP signal,
> which is fed to the connected eDP panel.
>
> This chip can be controlled via either i2c interface or
> dsi interface.
On Wed, Apr 18, 2018 at 12:14:03PM +0100, Alexandru-Cosmin Gheorghe wrote:
> On Tue, Apr 17, 2018 at 01:47:46PM -0400, Sean Paul wrote:
> > On Wed, Apr 11, 2018 at 04:22:28PM +0100, Alexandru Gheorghe wrote:
> > > Flatten scene on the same CRTC as the one driving the display.
> > > The active
On Tue, Apr 17, 2018 at 12:14:14PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:21PM +0100, Alexandru Gheorghe wrote:
> > When doing flattening of a composition on a different CRTC we need to be
> > able to clone a layer in order to import it and then pass it to another
> > CRTC.
> >
On 04/18/2018 01:18 PM, Paul Durrant wrote:
-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
Of Roger Pau Monné
Sent: 18 April 2018 11:11
To: Oleksandr Andrushchenko
Cc: jgr...@suse.com; Artem Mygaiev
On 04/18/18 18:51, StanLis wrote:
> From: Stanislav Lisovskiy
>
> Added encoding of drm content_type property from
> drm_connector_state within AVI infoframe in order to properly handle
> external HDMI TV content-type setting.
>
> Signed-off-by: Stanislav
On 17/04/18 20:31, Linus Walleij wrote:
On Tue, Apr 17, 2018 at 3:12 PM, Robin Murphy wrote:
On 17/04/18 13:32, Linus Walleij wrote:
[...]
Unfortunately there is just one single vexpress core tile in the
upstream kernel that define a CLCD controller, the CA9 (4xA9)
that
On Wed, 18 Apr 2018, StanLis wrote:
> +static const struct drm_prop_enum_list drm_content_type_enum_list[] = {
> + { DRM_MODE_CONTENT_TYPE_GRAPHICS, "GRAPHICS" },
> + { DRM_MODE_CONTENT_TYPE_PHOTO, "PHOTO" },
> + { DRM_MODE_CONTENT_TYPE_CINEMA, "CINEMA"
The Lenovo Ideapad Mixx 320 laptop uses a portrait LCD panel, add a
quirk for this.
While at it instead of duplicating the same drm_dmi_panel_orientation_data
for 3 laptops add a generic lcd800x1280_rightside_up orientation_data and
use that for all 3 (including the new Mixx 320 entry).
Some production batches of the Lenovo Ideapad Mixx 310 laptop use
a portrait LCD panel, add a quirk for this.
Signed-off-by: Hans de Goede
---
drivers/gpu/drm/drm_panel_orientation_quirks.c | 17 +
1 file changed, 17 insertions(+)
diff --git
On 18 April 2018 at 11:22, Noralf Trønnes wrote:
>> os.putenv('SDL_VIDEODRIVER', 'fbcon')
>> os.putenv('SDL_FBDEV' , '/dev/fb1')
>> pygame.init()
>> list = pygame.display.list_modes()
>> print "List of modes: %s" % (list)
>>
>> It shows an empty set
On Wed, Apr 18, 2018 at 11:52:18AM +0100, Daniel Thompson wrote:
> On Tue, Apr 17, 2018 at 05:42:04PM -0700, abhin...@codeaurora.org wrote:
> > Adding another point.
> >
> > On 2018-04-17 17:04, abhin...@codeaurora.org wrote:
> > > Hi Bjorn
> > >
> > > Apologies if the prev reply wasnt clear.
>
On Tue, Apr 17, 2018 at 01:02:18PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:25PM +0100, Alexandru Gheorghe wrote:
> > ApplyFrame holds the lock just when it swaps the value of
> > active_composition_, in a multithread context we could end up in a
> > situation where something is
https://bugzilla.kernel.org/show_bug.cgi?id=199319
--- Comment #17 from zxvfxwing (zxvfxw...@protonmail.com) ---
(In reply to Harry Wentland from comment #16)
> A fix should be in drm-next-4.17 of Alex's git repo at
> https://cgit.freedesktop.org/~agd5f/linux/?h=drm-next-4.17 and should make
> it
Den 16.04.2018 18.44, skrev Tom Callaway:
Noralf,
Thanks for the guidance on how to use the mi0283qt driver to run the
panel included in the Adafruit 2.8" capacitive PiTFT Plus (running on
top of a Raspberry Pi 3).
I am working with 4.16.0 (Fedora 28). I can get the driver to load, and
have
On 04/18/2018 01:18 PM, Paul Durrant wrote:
-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
Of Roger Pau Monné
Sent: 18 April 2018 11:11
To: Oleksandr Andrushchenko
Cc: jgr...@suse.com; Artem Mygaiev
On 04/18/18 18:51, StanLis wrote:
> From: Stanislav Lisovskiy
>
> Added content_type property to
> drm_connector_state in order to properly handle
> external HDMI TV content-type setting.
>
> Signed-off-by: Stanislav Lisovskiy
> ---
https://bugs.freedesktop.org/show_bug.cgi?id=104520
--- Comment #20 from hfe...@cannon.com ---
same problem here.
I am using Intel(R) Celeron(R) CPU N3160
reproduced on Linux (kernel) 4.16.2 and 4.14.34, (Mesa 17.3.8)
problem can be reproduced by starting any application using OPEN GL ES
Using drm_atomic_get_private_obj_state after state has been swapped
will return old state.
Fixes: 0281c4149021 ("drm/tegra: hub: Use private object for global state")
Signed-off-by: Stefan Schake
---
drivers/gpu/drm/tegra/hub.c | 5 ++---
1 file changed, 2 insertions(+), 3
Hi,
Please see my reply inline:
From: dri-devel [dri-devel-boun...@lists.freedesktop.org] on behalf of Hans
Verkuil [hverk...@xs4all.nl]
Sent: Wednesday, April 18, 2018 2:35 PM
To: Lisovskiy, Stanislav; dri-devel@lists.freedesktop.org
Cc:
On 18/04/18 09:52, Linus Walleij wrote:
The Versatile Express uses a special configuration controller
deeply embedded in the system motherboard FPGA to multiplex the
two to three (!) display controller instances out to the single
SiI9022 bridge.
Set up an extra file with the logic to probe to
From: Hans Verkuil [hverk...@xs4all.nl]
Sent: Wednesday, April 18, 2018 3:35 PM
To: Lisovskiy, Stanislav; dri-devel@lists.freedesktop.org
Cc: intel-...@lists.freedesktop.org
Subject: Re: [PATCH v2 2/2] i915: content-type property for HDMI connector
>> Is
On 04/18/18 14:01, Lisovskiy, Stanislav wrote:
> Hi,
>
> Please see my reply inline:
>
> From: dri-devel [dri-devel-boun...@lists.freedesktop.org] on behalf of Hans
> Verkuil [hverk...@xs4all.nl]
> Sent: Wednesday, April 18, 2018 2:35 PM
> To: Lisovskiy,
On 04/18/2018 01:55 PM, Roger Pau Monné wrote:
On Wed, Apr 18, 2018 at 01:39:35PM +0300, Oleksandr Andrushchenko wrote:
On 04/18/2018 01:18 PM, Paul Durrant wrote:
-Original Message-
From: Xen-devel [mailto:xen-devel-boun...@lists.xenproject.org] On Behalf
Of Roger Pau Monné
Sent: 18
On Tue, Apr 17, 2018 at 05:04:56PM -0700, abhin...@codeaurora.org wrote:
> Hi Bjorn
>
> Apologies if the prev reply wasnt clear.
>
> Hope this one is.
>
> reply inline.
>
> On 2018-04-17 14:29, Bjorn Andersson wrote:
> > On Tue 17 Apr 11:21 PDT 2018, abhin...@codeaurora.org wrote:
> > > On
On Wed, Apr 18, 2018 at 05:50:00PM +0530, Sandeep Panda wrote:
> Document the bindings used for the sn65dsi86 DSI to eDP bridge.
>
Please add a changelog to your patches so reviewers know what has changed
between patch versions.
> Signed-off-by: Sandeep Panda
> ---
>
On Tue, Apr 17, 2018 at 12:37:15PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:23PM +0100, Alexandru Gheorghe wrote:
> > There is a lot of boilerplate for creating an initialized
> > drmdisplaycomposition. This patch gathers that in a separate method.
> >
> > Signed-off-by: Alexandru
https://bugs.freedesktop.org/show_bug.cgi?id=104520
--- Comment #21 from hfe...@cannon.com ---
Created attachment 138905
--> https://bugs.freedesktop.org/attachment.cgi?id=138905=edit
/sys/class/drm/card0/error
--
You are receiving this mail because:
You are the assignee for the
Totally agree about caps, thanks for spotting.
From: Jani Nikula [jani.nik...@linux.intel.com]
Sent: Wednesday, April 18, 2018 2:50 PM
To: Lisovskiy, Stanislav; dri-devel@lists.freedesktop.org
Cc: intel-...@linux.intel.com
Subject: Re: [PATCH v2 1/2] drm:
On Wed, Apr 18, 2018 at 12:24:50PM +0300, Alexey Brodkin wrote:
> After commit ad67b74 ("printk: hash addresses printed with %p")
> pointers are being hashed when printed. However, this makes
> debug output completely useless. Switch to %px in order to see the
> unadorned kernel pointers.
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=106111
--- Comment #5 from Max ---
(In reply to Alex Williamson from comment #4)
> There is a difference, now we have:
>
> [ 84.997634] vfio_ecap_init: :0a:00.0 hiding ecap 0x19@0x270
> [ 84.997645] vfio_ecap_init:
https://bugzilla.kernel.org/show_bug.cgi?id=199319
--- Comment #18 from har...@gmx.de ---
@Harry Wentland,
i am trying kernel 4.17.0-rc1 (patches already merged by linus):
With 'amdgpu.dc=1', i get a black screen now at login (perhaps related to this
dc issue). I found 2 new warnings and call
On 04/18/2018 06:22 AM, Noralf Trønnes wrote:
> It turns out that the reason for this is that the pitft has a hw reset
> circuit that resets only on power-on and not on each reboot through a
> gpio like rpi-display does.
>
> When the driver is enabling the display pipeline it checks if the
>
Linus Walleij writes:
> The Versatile Express has 8 MB of dedicated video RAM (VRAM)
> on the motherboard, which is what we should be using for the
> PL111 if available. On this platform, the memory backplane
> is constructed so that only this memory will work properly
Blending win0 with the background color doesn't seem to work
correctly. We only get the background color, no matter the contents of
the win0 framebuffer. However, blending pre-multiplied color with the
default opaque black default background color is a no-op, so we can
just disable blending to
On Wed, Apr 18, 2018 at 03:42:29PM +0300, Oleksandr Andrushchenko wrote:
> On 04/18/2018 01:55 PM, Roger Pau Monné wrote:
> >On Wed, Apr 18, 2018 at 01:39:35PM +0300, Oleksandr Andrushchenko wrote:
> >>On 04/18/2018 01:18 PM, Paul Durrant wrote:
> -Original Message-
> From:
On 4/17/2018 11:17 PM, Ville Syrjälä wrote:
On Tue, Apr 17, 2018 at 10:45:07AM +0530, Nautiyal, Ankit K wrote:
On 4/6/2018 11:14 PM, Ville Syrjälä wrote:
On Fri, Apr 06, 2018 at 10:55:14PM +0530, Nautiyal, Ankit K wrote:
This patch is causing failure of IGT test kms_3d. The kms_3d test
Linus Walleij writes:
> The Versatile Express uses a special configuration controller
> deeply embedded in the system motherboard FPGA to multiplex the
> two to three (!) display controller instances out to the single
> SiI9022 bridge.
With Robin's little fixes merged
On Wed, Apr 18, 2018 at 09:38:39AM +0300, Oleksandr Andrushchenko wrote:
> On 04/17/2018 11:57 PM, Dongwon Kim wrote:
> >On Tue, Apr 17, 2018 at 09:59:28AM +0200, Daniel Vetter wrote:
> >>On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
> >>>Yeah, I definitely agree on the idea of
On 2018-04-18 05:24 AM, Alexey Brodkin wrote:
> After commit ad67b74 ("printk: hash addresses printed with %p")
> pointers are being hashed when printed. However, this makes
> debug output completely useless. Switch to %px in order to see the
> unadorned kernel pointers.
My understanding of the
https://bugs.freedesktop.org/show_bug.cgi?id=106111
--- Comment #4 from Alex Williamson ---
There is a difference, now we have:
[ 84.997634] vfio_ecap_init: :0a:00.0 hiding ecap 0x19@0x270
[ 84.997645] vfio_ecap_init: :0a:00.0 hiding ecap 0x1b@0x2d0
[
On Fri, Apr 13, 2018 at 5:48 AM, Alexandru-Cosmin Gheorghe
wrote:
> On second thought, I pushed this patchset here:
> https://github.com/ARM-software/drm-hwcomposer/tree/scene_flattening_support
Thanks for doing this! For what its worth, I've spun these up on
On Tue, Apr 17, 2018 at 05:42:04PM -0700, abhin...@codeaurora.org wrote:
> Adding another point.
>
> On 2018-04-17 17:04, abhin...@codeaurora.org wrote:
> > Hi Bjorn
> >
> > Apologies if the prev reply wasnt clear.
> >
> > Hope this one is.
> >
> > reply inline.
> >
> > On 2018-04-17 14:29,
On Tue, Apr 17, 2018 at 01:47:46PM -0400, Sean Paul wrote:
> On Wed, Apr 11, 2018 at 04:22:28PM +0100, Alexandru Gheorghe wrote:
> > Flatten scene on the same CRTC as the one driving the display.
> > The active composition is played back to the display with a buffer
> > attached to the writeback
On Wed, Apr 18, 2018 at 12:50:10PM +0100, Robin Murphy wrote:
> On 17/04/18 20:31, Linus Walleij wrote:
> > On Tue, Apr 17, 2018 at 3:12 PM, Robin Murphy wrote:
> > > On 17/04/18 13:32, Linus Walleij wrote:
> > > [...]
> > > >
> > > > Unfortunately there is just one single
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #35 from i...@yahoo.com ---
Any results?
Enable SysRq, start Xonotic, set r_shadow 2, play until it crashes, use SysRq
to sync, umonut, reboot.
After reboot, check if the crash has been captured by syslog/journald.
If there is
On 2018-04-17 13:28, Sean Paul wrote:
On Mon, Apr 16, 2018 at 05:40:13PM -0700, Chandan Uddaraju wrote:
For dual dsi mode, the horizontal timing needs
to be divided by half since both the dsi controllers
will be driving this panel. Adjust the pixel clock and
DSI timing accordingly.
Changes in
https://bugzilla.kernel.org/show_bug.cgi?id=199319
--- Comment #19 from Harry Wentland (harry.wentl...@amd.com) ---
@haro41, I recommend opening a new bug if you're seeing a different issue,
unless you have strong reason to believe it's caused by the fixes for the
flickering screen, or otherwise
On Wed, Apr 18, 2018 at 10:31:52AM -0700, Kristian H. Kristensen wrote:
> Blending win0 with the background color doesn't seem to work
> correctly.
Did you come to a conclusion about whether this applies across all Rk vops, or
just 3399 big?
Sean
> We only get the background color, no matter
Hi Dave,
Here's the first misc-fixes pull. It unfortunately contains a backmerge due to
Eric committing Daniel's patch before I had a chance to fast forward. Anyways,
it's not too convoluted, so I'll try to win the race this week :-). In general,
this is going to become more common as the number
For dual dsi mode, the horizontal timing needs
to be divided by half since both the dsi controllers
will be driving this panel. Adjust the pixel clock and
DSI timing accordingly.
Changes in V2:
--Removed Change-Id from the commit text tags.
Changes in V3:
--Instead of adjusting the DRM mode
This patch series adds support to DSI connector
virtualization for Dual-DSI configuration.
These changes have been tested using dual-dsi truly panel on sdm845 platform.
Additional changes that will be needed to have end-to-end functionality:
--> DSI6G-v2 changes:
Current DSI driver uses two connectors for dual DSI case even
though we only have one panel. Fix this by implementing one
connector/bridge for dual DSI use case. Use master DSI
controllers to register one connector/bridge.
Changes in V2:
-Removed Change-Id from the commit text tags.
On Tue, 17 Apr 2018 15:10:50 +0200
Peter Rosin wrote:
> This beats the heuristic that the connector is involved in what format
> should be output for cases where this fails.
>
> E.g. if there is a bridge that changes format between the encoder and the
> connector, or if some of
On Tue, 17 Apr 2018 15:10:52 +0200
Peter Rosin wrote:
> Bump the minor version while at it.
>
> Signed-off-by: Peter Rosin
> ---
> drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git
Op 18-04-18 om 11:59 schreef Alexey Brodkin:
> On Wed, 2018-04-18 at 11:29 +0200, Maarten Lankhorst wrote:
>> Op 18-04-18 om 11:24 schreef Alexey Brodkin:
>>> After commit ad67b74 ("printk: hash addresses printed with %p")
>>> pointers are being hashed when printed. However, this makes
>>> debug
On Tue 17 Apr 11:21 PDT 2018, abhin...@codeaurora.org wrote:
> On 2018-04-16 23:13, Bjorn Andersson wrote:
[..]
> > If the panel isn't actually a piece of backlight hardware then it should
> > not register a backlight device. Why do you need your own sysfs?
> >
> > Regards,
> > Bjorn
> [Abhinav]
When the of-graph points to a tda998x-compatible HDMI encoder, register
as a component master and bind to the encoder/connector provided by
the tda998x driver.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 81 --
On 04/17/2018 12:08 PM, Oleksandr Andrushchenko wrote:
On 04/17/2018 12:04 PM, Daniel Vetter wrote:
On Tue, Apr 17, 2018 at 10:40:12AM +0300, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Even if xen-front allocates its buffers from contiguous
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Reference id -> 1c8f422059ae ("mm: change return type to
vm_fault_t")
On 17.04.2018 12:00, Daniel Vetter wrote:
> On Mon, Apr 16, 2018 at 03:16:27PM +0300, Dmitry Osipenko wrote:
>> Colorkey'ing allows to draw on top of overlapping planes, like for example
>> on top of a video plane. Older Tegra's have a limited colorkey'ing
>> capability such that blending features
On 4/17/2018 11:58 AM, Robin Murphy wrote:
> The amdgpu driver doesn't appear to directly use the scatterlist mapped
> by amdgpu_ttm_tt_pin_userptr(), it merely hands it off to
> drm_prime_sg_to_page_addr_arrays() to generate the dma_address array
> which it actually cares about. Now that the
Bump the minor version while at it.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c
b/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c
From: Stanislav Lisovskiy
Added encoding of drm content_type property from
drm_connector_state within AVI infoframe in order to properly handle
external HDMI TV content-type setting.
Signed-off-by: Stanislav Lisovskiy
---
From: Stanislav Lisovskiy
Added content type setting property to drm_connector(part 1)
and enabled transmitting it with HDMI AVI infoframes
for i915(part 2).
rev 2:
Moved helper function which attaches content type property
to the drm core, as was suggested.
https://bugs.freedesktop.org/show_bug.cgi?id=105317
--- Comment #9 from mikhail.v.gavri...@gmail.com ---
I don't thinks so because if it happens again by another reason GPU again will
hang.
I will be happy if it this case GPU reset code will present in driver.
--
You are receiving this mail
Hi Peter,
On Tue, 17 Apr 2018 15:10:48 +0200
Peter Rosin wrote:
> With bus-type/bus-width properties in the endpoint nodes, the video-
> interface of the connection can be specified for cases where the
> heuristic fails to select the correct output mode. This can happen
> e.g.
On Wed, Apr 18, 2018 at 5:58 AM, Keith Packard wrote:
> Michel Dänzer writes:
>> Time-based presentation seems to be the right approach for preventing
>> micro-stutter in games as well, Croteam developers have been researching
>> this.
>
> Both the Vulkan
On 04/18/2018 10:35 AM, Roger Pau Monné wrote:
On Wed, Apr 18, 2018 at 09:38:39AM +0300, Oleksandr Andrushchenko wrote:
On 04/17/2018 11:57 PM, Dongwon Kim wrote:
On Tue, Apr 17, 2018 at 09:59:28AM +0200, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
3.2
https://bugs.freedesktop.org/show_bug.cgi?id=106115
Bug ID: 106115
Summary: Changing display's orientation hits
[drm:generic_reg_wait [amdgpu]] *ERROR* REG_WAIT
timeout 1us * 10 tries - optc1_lock line:553
Product: DRI
From: Stanislav Lisovskiy
Added content_type property to
drm_connector_state in order to properly handle
external HDMI TV content-type setting.
Signed-off-by: Stanislav Lisovskiy
---
Documentation/gpu/kms-properties.csv | 1 +
On Tue, Apr 17, 2018 at 07:17:55PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler. For
> now, this is just documenting that the function returns
> a VM_FAULT value rather than an errno. Once all instances
> are converted, vm_fault_t will become a distinct type.
>
On Tue, 17 Apr 2018 15:10:51 +0200
Peter Rosin wrote:
> When the of-graph points to a tda998x-compatible HDMI encoder, register
> as a component master and bind to the encoder/connector provided by
> the tda998x driver.
Can't we do the opposite: make the tda998x driver expose
From: Stanislav Lisovskiy
Added content_type property to
drm_connector_state in order to properly handle
external HDMI TV content-type setting.
Signed-off-by: Stanislav Lisovskiy
---
Documentation/gpu/kms-properties.csv | 1 +
From: Stanislav Lisovskiy
Added content type setting property to drm_connector(part 1)
and enabled transmitting it with HDMI AVI infoframes
for i915(part 2).
rev 2:
Moved helper function which attaches content type property
to the drm core, as was suggested.
From: Stanislav Lisovskiy
Added encoding of drm content_type property from
drm_connector_state within AVI infoframe in order to properly handle
external HDMI TV content-type setting.
Signed-off-by: Stanislav Lisovskiy
---
Hi Daniel,
On Tuesday 17 April 2018 05:51 PM, Daniel Mack wrote:
(cc Stephen)
Hi Archit,
On Monday, April 16, 2018 07:06 PM, Daniel Mack wrote:
On Monday, April 09, 2018 03:08 PM, Archit Taneja wrote:
You could comment out the pm_runtime_put_sync() calls in
On Wed, 18 Apr 2018 09:31:53 +0200
Peter Rosin wrote:
> On 2018-04-18 09:16, Boris Brezillon wrote:
> > Hi Peter,
> >
> > On Tue, 17 Apr 2018 15:10:48 +0200
> > Peter Rosin wrote:
> >
> >> With bus-type/bus-width properties in the endpoint nodes, the video-
Not exactly. The plan for these patches is to introduce new vm_fault_t type
in vm_operations_struct fault handlers. It's now available in 4.17-rc1. We will
push all the required drivers/filesystem changes through different maintainers
to linus tree. Once everything is converted into vm_fault_t
Start list of actual chips compatible with "lvds-encoder".
Reviewed-by: Laurent Pinchart
Reviewed-by: Rob Herring
Signed-off-by: Peter Rosin
---
.../devicetree/bindings/display/bridge/lvds-transmitter.txt | 8 +++-
On 17.04.2018 12:01, Daniel Vetter wrote:
> On Mon, Apr 16, 2018 at 03:16:28PM +0300, Dmitry Osipenko wrote:
>> This new property allows userspace to apply custom color conversion
>> coefficients per plane, making possible to utilize display controller
>> for color adjustments of a video overlay.
Daniel,
Oddly thunderbird and gmail webinterface are refusing to add your 'Daniel Vetter
' to list of recipients automatically.
On 17.04.2018 20:08, Dmitry Osipenko wrote:
> On 17.04.2018 12:00, Daniel Vetter wrote:
>> On Mon, Apr 16, 2018 at 03:16:27PM +0300, Dmitry Osipenko
On Tue, Apr 17, 2018 at 09:14:32PM +0530, Souptick Joarder wrote:
> Not exactly. The plan for these patches is to introduce new vm_fault_t type
> in vm_operations_struct fault handlers. It's now available in 4.17-rc1. We
> will
> push all the required drivers/filesystem changes through different
Add a central function to parse a node according to the video
interface binding and get a media bus format.
Start with only supporting a very limited set of a few basic media
bus formats.
Signed-off-by: Peter Rosin
---
drivers/gpu/drm/drm_of.c | 38
Testing my responsde
On 04/17/2018 11:21 AM, abhin...@codeaurora.org wrote:
Hi Bjorn
Thanks for the comments.
Reply inline.
On 2018-04-16 23:13, Bjorn Andersson wrote:
On Mon 16 Apr 15:45 PDT 2018, abhin...@codeaurora.org wrote:
Hi Bjorn
Thanks for the review.
Reply inline.
On
On 17-Apr-2018 9:45 PM, "Matthew Wilcox" wrote:
>
> On Tue, Apr 17, 2018 at 09:14:32PM +0530, Souptick Joarder wrote:
> > Not exactly. The plan for these patches is to introduce new vm_fault_t
type
> > in vm_operations_struct fault handlers. It's now available in 4.17-rc1.
We
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Reference id -> 1c8f422059ae ("mm: change return type to
vm_fault_t")
This beats the heuristic that the connector is involved in what format
should be output for cases where this fails.
E.g. if there is a bridge that changes format between the encoder and the
connector, or if some of the RGB pins between the lcd controller and the
encoder are not routed on the PCB.
With bus-type/bus-width properties in the endpoint nodes, the video-
interface of the connection can be specified for cases where the
heuristic fails to select the correct output mode. This can happen
e.g. if not all RGB pins are routed on the PCB; the driver has no
way of knowing this, and needs
(cc Stephen)
Hi Archit,
On Monday, April 16, 2018 07:06 PM, Daniel Mack wrote:
> On Monday, April 09, 2018 03:08 PM, Archit Taneja wrote:
You could comment out the pm_runtime_put_sync() calls in
drivers/gpu/drm/msm/dsi/dsi_host.c, in case some registers got
reset during put_sync
Hi!
I naively thought that since there was support for both nxp,tda19988 (in
the tda998x driver) and the atmel-hlcdc, things would be a smooth ride.
But it wasn't, so I started looking around, and found some missing
pieces in the tilcdc driver. I "stole" some things and made it work
for my use
Use new return type vm_fault_t for fault handler. For
now, this is just documenting that the function returns
a VM_FAULT value rather than an errno. Once all instances
are converted, vm_fault_t will become a distinct type.
Reference id -> 1c8f422059ae ("mm: change return type to
vm_fault_t")
https://bugs.freedesktop.org/show_bug.cgi?id=103743
--- Comment #12 from Samuel Pitoiset ---
Any news on this? The two LLVM patches have been pushed ~2 weeks ago. Can you
still reproduce the issue? Thanks!
--
You are receiving this mail because:
You are the assignee
On 04/18/2018 12:12 PM, Alexandru-Cosmin Gheorghe wrote:
On Tue, Apr 17, 2018 at 06:08:06PM +0200, Robert Foss wrote:
Hey,
On 04/17/2018 05:33 PM, Sean Paul wrote:
On Wed, Apr 11, 2018 at 04:22:15PM +0100, Alexandru Gheorghe wrote:
Add a resource manager object that is responsible for
On 04/17/2018 11:57 PM, Dongwon Kim wrote:
On Tue, Apr 17, 2018 at 09:59:28AM +0200, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
Yeah, I definitely agree on the idea of expanding the use case to the
general domain where dmabuf sharing is used. However,
On Fri, 30 Mar 2018 16:55:18 +0200
Boris Brezillon wrote:
> ->atomic_async_update() requires that drivers update the plane->state
> object before returning. Make sure at least common properties have been
> updated.
>
> Cc: Gustavo Padovan
>
On Wed, 18 Apr 2018 09:46:09 +0200
Peter Rosin wrote:
> On 2018-04-18 09:29, Boris Brezillon wrote:
> > On Tue, 17 Apr 2018 15:10:50 +0200
> > Peter Rosin wrote:
> >
> >> This beats the heuristic that the connector is involved in what format
> >> should be
On Wed, 18 Apr 2018 10:02:12 +0200
Peter Rosin wrote:
> On 2018-04-18 09:36, Boris Brezillon wrote:
> > On Tue, 17 Apr 2018 15:10:51 +0200
> > Peter Rosin wrote:
> >
> >> When the of-graph points to a tda998x-compatible HDMI encoder, register
> >> as a
1 - 100 of 114 matches
Mail list logo