Daniel
Thanks! I agree the PATCH 1/2 needs some more work.
What do you think about the PATCH 2/2 (suspend/resume) -- would it
make sense to review it as a single standalone patch?
Regards, Haixia
On Wed, Aug 31, 2016 at 2:17 PM, Daniel Vetter wrote:
> On Wed, Aug 31, 2016 at 11:05 PM, Daniel
This can be useful for debugging. xrandr prints it, so why not.
---
tests/modetest/modetest.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tests/modetest/modetest.c b/tests/modetest/modetest.c
index 21d5438..dedd286 100644
--- a/tests/modetest/modetest.c
+++
Hi David,
On Tue, Aug 30, 2016 at 09:30:44PM +0200, David Herrmann wrote:
> Hi Rob
> IOW the device handover code somehow needs to know who was responsible
> for the instantiation of the simple-framebuffer device, so it can tell
> them to remove it again. On x86 there is only one place where
Hi
On Tue, Aug 30, 2016 at 10:58 PM, Rob Herring wrote:
> On Tue, Aug 30, 2016 at 2:30 PM, David Herrmann
> wrote:
>> Sure, all those functions are not meant to be called in parallel by
>> multiple tasks. They are rather meant to have a single holder which
>> preferably
On Tue, Aug 30, 2016 at 8:56 PM, Maxime Ripard
wrote:
> Hi,
>
> On Tue, Aug 30, 2016 at 08:22:23PM +0800, Chen-Yu Tsai wrote:
>> The KMS helpers (drm_atomic_helper_check_modeset/mode_fixup) pass
>> encoder->bridge directly to drm_bridge_mode_fixup, which expects a
>> valid pointer, or NULL (in
We get some warnings when building kernel with W=1:
drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxgf117.c:222:1: warning: no previous
prototype for 'gf117_grctx_generate_main' [-Wmissing-prototypes]
drivers/gpu/drm/nouveau/nvkm/engine/gr/ctxnv50.c:255:1: warning: no previous
prototype for
nsolidate all of them into one patch this
> > time? or next time?
>
> I'd suggest consolidating the 'nouveau' changes into a single patch,
> as this is one (very big) driver and resend that one.
>
> Arnd
>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/2a3390ab/attachment-0001.html>
ether'?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/01e54601/attachment-0001.html>
Patrik Jakobsson wrote on 2016/08/30 18:21:08:
> Patrik Jakobsson
> 2016/08/30 18:21
>
> From
> jiang.biao2 at zte.com.cn,
> cc
> dri-devel
> Re: [PATCH] drm/gma500: remove the process of stolen page in page fault
> handler.
>
> On Tue, Aug 30, 2016 at 7:10 AM, wrote:
> >
> > Direct gtt
was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/4beed300/attachment.html>
il because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/bf436b4d/attachment.html>
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/aa1570ba/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160831/bf76404f/attachment.html>
...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/ee50ede0/attachment.html>
attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/f3952cbd/attachment-0001.html>
attached is now gone on subsequent freeze()/thaw() cycles.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/27023
was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/76a79ee8/attachment.html>
because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/99530e3f/attachment.html>
Hi,
On 08/29/2016 03:00 PM, Jose Abreu wrote:
> Colorspace and scan information values were being written in wrong
> offsets. This patch corrects this and writes the values at the
> offsets specified in the databook.
queued to drm-misc after cleaning up some checkpatch
errors.
Thanks,
Archit
>
vel/attachments/20160831/cf400d9b/attachment.html>
v4:
Only DRM patchset is sent, DTS patch was sent separately.
Milo Kim (3):
gpu: drm: exynos_hdmi: Move DDC logic into single function
gpu: drm: exynos_hdmi: Move PHY logic into single function
gpu: drm: exynos_hdmi: Remove duplicate initialization of regulator
bulk consumer
Paring DT properties and getting the I2C adapter in one function.
Cc: Inki Dae
Cc: Joonyoung Shim
Cc: Seung-Woo Kim
Cc: Kyungmin Park
Cc: dri-devel at lists.freedesktop.org
Cc: linux-kernel at vger.kernel.org
Signed-off-by: Milo Kim
---
drivers/gpu/drm/exynos/exynos_hdmi.c | 46
Paring DT properties and getting PHY IO (memory mapped or I2C) in one
function.
Cc: Inki Dae
Cc: Joonyoung Shim
Cc: Seung-Woo Kim
Cc: Kyungmin Park
Cc: dri-devel at lists.freedesktop.org
Cc: linux-kernel at vger.kernel.org
Signed-off-by: Milo Kim
---
drivers/gpu/drm/exynos/exynos_hdmi.c |
The helper, devm_regulator_bulk_get() initializes the consumer as NULL,
so this code can be ignored.
Reviewed-by: Andrzej Hajda
Cc: Inki Dae
Cc: Joonyoung Shim
Cc: Seung-Woo Kim
Cc: Kyungmin Park
Cc: dri-devel at lists.freedesktop.org
Cc: linux-kernel at vger.kernel.org
Signed-off-by: Milo
Hi Krzysztof,
On 08/25/2016 04:05 AM, Krzysztof Kozlowski wrote:
> First of all - it looks like these DTS patches do not depend on DRM
> part, do they?
I just sent the v4 patch for DTS. DRM patch-set was sent separately.
Thanks for your advise.
Best regards,
Milo
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160831/b0514b7d/attachment.html>
tps://lists.freedesktop.org/archives/dri-devel/attachments/20160831/c64b5180/attachment.html>
On 08/31/2016 08:14 AM, Milo Kim wrote:
> Paring DT properties and getting the I2C adapter in one function.
>
> Cc: Inki Dae
> Cc: Joonyoung Shim
> Cc: Seung-Woo Kim
> Cc: Kyungmin Park
> Cc: dri-devel at lists.freedesktop.org
> Cc: linux-kernel at vger.kernel.org
> Signed-off-by: Milo Kim
>
Hey Rob!
On Wed, Aug 31, 2016 at 1:01 AM, Rob Herring wrote:
> On Tue, Aug 30, 2016 at 4:12 PM, David Herrmann
> wrote:
>> Currently I see at least 3 paths that might add such nodes:
>>
>> - of_platform_populate()
>
> If we assume the node is only under chosen, then
On 08/31/2016 08:14 AM, Milo Kim wrote:
> Paring DT properties and getting PHY IO (memory mapped or I2C) in one
> function.
>
> Cc: Inki Dae
> Cc: Joonyoung Shim
> Cc: Seung-Woo Kim
> Cc: Kyungmin Park
> Cc: dri-devel at lists.freedesktop.org
> Cc: linux-kernel at vger.kernel.org
>
On Wed, 31 Aug 2016 11:29:53 +0900
Hyung Jin Jung wrote:
> According to Atmel's guideline...
> http://www.at91.com/linux4sam/bin/view/Linux4SAM/UsingAtmelDRMDriver
>
> the "fbdev emulation mode" could be set from kernel command line (LVDS-1:...)
> however, driver register it as
On Tue, Aug 30, 2016 at 02:50:20PM -0700, Haixia Shi wrote:
> Previously this function had a NULL pointer check for gem->map_list.map, but
> that line was refactored after commit
> 0de23977cfeb5b357ec884ba15417ae118ff9e9bb
> ("drm/gem: convert to new unified vma manager").
>
> After the refactor
According to Atmel's guideline...
http://www.at91.com/linux4sam/bin/view/Linux4SAM/UsingAtmelDRMDriver
the "fbdev emulation mode" could be set from kernel command line (LVDS-1:...)
however, driver register it as DRM_MODE_CONNECTOR_Unknown connector.
Actually we using sama5d3x with LVDS cable so
Hi,
This serie introduces the support for the NextThing GR8.
This SoC is loosely based on the SoCs of the Allwinner sun5i family,
hence we can use most of the support already there. Compared to the
already existing A10s and A13/R8, the pin layout completely changed,
meaning that also the set of
Some backlight GPIOs might be connected to some i2c based expanders whose
access might sleep.
Since it's not in any critical path, use the cansleep variant of the GPIO
API.
Signed-off-by: Maxime Ripard
---
drivers/video/backlight/pwm_bl.c | 4 ++--
1 file changed, 2 insertions(+), 2
The A10-EVB from Allwinner comes with an unidentified panel, with the only
mark on the PCB being A10-SUB-EVB-5LCD.
Add timings to simple panel to handle it.
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/panel/panel-simple.c | 26 ++
1 file changed, 26 insertions(+)
From: Mylène Josserand
Just like the other member of the sunxi family, let's add a pinctrl table
for the muxing options.
Signed-off-by: Mylène Josserand
Signed-off-by: Maxime Ripard
---
.../bindings/pinctrl/allwinner,sunxi-pinctrl.txt | 1 +
The GR8 is an SoC made by Nextthing Co, loosely based on the sun5i family.
It has a number of new controllers compared to the A10s and A13 (SPDIF, I2S),
but some controllers missing too (Ethernet, less I2C, less UARTs).
Signed-off-by: Maxime Ripard
---
From: Mylène Josserand
The GR8 is an SoC made by Nextthing loosely based on the sun5i family.
Since it's not clear yet what we can factor out and merge with the A10s and
A13 support, let's keep it out of the sun5i.dtsi include tree. We will
figure out what
From: Mylène Josserand
The GR8-EVB is a small board with an NextThing GR8, an Hynix MLC NAND,
an AXP209 PMIC, USB host and OTG, an SPDIF output and a connectors for CSI,
I2S and LCD.
Signed-off-by: Mylène Josserand
Signed-off-by: Maxime Ripard
---
drm_atomic_state has a complicated single owner model that tracks the
single reference from allocation through to destruction on another
thread - or perhaps on a local error path. We can simplify this tracking
by using reference counting (at a cost of a few more atomics). This is
even more
ADV7533 requires supply to the AVDD, V1P2 and V3P3 pins for proper
functionality.
Initialize and enable the regulators during probe itself. Controlling
these dynamically is left for later.
Cc: dri-devel at lists.freedesktop.org
Cc: Laurent Pinchart
Signed-off-by: Archit Taneja
---
attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/1819c8e6/attachment.html>
On Tue, 30 Aug 2016, Peter Griffin wrote:
> On Tue, 30 Aug 2016, Lee Jones wrote:
> > On Fri, 26 Aug 2016, Peter Griffin wrote:
> >
> > > slim core is used as a basis for many IPs in the STi
> > > chipsets such as fdma and demux. To avoid duplicating
> > > the elf loading code in each device
On Wed, Aug 31, 2016 at 02:09:05PM +0300, Peter Ujfalusi wrote:
> drm_kms_helper_poll_enable_locked() should check if we have delayed event
> pending and if we have, schedule the work to run without delay.
>
> Currently the output_poll_work is only scheduled if any of the connectors
> have
On Tue, 30 Aug 2016, Peter Griffin wrote:
> Thanks for reviewing and your very valuable feedback.
> On Tue, 30 Aug 2016, Lee Jones wrote:
> > On Fri, 26 Aug 2016, Peter Griffin wrote:
> >
> > > This patch adds the DT node for the uniperif reader
> > > IP block found on STiH407 family silicon.
> >
On Wed, Aug 31, 2016 at 01:27:36PM +0200, Roland Singer wrote:
> Am 30.08.2016 um 21:53 schrieb Peter Wu:
> > On Mon, Aug 29, 2016 at 11:02:10AM -0500, Bjorn Helgaas wrote:
> >> [+cc linux-acpi, linux-kernel, dri-devel]
> >>
> >> Hi Roland,
> >>
> >> I have no idea how to debug this problem. Are
On Wed, 31 Aug 2016, Maxime Ripard wrote:
> Some backlight GPIOs might be connected to some i2c based expanders whose
> access might sleep.
>
> Since it's not in any critical path, use the cansleep variant of the GPIO
> API.
>
> Signed-off-by: Maxime Ripard
> ---
>
Hi,
On 08/30/2016 12:50 AM, Randy Li wrote:
> It is actually a lvds panel connected through a rga-lvds bridge.
> But I really have no idea about what does a port mean in fimd node.
>
> Also how should I configure this panel size? I think the i2c found
> on the panel schematic, but it more likely
On Wed, Aug 31, 2016 at 02:21:31PM +0200, Roland Singer wrote:
> Am 31.08.2016 um 13:46 schrieb Peter Wu:
> > On Wed, Aug 31, 2016 at 01:27:36PM +0200, Roland Singer wrote:
> >> Am 30.08.2016 um 21:53 schrieb Peter Wu:
> >>> On Mon, Aug 29, 2016 at 11:02:10AM -0500, Bjorn Helgaas wrote:
>
Dear all,
This is a quick fix of the incorrect usage of runtime pm for system sleep
pm purposes. Patches introduce usage of the generic helpers
pm_runtime_force_{suspend,resume} instead of open-coding them, which was
potentially broken for some corner cases. The side-effect of this patch
set is
Use generic helpers instead of open-coding usage of runtime pm for system
sleep pm, which was potentially broken for some corner cases.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_fimc.c | 29 ++---
1 file changed, 2 insertions(+), 27
Use generic helpers instead of open-coding usage of runtime pm for system
sleep pm, which was potentially broken for some corner cases.
Signed-off-by: Marek Szyprowski
---
drivers/staging/media/s5p-cec/s5p_cec.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff
Use generic helpers instead of open-coding usage of runtime pm for system
sleep pm, which was potentially broken for some corner cases.
Signed-off-by: Marek Szyprowski
---
drivers/media/platform/s5p-jpeg/jpeg-core.c | 24
1 file changed, 4 insertions(+), 20 deletions(-)
Use generic helpers instead of open-coding usage of runtime pm for system
sleep pm, which was potentially broken for some corner cases.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_rotator.c | 26 ++
1 file changed, 2 insertions(+), 24
Move code from system sleep pm to runtime pm callbacks to ensure proper
driver state preservation when device is under power domain. Then, use
generic helpers for using runtime pm for system sleep pm.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_g2d.c | 29
Use generic helpers instead of open-coding usage of runtime pm for system
sleep pm, which was potentially broken for some corner cases.
Signed-off-by: Marek Szyprowski
---
drivers/gpu/drm/exynos/exynos_drm_gsc.c | 29 ++---
1 file changed, 2 insertions(+), 27
message 201 ret is 0
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/58e4101c/attachment-0001.html>
drm_helper_disable_unused_functions() should not be called by atomic
drivers.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c
b/drivers/gpu/drm/tilcdc/tilcdc_drv.c
index 3404d24..e45c268
Changes since v2:
- Fiddle with color wiring propety once more, now it follows this Tomi's
comment:
- No property set: driver advertises RG16 and RG24. This is
wrong, but that's what the current status is, right?
- Property set to "default" or "straight" or whatever: driver
says RG16
Write DMA base and ceiling address with a single instruction, if
available. This should make it more unlikely that LCDC would fetch the
DMA addresses in the middle of an update. Having bad combination of
addresses in dma base and ceiling (e.g base > ceiling) can cause
unpredictaple behavior in
Choose console BPP that supports RGB and remove the old fbdev bpp
selection code. LCDC on AM335x has red and blue wires switched between
24 bit and 16 bit colors. If 24 format is wired for RGB colors, the 16
bit format is wired for BGR. drm_fbdev_cma_init() does not currently
like anything else
Add "blue-and-red-wiring"-device tree property and update devicetree
binding document. The red and blue components are reversed between 24
and 16 bit modes on am335x LCDC output pins. To get 24 RGB format the
red and blue wires has to be crossed and this in turn causes 16 colors
output to be in
Add blue-and-red-wiring -property to lcdc node. The am335x-evm has
blue and red wires crossed to get 24-bit RGB (and 16-bit BGR)
support. After this patch am335x-evm supports BGR565, RGB888, and
XRGB color formats. See details in
Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt.
Add blue-and-red-wiring -property to LCDC node. Also adds comments on
how to get support 24 bit RGB mode. After this patch am335x-boneblack
support RGB565, BGR888, and XBGR color formats. See details in
Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt.
The BBB has straight color
Add blue-and-red-wiring -property to lcdc node. The am335x-evmsk has
blue and red wires crossed to get 24-bit RGB (and 16-bit BGR)
support. After this patch am335x-evmsk supports BGR565, RGB888, and
XRGB color formats. See details in
Documentation/devicetree/bindings/display/tilcdc/tilcdc.txt.
Whitespace cleanup of lcdc related nodes. Do all indentation and
alignment with tabs instead of spaces.
Signed-off-by: Jyri Sarha
---
arch/arm/boot/dts/am335x-evmsk.dts | 40 +++---
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git
e Mesa driver such that
looking at other drivers won't likely help.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831
ext part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/3e4e599c/attachment.html>
vel/attachments/20160831/645a84bf/attachment.html>
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/cb11b372/attachment-0001.html>
nee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/af4a97aa/attachment.html>
bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/df3151ac/attachment.html>
>>
> >> + if (IS_ERR(encoder->bridge))
> >> + encoder->bridge = NULL;
> >> +
> >
> > And that could be the else condition of the if statement below.
>
> That would be a bit confusing, changing it after calling drm_encoder_init.
> The code says it ok to do though.
The magic really happens only after the encoder has been attached to
something, so it's really safe.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/6f45c0e7/attachment.sig>
Hi Archit,
Thank you for the patch.
On Wednesday 31 Aug 2016 16:22:09 Archit Taneja wrote:
> ADV7533 requires supply to the AVDD, V1P2 and V3P3 pins for proper
> functionality.
>
> Initialize and enable the regulators during probe itself. Controlling
> these dynamically is left for later.
You
Hi all,
It's not entirely done yet, there's a few (very small bits) left in drm_crtc.c
which aren't for struct drm_crtc. But I figured it's better to keep things in
manageable pieces.
More important this now contains my proposal for how to best document (atomic)
property extensions. I grouped
Now that there's less stuff in there I noticed that I overlooked them.
Sprinkle some docs over them while at it.
Signed-off-by: Daniel Vetter
---
include/drm/drm_connector.h | 24 ++--
include/drm/drm_crtc.h| 32
We don't want to burry the bridge structures kerneldoc in drm_crtc.h.
Cc: Archit Taneja
Signed-off-by: Daniel Vetter
---
Documentation/gpu/drm-kms-helpers.rst | 7 ++
drivers/gpu/drm/drm_bridge.c | 5 +-
include/drm/drm_bridge.h | 218
Some were still left in drm_crtc.h. Also include drm_edid.h in the
rst files.
Signed-off-by: Daniel Vetter
---
Documentation/gpu/drm-kms-helpers.rst | 3 +++
include/drm/drm_crtc.h| 30 +-
include/drm/drm_edid.h| 30
Imo zpos, rotatation, blending eq (once we have it) and all that
should be in drm_blend.c, since those are all about how exactly the
pixels are rendered onto the CRTC's visible area. Also noticed that
one exported function accidentally ended up in drm_crtc_internal.h,
move it to the right place
Try to spec a bit more precisely how they all fit together, now that
at least the code is for all the additional properties is in one
place.
Also remove the entries for the standardized properties from the
table, because that thing is supremely unmaintaineable.
Cc: Ville Syrjälä
Cc: Sean Paul
Just pure code movement, cleanup and polish will happen in later
patches.
v2: Don't forget all the ioctl! To extract those cleanly I decided to
put check_src_coords into drm_framebuffer.c (and give it a
drm_framebuffer_ prefix), since that just checks framebuffer
constraints.
Signed-off-by:
For both the new degamm/lut/gamma atomic combo, and the old legacy
gamma tables.
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/Makefile| 2 +-
drivers/gpu/drm/drm_color_mgmt.c| 248
drivers/gpu/drm/drm_crtc.c | 220
Again move it from the unmaintainable csv into DOC free-form overview
sections.
Cc: Lionel Landwerlin
Signed-off-by: Daniel Vetter
---
Documentation/gpu/drm-kms.rst| 12 +
Documentation/gpu/kms-properties.csv | 5
drivers/gpu/drm/drm_color_mgmt.c | 48
We removed it in
commit 6ab10b76ff6252bd9be0849c40f5865e39a29961
Author: Daniel Vetter
Date: Fri Aug 12 22:48:45 2016 +0200
drm/kms: Nuke dirty_info property
Signed-off-by: Daniel Vetter
---
Documentation/gpu/kms-properties.csv | 1 -
1 file changed, 1 deletion(-)
diff --git
Am Montag, 22. August 2016, 11:36:18 schrieb Lin Huang:
> Signed-off-by: Lin Huang
applied to my shared clock-id branch for 4.9
From: Gustavo Padovan
Instead of wrapping virtio_gpu_execbuffer() to execute the ioctl
just execute it directly.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/virtio/virtgpu_ioctl.c | 24
1 file changed, 8 insertions(+), 16
From: Gustavo Padovan
virtio fences were created with no fence context, which would make then
clash with an allocated fence context.
Signed-off-by: Gustavo Padovan
---
drivers/gpu/drm/virtio/virtgpu_drv.h | 1 +
drivers/gpu/drm/virtio/virtgpu_fence.c | 2 +-
On Wed, Aug 31, 2016 at 05:40:02PM +0200, Maxime Ripard wrote:
> On Tue, Aug 30, 2016 at 11:51:26PM +0800, Chen-Yu Tsai wrote:
> > On Tue, Aug 30, 2016 at 8:56 PM, Maxime Ripard
> > wrote:
> > > Hi,
> > >
> > > On Tue, Aug 30, 2016 at 08:22:23PM +0800, Chen-Yu Tsai wrote:
> > >> The KMS helpers
ceiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/5ddc8ee3/attachment-0001.html>
was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/05fc9ca6/attachment.sig>
nux and Kernel engineering
http://free-electrons.com
-- next part --
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/39904c8d/attachment.sig>
Hi Dave,
More -misc stuff
- moar drm_crtc.c split up
- some fixes for the simple kms helpers (Andrea)
- I included all the dri1 patches from David - we're not removing any code
or drivers, and it seems to have worked as a wake-up call to motivate a
few more people to upstream kms conversions
Hi Laurent,
On 8/31/2016 9:23 PM, Laurent Pinchart wrote:
> Hi Archit,
>
> Thank you for the patch.
>
> On Wednesday 31 Aug 2016 16:22:09 Archit Taneja wrote:
>> ADV7533 requires supply to the AVDD, V1P2 and V3P3 pins for proper
>> functionality.
>>
>> Initialize and enable the regulators during
attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/5e21ed01/attachment-0001.html>
Remove double gamma table write in omap_crtc_atomic_flush().
Fixes commit 492a426a2fc53
("drm/omapdrm: Implement gamma_lut atomic crtc properties")
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/omapdrm/omap_crtc.c | 13 -
1 file changed, 13 deletions(-)
diff --git
Hi Dave,
Fixes for 4.8:
- 2 CI S4 fixes
- error handling fix
I have additional features for 4.9, but I'll be out of
the office next week, so I probably won't get to send them out
until the following week.
The following changes since commit 279cf3f23870f7eb8ca071115e06d3d5ca0a2b9e:
process of acquiring one.
James
-- next part --
A non-text attachment was scrubbed...
Name: Xorg.0.log
Type: text/x-log
Size: 31792 bytes
Desc: not available
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/9456e526/attachment-0001.bin>
On 08/31/16 21:04, Tony Lindgren wrote:
> * Jyri Sarha [160831 06:19]:
>> ARM: dts: am335x-boneblack: Add blue-and-red-wiring -property to LCDC
>> node
>> ARM: dts: am335x-evm: Add blue-and-red-wiring -property to lcdc node
>> ARM: dts: am335x-evmsk: Whitespace cleanup of lcdc related
From: Gustavo Padovan
Hi,
Currently the Linux Kernel only have an implicit fencing mechanism where the
fence are attached directly to buffers and userspace is unaware of the inner
kernel workings. However by enabling explicit fencing, where fences travels
all
1 - 100 of 126 matches
Mail list logo