Hi Archit,
On Wednesday 31 Aug 2016 22:24:30 Archit Taneja wrote:
> On 8/31/2016 9:23 PM, Laurent Pinchart wrote:
> > 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
On Wed, Aug 31, 2016 at 11:05 PM, Daniel Vetter wrote:
> On Wed, Aug 31, 2016 at 10:45 PM, Haixia Shi wrote:
>> For details see https://bugs.chromium.org/p/chromium/issues/detail?id=468050
>>
>> So drm_mode_config_cleanup() is called from udl_driver_unload() in
>> which we found there's still a f
On Wed, Aug 31, 2016 at 10:45 PM, Haixia Shi wrote:
> For details see https://bugs.chromium.org/p/chromium/issues/detail?id=468050
>
> So drm_mode_config_cleanup() is called from udl_driver_unload() in
> which we found there's still a framebuffer left, hence the WARN in
> drm_crtc.c:5495. This als
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 p
On 08/31/16 22:06, Roland Singer wrote:
> Here is Peter Wu's reply, which was not send to the mailing list, because
> I had to resend my e-mail to him due to a failure...
>
>
> Forwarded Message
> Subject: Re: Fwd: Re: Kernel Freeze with American Megatrends BIOS
> Date: Wed, 31
Here is Peter Wu's reply, which was not send to the mailing list, because
I had to resend my e-mail to him due to a failure...
Forwarded Message
Subject: Re: Fwd: Re: Kernel Freeze with American Megatrends BIOS
Date: Wed, 31 Aug 2016 18:08:53 +0200
From: Peter Wu
To: Roland Sin
Hi
Em Qua, 2016-08-31 Ã s 14:43 -0700, James Bottomley escreveu:
> On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote:
> >
> > On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote:
> > >
> > > We seem to have an xrandr regression with skylake now.  What's
> > > happening is that I ca
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 no
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 a/drivers/gpu/drm/
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
+++ b/tests/mod
Hi Maxime,
On Tue, Aug 30, 2016 at 11:51 PM, 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 (drm_atomic_helper_check_modeset/mode_fixup) pass
>>> encoder->bridge directly
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 s
Hi Dave,
More -misc stuff
- moar drm_crtc.c split up&documentation
- 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
ed 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/39904c8d/attachment.sig>
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/05fc9ca6/attachment.sig>
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 (d
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 V
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
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 a/Document
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 +
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 --
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
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 too
Big thing is untangling and carefully documenting the different uapi
types of planes. I also sprinkled a few more cross references around
to make this easier to discover.
As usual, remove the kerneldoc for internal functions which are not
exported. Aside: We should probably go OCD on all the ioctl
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: Danie
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 +++
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 ++
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
include/drm/drm_enco
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 and
;
> >> + 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>
attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/5e21ed01/attachment-0001.html>
re 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/5ddc8ee3/attachment-0001.html>
On Wed, Aug 31, 2016 at 4:18 PM, Maxime Ripard
wrote:
> 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-b
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
---
drivers/gpu/
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 a/arch/arm/boot/dts/
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.
Sig
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 wir
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 but
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 BGR
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 LCDC
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 1
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
The following changes since commit 969af80f770a86e65bf8be1f72b218b5f8556b56:
Merge tag 'drm-intel-fixes-2016-08-25' of
git://anongit.freedesktop.org/drm-intel into drm-fixes (2016-08-26
05:18:40 +1000)
are available in the git repository at:
git://people.freedesktop.org/~robclark/linux msm-f
On Wed, 2016-08-31 at 21:51 +, Zanoni, Paulo R wrote:
> Hi
>
> Em Qua, 2016-08-31 Ã s 14:43 -0700, James Bottomley escreveu:
> > On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote:
> > >
> > > On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote:
> > > >
> > > > We seem to have an
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
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 Ki
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 | 63
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 +
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
drivers/
>>
>> Thanks. Right now I am overriding the DSDT, but I am not able to override
>> the SSDT, because I have to fix and compile all the SSDT files. There
>> are too many compile errors... Wanted to find the exact line which
>> is responsible for the hickup.
>
> Have you disassembled with externs in
Hi Jyri,
Jyri Sarha writes:
> On 08/23/16 15:56, Karl Beldan wrote:
>> Hi,
>>
>> I found some missing bits for rev1 of the LCDC and here are some of the
>> changes I am using to use the DRM driver on an LCDCK (which has a rev1).
>> 1/3 seems required by rev1 of the IP and without it my the LCDC
From: Gustavo Padovan
Support DRM out-fences creating a sync_file with a fence for each crtc
update with the DRM_MODE_ATOMIC_OUT_FENCE flag.
We then send an struct drm_out_fences array with the out-fences fds back in
the drm_atomic_ioctl() as an out arg in the out_fences_ptr field.
struct drm_o
From: Gustavo Padovan
Create one timeline context for each CRTC to be able to handle out-fences
and signal them. It adds a few members to struct drm_crtc: fence_context,
where we store the context we get from fence_context_alloc(), the
fence seqno and the fence lock, that we pass in fence_init()
From: Gustavo Padovan
There is now a new property called FENCE_FD attached to every plane
state that receives the sync_file fd from userspace via the atomic commit
IOCTL.
The fd is then translated to a fence (that may be a fence_collection
subclass or just a normal fence) and then used by DRM to
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 the way up the userspace we can prov
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/staging/media/s5p-cec/s5p_cec.c | 17 ++---
1 file changed, 2 insertions(+), 15 deletions(-)
diff --git
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_rotator.c | 26 ++
1 file changed, 2 insertions(+), 24 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_gsc.c | 29 ++---
1 file changed, 2 insertions(+), 27 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_fimc.c | 29 ++---
1 file changed, 2 insertions(+), 27 deletions(-
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 no
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/df3151ac/attachment.html>
ssignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/af4a97aa/attachment.html>
next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/cb11b372/attachment-0001.html>
On Wed, 2016-08-31 at 11:23 -0700, James Bottomley wrote:
> On Fri, 2016-08-26 at 09:10 -0400, James Bottomley wrote:
> > We seem to have an xrandr regression with skylake now. What's
> > happening is that I can get output on to a projector, but the
> > system is losing video when I change the xr
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:
> [+cc
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
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:
[+cc linux-acpi, linux-kernel, dri-devel]
Hi Roland,
I ha
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:
drm/nouveau
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 DRM_CONNECTOR_POLL_CONNECT or DRM_CONNECTOR_POLL_DISCONNECT with
DRM_OUTPUT_POLL_
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 y
For details see https://bugs.chromium.org/p/chromium/issues/detail?id=468050
So drm_mode_config_cleanup() is called from udl_driver_unload() in
which we found there's still a framebuffer left, hence the WARN in
drm_crtc.c:5495. This also forcefully releases all the buffers.
A bit later the actual
On Tue, Aug 09, 2016 at 10:00:03PM +0300, Jyri Sarha wrote:
> Changes since first version [1] of this series:
> - "drm/i2c: tda998x: Improve tda998x_configure_audio() audio related pdata"
> - Change audio in tda998x pdata to audio_params to match the naming in
> private data struct
> - Skip
vel/attachments/20160831/645a84bf/attachment.html>
On Tue, Aug 23, 2016 at 10:05:45AM +0200, Hans Verkuil wrote:
>
>
> On 08/23/16 09:59, Russell King - ARM Linux wrote:
> > On Tue, Aug 23, 2016 at 09:21:17AM +0200, Hans Verkuil wrote:
> >> Hi Russell,
> >>
> >> On 08/12/2016 04:15 PM, Russell King wrote:
> >>> Add a CEC driver for the dw-hdmi ha
On Tue, Aug 23, 2016 at 10:03:03AM +0200, Hans Verkuil wrote:
> Hi Russell,
>
> On 08/12/16 16:15, Russell King wrote:
> > + ret = devm_request_threaded_irq(&pdev->dev, cec->irq,
> > + dw_hdmi_cec_hardirq,
> > + dw_hdmi_cec_thre
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 you seeing something
>> that suggests it may be a PCI problem?
>
> Yes I susp
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/3e4e599c/attachment.html>
here in the 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/attac
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
> ---
> drivers/video/backlight/pwm_
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 DRM_CON
Am 30.08.2016 um 21:21 schrieb Peter Wu:
> On Tue, Aug 30, 2016 at 02:13:46PM -0400, Ilia Mirkin wrote:
>> On Tue, Aug 30, 2016 at 2:02 PM, Roland Singer
>> wrote:
>>> I configured bbswitch to not set any states automatically...
>>> So it's possible to obtain and verify the GPU power state.
>>>
>>
Am 30.08.2016 um 20:13 schrieb Ilia Mirkin:
> On Tue, Aug 30, 2016 at 2:02 PM, Roland Singer
> wrote:
>> I configured bbswitch to not set any states automatically...
>> So it's possible to obtain and verify the GPU power state.
>>
>> However I removed the bbswitch module and booted with nouveau.
>
to send pre message 201 ret is 0
[ 1962.560233]
failed to send 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>
Am 30.08.2016 um 20:09 schrieb Emil Velikov:
> I second Ilia here. Using bbswitch in conjunction with any driver (be
> that nouveau or the proprietary one) is a bad idea.
>
I removed bbswitch from my system and will use vgaswitcheroo to check
the GPU power state from now.
> (If Ilia's suggestions
* Jyri Sarha [160831 11:49]:
> 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-ev
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.
> >
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 +-
drivers/gpu/drm/virtio/virtgpu_km
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 deletions(-)
diff --git a/drivers/gpu/d
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 drive
Hi Bjorn,
On Tue, 30 Aug 2016, Bjorn Andersson wrote:
> On Tue 30 Aug 05:34 PDT 2016, Lee Jones wrote:
>
> Thanks for your review Lee.
>
> > On Fri, 26 Aug 2016, Peter Griffin wrote:
> [..]
> > > diff --git a/drivers/remoteproc/Kconfig b/drivers/remoteproc/Kconfig
> > > index 1a8bf76a..06765e0
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
have a HDMI dongle,
but I'm in the 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>
attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160831/1819c8e6/attachment.html>
* 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 nodes
> ARM: dts: am335x-evmsk: Add blue-and-r
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 ra
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
---
arch/arm/boot/dts/Makefile| 3 +-
arc
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 can be shared when things settle down.
1 - 100 of 127 matches
Mail list logo