On 17 October 2017 at 15:56, Andrzej Hajda wrote:
> On 16.10.2017 16:21, Alex Deucher wrote:
>> On Mon, Oct 16, 2017 at 5:24 AM, Daniel Vetter wrote:
>>> On Mon, Oct 16, 2017 at 04:50:16PM +1000, Dave Airlie wrote:
On 16 October 2017 at 16:41, Thierry
On 16.10.2017 16:21, Alex Deucher wrote:
> On Mon, Oct 16, 2017 at 5:24 AM, Daniel Vetter wrote:
>> On Mon, Oct 16, 2017 at 04:50:16PM +1000, Dave Airlie wrote:
>>> On 16 October 2017 at 16:41, Thierry Reding
>>> wrote:
On Mon, Oct 16, 2017 at
Commit 669c9215afea ("drm/atomic: Make async plane update checks work as
intended, v2.") forced planes to always be tracked, but forgot to
explicitly get the crtc commit from the new crtc when available.
This broke plane commit tracking, and caused kms_atomic_transitions
to randomly fail with
On Tue, Oct 17, 2017 at 12:23 PM, Chen-Yu Tsai wrote:
> Hi,
>
> Here's another bunch of cleanups for sun4i-drm. Most of these were
> found while working on A10/A20 DRM and HDMI support. To be clear,
> nothing was broken before these patches.
>
> Changes since v1:
>
> - Expanded
The backend has various clocks and reset controls that need to be
enabled and deasserted before register access is possible.
Move the creation of the regmap to after the clocks and reset controls
have been configured where it makes more sense.
Signed-off-by: Chen-Yu Tsai
---
Hi,
Here's another bunch of cleanups for sun4i-drm. Most of these were
found while working on A10/A20 DRM and HDMI support. To be clear,
nothing was broken before these patches.
Changes since v1:
- Expanded commit message for patch 5 explaining the details of
memory address difference,
While debugging inverted color from the HDMI output on the A10, I
found that the lowest 3 bits were set. These were cleared on A20
boards that had normal display output. By manually toggling these
bits the mapping of the color components to these bits was found.
While these are not used anywhere,
Initially we configured the PAD_CTRL1 register at probe/bind time.
However it seems the HDMI controller will modify some of the bits
in this register by itself. On the A10 it is particularly annoying
as it toggles the output invert bits, which inverts the colors on
the display output.
The U-boot
The display backend, as well as other peripherals that have a DRAM
clock gate and access DRAM directly, bypassing the system bus,
address the DRAM starting from 0x0, while physical addresses the
system uses starts from 0x4000 (or 0x2000 in A80's case).
This issue was witnessed on the
Many of the backend's layer configuration registers have undefined
default values. This poses a risk as we use regmap_update_bits in
some places, and don't overwrite the whole register.
At probe/bind time we explicitly clear all the control registers
by writing 0 to them. This patch adds a more
Commit 4636ce93d5b2 ("drm/fb-cma-helper: Add drm_fb_cma_get_gem_addr()")
adds a new helper, which covers fetching a drm_framebuffer's GEM object
and calculating the buffer address for a given plane.
This patch uses this helper to replace our own open coded version of the
same function.
Even though the components framework can handle duplicate entries,
the extra entries cause a lot more debug messages to be generated,
which would be confusing to developers not familiar with our driver
and the framework in general.
Instead, we can scan the relatively small queue and check if the
On Tue, Oct 17, 2017 at 4:15 AM, Maxime Ripard
wrote:
> On Mon, Oct 16, 2017 at 04:20:32PM +0800, Chen-Yu Tsai wrote:
>> > On Sat, Oct 14, 2017 at 12:02:50PM +0800, Chen-Yu Tsai wrote:
>> >> The display backend, as well as other peripherals that have a DRAM
>> >>
Bjorn Helgaas writes:
> The default VGA device is normally set in vga_arbiter_add_pci_device() when
> we call it for the first enabled device that can be accessed with the
> legacy VGA resources ([mem 0xa-0xb], etc.)
>
> That default device can be overridden by an
On 2017年10月09日 16:06, Sandy Huang wrote:
Some Rockchip CRTCs, like rv1108, can directly output parallel and
serial RGB data to panel or conversion chip, so we add this driver to
probe encoder and connector.
Signed-off-by: Sandy Huang
---
Changes in v3:
update for
https://bugs.freedesktop.org/show_bug.cgi?id=103130
--- Comment #5 from Adam ---
I upgraded to the offending repo. I attempted again with wine log -all. I get:
mesa: for the -simplifycfg-sink-common option: may only occur zero or one
times!
/bin/sh: line 1: 4553
On 10/15/2017 11:47 PM, Thierry Reding wrote:
On Mon, Oct 16, 2017 at 02:29:09PM +1000, Dave Airlie wrote:
From: Dave Airlie
This uses the EDID info from my HTC Vive to mark it as
non-standard.
Signed-off-by: Dave Airlie
---
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: 43dd6fde5df450938568885249b836eb376e2ad6
commit: f4ef395e89a5352d31d2381dc06ff52fa5893c2d [160/1021] ASoC: AMD: enable
ACP3x drivers build
config: arm-allmodconfig (attached as .config)
compiler:
Hi,
On Mon, Oct 16, 2017 at 06:06:37PM +0800, Jeffy Chen wrote:
> When the pwm driver is unbound, the pwm_bl driver would still hold a
> reference to that pwm, and crash the kernel later(if someone trying
> to access that invalid pwm).
This is not the primary problem you're trying to address
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #10 from Harry Wentland ---
Alex is correct about the intention of this change. I've never played around
with the modeline before so don't fully understand the impact of having that in
the xorg.conf. It
On Mon, Oct 16, 2017 at 6:00 PM, Jordan Crouse wrote:
> On Mon, Oct 16, 2017 at 11:27:47AM -0400, Rob Clark wrote:
>> Previously, in an effort to defer initializing the gpu until firmware
>> was available (ie. rootfs mounted), the gpu was not loaded at when the
>>
On Wed, Oct 11, 2017 at 6:23 AM, Lothar Waßmann
wrote:
> The Ka-Ro electronics MB7 baseboard has an on-board LCD->LVDS
> converter that requires a fixed pixelclk polarity, no matter what the
> panel's display_mode specifies. Add an option to override the pixelclk
>
On 10/10/2017 02:11 AM, Mark Brown wrote:
> On Mon, Oct 09, 2017 at 05:10:37PM -0700, Laura Abbott wrote:
>> On 10/09/2017 03:08 PM, Mark Brown wrote:
>>> On Mon, Oct 09, 2017 at 02:25:47PM -0700, Laura Abbott wrote:
>
Anyway, to move this forward I think we need to see a proof of concept
On Mon, Oct 16, 2017 at 11:27:47AM -0400, Rob Clark wrote:
> Previously, in an effort to defer initializing the gpu until firmware
> was available (ie. rootfs mounted), the gpu was not loaded at when the
> subdevice was bound. Which resulted that clks/etc were requested in a
> place that devm
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #9 from Alex Deucher ---
(In reply to dwagner from comment #8)
> (In reply to Alex Deucher from comment #7)
> > I think it blocks modes that require 6Ghz timings if the platform isn't
> > validated for them.
>
Sean Paul writes:
> nit: space before ,
Thanks.
>> +/* Clone the lessor file to create a new file for us */
>> +DRM_DEBUG_LEASE("Allocating lease file\n");
>> +path_get(_file->f_path);
>
> Please forgive the stupid question, but where is this reference given
Hi Harsha,
[auto build test WARNING on v4.14-rc3]
[cannot apply to drm/drm-next next-20171013]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Mon, 16 Oct 2017 20:49:11 +0530
Sumit Semwal wrote:
> I suspect it should be ok; please do feel free to add my
> Acked-by: Sumit Semwal
> if you wish :)
Done. Thanks!
-- Steve
___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #8 from dwagner ---
(In reply to Alex Deucher from comment #7)
> I think it blocks modes that require 6Ghz timings if the platform isn't
> validated for them.
What does "platform isn't validated for 6Ghz
Hi Harsha,
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.14-rc5 next-20171013]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Mon, Oct 16, 2017 at 01:42:46PM -0700, Keith Packard wrote:
> Sean Paul writes:
>
>
> > With these nits fixed,
> > Reviewed-by: Sean Paul
>
> Like this?
>
Perfect, thanks!
Sean
> From 0aa52dd5a0873831c79c14942075354c041e5bed Mon Sep 17
On Thu, Oct 12, 2017 at 06:56:31PM -0700, Keith Packard wrote:
> drm_mode_create_lease
>
> Creates a lease for a list of drm mode objects, returning an
> fd for the new drm_master and a 64-bit identifier for the lessee
>
> drm_mode_list_lesees
>
> List the identifiers of the
On Fri, Oct 13, 2017 at 5:03 PM, Frank Rowand wrote:
> Hi Rob,
>
> On 10/02/17 20:53, frowand.l...@gmail.com wrote:
>> From: Frank Rowand
>>
>> I have found the device tree overlay code to be difficult to read and
>> maintain. This patch series
On Tue, Oct 10, 2017 at 8:02 PM, wrote:
> From: Frank Rowand
>
> Move more code into of_overlay_apply() so that it does not have
> to be duplicated by each caller of of_overlay_apply().
>
> The test in of_resolve_phandles() that the overlay tree is
Sean Paul writes:
> With these nits fixed,
> Reviewed-by: Sean Paul
Like this?
From 0aa52dd5a0873831c79c14942075354c041e5bed Mon Sep 17 00:00:00 2001
From: Keith Packard
Date: Mon, 16 Oct 2017 13:41:20 -0700
Subject: [PATCH]
On Thu, Oct 12, 2017 at 06:56:30PM -0700, Keith Packard wrote:
> Attempts to modify un-leased objects are rejected with an error.
> Information returned about unleased objects is modified to make them
> appear unusable and/or disconnected.
>
> Changes for v2 as suggested by Daniel Vetter
On Mon, Oct 16, 2017 at 04:20:32PM +0800, Chen-Yu Tsai wrote:
> > On Sat, Oct 14, 2017 at 12:02:50PM +0800, Chen-Yu Tsai wrote:
> >> The display backend, as well as other peripherals that have a DRAM
> >> clock gate and access DRAM directly, bypassing the system bus,
> >> address the DRAM starting
Hi Harsha,
[auto build test ERROR on v4.14-rc3]
[cannot apply to drm/drm-next next-20171013]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Thu, Oct 12, 2017 at 06:56:29PM -0700, Keith Packard wrote:
> This provides new data structures to hold "lease" information about
> drm mode setting objects, and provides for creating new drm_masters
> which have access to a subset of the available drm resources.
>
> An 'owner' is a drm_master
On Thu, Oct 12, 2017 at 06:56:28PM -0700, Keith Packard wrote:
> Separate out lease debugging from the core.
>
> Signed-off-by: Keith Packard
Reviewed-by: Sean Paul
> ---
> drivers/gpu/drm/drm_drv.c | 3 ++-
> include/drm/drmP.h| 4
> 2
On Thu, Oct 12, 2017 at 06:56:27PM -0700, Keith Packard wrote:
> From: Dave Airlie
>
> In order to implement plane leasing we need to count things,
> just make the code consistent with the counting code currently
> used for counting crtcs/encoders/connectors and drop the need
https://bugs.freedesktop.org/show_bug.cgi?id=103300
--- Comment #1 from Ian Bruene ---
Created attachment 134871
--> https://bugs.freedesktop.org/attachment.cgi?id=134871=edit
What should be
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=103300
Bug ID: 103300
Summary: Tear rendering bug in Bioshock Infinite
Product: Mesa
Version: 17.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Sun, Oct 15, 2017 at 01:58:23AM +0530, Harsha Sharma wrote:
> Replace use of list_for_each with list_for_each_entry to simplify the
> code and remove variables that are used only in list_for_each.
> Done with following coccinelle patch:
>
> @r@
> identifier fn,i,f,p;
> expression e;
> iterator
On Mon, Oct 16, 2017 at 2:53 PM, Harsha Sharma
wrote:
> On Tue, Oct 17, 2017 at 12:15 AM, Sean Paul wrote:
>> On Sat, Oct 14, 2017 at 2:36 PM, Harsha Sharma
>> wrote:
>>> Replace instances of
On Wed, Sep 20, 2017 at 12:01:05PM -0700, Sean Paul wrote:
> On Wed, Sep 20, 2017 at 11:54 AM, Haneen Mohammed
> wrote:
> > This patch replace instances of drm_gem_object_reference/unreference with
> > *_get/put() suffixes, because get/put is shorter and consistent with
On Wed, Sep 20, 2017 at 12:01:39PM -0700, Sean Paul wrote:
> On Wed, Sep 20, 2017 at 11:57 AM, Haneen Mohammed
> wrote:
> > This patch replace instances of drm_framebuffer_reference/unreference with
> > *_get/put() suffixes, because get/put is shorter and consistent with
On Sat, Oct 14, 2017 at 2:36 PM, Harsha Sharma
wrote:
> Replace instances of drm_framebuffer_reference/unreference() with
> *_get/put() suffixes and drm_dev_unref with *_put() suffix
> because get/put is shorter and consistent with the
> kernel use of *_get/put
On Fri, Oct 13, 2017 at 7:25 PM, Rob Clark wrote:
> On Fri, Oct 13, 2017 at 4:25 PM, Sean Paul wrote:
>> On Fri, Oct 13, 2017 at 04:11:43PM +0530, Meghana Madhyastha wrote:
>>> Rename tinydrm_of_find_backlight to backlight_get and move it
>>> to
https://bugzilla.kernel.org/show_bug.cgi?id=79011
mirh (m...@protonmail.ch) changed:
What|Removed |Added
CC||m...@protonmail.ch
---
On Fri, Oct 13, 2017 at 6:42 PM, Noralf Trønnes wrote:
>
> Den 13.10.2017 22.25, skrev Sean Paul:
>>
>> On Fri, Oct 13, 2017 at 04:11:43PM +0530, Meghana Madhyastha wrote:
>>>
>>> Rename tinydrm_of_find_backlight to backlight_get and move it
>>> to linux/backlight.c so that it
Daniel Vetter writes:
> A bit lacking time to do an in-depth review, but all my major concerns
> seem to be addressed. On the series.
Thanks much.
I sent out a note over the weekend about how we can make the Vulkan API
work without the permissions change in the kernel. We need
From: Ville Syrjälä
Allow the user to override the default configuration set by setcrtc
for the primary plane. On some hardware primary planes can be freely
positioned/sized, and it'd be nice if we can actually test that feature.
Signed-off-by: Ville Syrjälä
https://bugs.freedesktop.org/show_bug.cgi?id=98981
--- Comment #6 from Elizabeth ---
Hello everybody,
Any update at this? According to
https://intel-gfx-ci.01.org/tree/drm-tip/fi-ivb-3520m.html and
https://intel-gfx-ci.01.org/tree/drm-tip/fi-ivb-3770.html
https://bugs.freedesktop.org/show_bug.cgi?id=96620
--- Comment #3 from Elizabeth ---
(In reply to Jani Nikula from comment #2)
> (In reply to Mike Frysinger from comment #1)
> > Created attachment 124646 [details] [review] [review]
> > fix
>
> Care to post
4.13-stable review patch. If anyone has any objections, please let me know.
--
From: Ville Syrjälä
commit 7b50f7b24cd6c98541f1af53bddc5b6e861ee8c8 upstream.
intel_crtc->config->cpu_transcoder isn't yet filled out when
intel_crtc_mode_get() gets
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ville Syrjälä
commit 7b50f7b24cd6c98541f1af53bddc5b6e861ee8c8 upstream.
intel_crtc->config->cpu_transcoder isn't yet filled out when
intel_crtc_mode_get() gets
https://bugs.freedesktop.org/show_bug.cgi?id=103297
Bug ID: 103297
Summary: Rendering issue in cemu BOTW game for pre gcn hardware
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
On Mon, Oct 16, 2017 at 3:48 AM, Christian König
wrote:
> Am 16.10.2017 um 04:29 schrieb Jérémy Lefaure:
>>
>> Using the ARRAY_SIZE macro improves the readability of the code.
>>
>> Found with Coccinelle with the following semantic patch:
>> @r depends on (org ||
On Mon, Oct 16, 2017 at 05:28:27PM +0200, Maarten Lankhorst wrote:
> Op 16-10-17 om 16:48 schreef Ville Syrjälä:
> > On Mon, Oct 16, 2017 at 03:59:38PM +0200, Maarten Lankhorst wrote:
> >> Op 16-10-17 om 15:42 schreef Ville Syrjälä:
> >>> On Mon, Oct 16, 2017 at 03:29:27PM +0200, Maarten Lankhorst
https://bugs.freedesktop.org/show_bug.cgi?id=103276
--- Comment #2 from Giovanni ongaro ---
i am using mea devel 17.3
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=103276
--- Comment #1 from Giovanni ongaro ---
UPDATE: The situation is as follows
if i start gnome in root or normal user RX480 accel is enable and vega not
(error Mesa_drm:image_required in glamor
if i start with
When firmware was added to linux-firmware, it was put in a qcom sub-
directory, unlike what we'd been using before. For a300_pfp.fw and
a300_pm4.fw symlinks were created, but we'd prefer not to have to do
this in the future. So add support to look in both places when
loading firmware.
Previously, in an effort to defer initializing the gpu until firmware
was available (ie. rootfs mounted), the gpu was not loaded at when the
subdevice was bound. Which resulted that clks/etc were requested in a
place that devm couldn't really help unwind if something failed.
Instead move
Prep work for the next patch.
Signed-off-by: Rob Clark
---
drivers/gpu/drm/msm/adreno/a5xx_gpu.c | 11 ++-
drivers/gpu/drm/msm/adreno/a5xx_power.c | 3 ++-
drivers/gpu/drm/msm/adreno/adreno_gpu.c | 35 ++---
Op 16-10-17 om 16:48 schreef Ville Syrjälä:
> On Mon, Oct 16, 2017 at 03:59:38PM +0200, Maarten Lankhorst wrote:
>> Op 16-10-17 om 15:42 schreef Ville Syrjälä:
>>> On Mon, Oct 16, 2017 at 03:29:27PM +0200, Maarten Lankhorst wrote:
Commit 669c9215afea ("drm/atomic: Make async plane update
Hi Steven,
On 16 October 2017 at 20:07, Steven Rostedt wrote:
> On Mon, 16 Oct 2017 11:15:45 +0200
> Daniel Vetter wrote:
>
>> On Fri, Oct 13, 2017 at 05:27:59PM +0200, Christian König wrote:
>> > Am 13.10.2017 um 16:06 schrieb Steven Rostedt:
>> > > From:
On Mon, Oct 16, 2017 at 03:59:38PM +0200, Maarten Lankhorst wrote:
> Op 16-10-17 om 15:42 schreef Ville Syrjälä:
> > On Mon, Oct 16, 2017 at 03:29:27PM +0200, Maarten Lankhorst wrote:
> >> Commit 669c9215afea ("drm/atomic: Make async plane update checks work as
> >> intended, v2.") forced planes
On Mon, 16 Oct 2017 11:15:45 +0200
Daniel Vetter wrote:
> On Fri, Oct 13, 2017 at 05:27:59PM +0200, Christian König wrote:
> > Am 13.10.2017 um 16:06 schrieb Steven Rostedt:
> > > From: Steven Rostedt (VMware)
> > >
> > > Commit e941759c74 ("fence:
On Mon, Oct 16, 2017 at 5:24 AM, Daniel Vetter wrote:
> On Mon, Oct 16, 2017 at 04:50:16PM +1000, Dave Airlie wrote:
>> On 16 October 2017 at 16:41, Thierry Reding wrote:
>> > On Mon, Oct 16, 2017 at 02:29:07PM +1000, Dave Airlie wrote:
>> >> From: Dave
https://bugs.freedesktop.org/show_bug.cgi?id=100443
taij...@posteo.de changed:
What|Removed |Added
Attachment #134553|0 |1
is obsolete|
Op 16-10-17 om 15:42 schreef Ville Syrjälä:
> On Mon, Oct 16, 2017 at 03:29:27PM +0200, Maarten Lankhorst wrote:
>> Commit 669c9215afea ("drm/atomic: Make async plane update checks work as
>> intended, v2.") forced planes to always be tracked, but forgot to
>> explicitly get the crtc commit from
On Mon, Oct 16, 2017 at 03:29:28PM +0200, Maarten Lankhorst wrote:
> We still want to fail with -EBUSY if a plane or connector is part of
> a commit, even if it will be assigned to a new commit.
>
> This closes a small hole left open where we should return -EBUSY.
> It's not severe, because
On Mon, Oct 16, 2017 at 03:29:27PM +0200, Maarten Lankhorst wrote:
> Commit 669c9215afea ("drm/atomic: Make async plane update checks work as
> intended, v2.") forced planes to always be tracked, but forgot to
> explicitly get the crtc commit from the new crtc when available.
>
> This broke plane
https://bugs.freedesktop.org/show_bug.cgi?id=102820
--- Comment #7 from Alex Deucher ---
I think it blocks modes that require 6Ghz timings if the platform isn't
validated for them. Does everything work correctly if you remove the modes
from your monitor section?
--
You
We still want to fail with -EBUSY if a plane or connector is part of
a commit, even if it will be assigned to a new commit.
This closes a small hole left open where we should return -EBUSY.
It's not severe, because wait_for_dependencies and swap_state helpers
still block. But it should return
Commit 669c9215afea ("drm/atomic: Make async plane update checks work as
intended, v2.") forced planes to always be tracked, but forgot to
explicitly get the crtc commit from the new crtc when available.
This broke plane commit tracking, and caused kms_atomic_transitions
to randomly fail with
On Thu, 5 Oct 2017 13:29:17 +0200
Boris Brezillon wrote:
> drm_gem_cma_create() prints an error message when dma_alloc_wc() fails to
> allocate the amount of memory we requested. This can lead to annoying
> error messages when CMA is only one possible source
https://bugs.freedesktop.org/show_bug.cgi?id=92755
--- Comment #6 from Julien Isorce ---
(In reply to vitor.hda from comment #5)
> similar problem in R9 280X, I have the "ring 0/3 stalled
Was it with the attached apitrace ? Otherwise could you generate one (apitrace
On Wed, Sep 13, 2017 at 2:08 AM, Laurent Pinchart
wrote:
>> -- compatible: Must be "ti,ths8135"
>> +- compatible: Must be one of
>> + "ti,ths8134a"
>> + "ti,ths8134b"
>> + "ti,ths8135"
>
> As mentioned in the review of patch 2/2, would it make sense to also
https://bugs.freedesktop.org/show_bug.cgi?id=101905
Chris Wilson changed:
What|Removed |Added
Status|NEW |RESOLVED
Hi Fabrizio,
Thank you for the patch.
On Friday, 13 October 2017 18:22:22 EEST Fabrizio Castro wrote:
> Add support for the R8A7745 DU (which is very similar to the R8A7794 DU);
> it has 2 RGB outputs.
>
> Signed-off-by: Fabrizio Castro
> Reviewed-by: Biju Das
Hi Fabrizio,
Thank you for the patch.
On Friday, 13 October 2017 18:22:20 EEST Fabrizio Castro wrote:
> Add support for the R8A7743 DU (which is very similar to the R8A7791 DU);
> it has 1 DPAD (RGB) output and 1 LVDS output.
>
> Signed-off-by: Fabrizio Castro
>
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in:
drivers/gpu/drm/i915/i915_gem.c
between commit:
b85577b72837e ("drm/i915: Order two completing nop_submit_request")
from the drm-intel-fixes tree and commit:
5d031f4e1618b ("drm/i915: Stop asserting on set-wedged
https://bugs.freedesktop.org/show_bug.cgi?id=102457
Marta Löfstedt changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
https://bugs.freedesktop.org/show_bug.cgi?id=102457
Marta Löfstedt changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Hi Sebastian,
On Monday, 16 October 2017 13:27:57 EEST Sebastian Reichel wrote:
> Hi,
>
> On Fri, Oct 13, 2017 at 05:59:27PM +0300, Laurent Pinchart wrote:
> > The omap_hdmi private data structure is currently stored as a global
> > variable. While no platform with multiple HDMI4 encoders
The etnaviv driver causes a link failure if it is built-in but THERMAL
is built as a module:
drivers/gpu/drm/etnaviv/etnaviv_gpu.o: In function `etnaviv_gpu_bind':
etnaviv_gpu.c:(.text+0x4c4): undefined reference to
`thermal_of_cooling_device_register'
etnaviv_gpu.c:(.text+0x600): undefined
On 16.10.2017 12:06, Jeffy Chen wrote:
> From: Tomasz Figa
>
> The driver that instantiates the bridge should own the drvdata, as all
> driver model callbacks (probe, remove, shutdown, PM ops, etc.) are also
> owned by its driver struct. Moreover, storing two different pointer
Hi,
On Fri, Oct 13, 2017 at 05:59:27PM +0300, Laurent Pinchart wrote:
> The omap_hdmi private data structure is currently stored as a global
> variable. While no platform with multiple HDMI4 encoders currently
> exists nor is planned, this doesn't comply with the kernel device model
> and should
Hi,
On Fri, Oct 13, 2017 at 05:59:27PM +0300, Laurent Pinchart wrote:
> The omap_hdmi private data structure is currently stored as a global
> variable. While no platform with multiple HDMI4 encoders currently
> exists nor is planned, this doesn't comply with the kernel device model
> and should
Since we are trying to access components' resources in the master's
suspend/resume PM callbacks(e.g. panel), add device links to correct
the suspend/resume and shutdown ordering.
Signed-off-by: Jeffy Chen
---
Changes in v2:
Use device link to correct the
When the pwm driver is unbound, the pwm_bl driver would still hold a
reference to that pwm, and crash the kernel later(if someone trying
to access that invalid pwm).
Add a device link to avoid this.
Signed-off-by: Jeffy Chen
---
Changes in v2: None
Add missing error handling in rockchip_dp_bind().
Fixes: 9e32e16e9e98 ("drm: rockchip: dp: add rockchip platform dp driver")
Signed-off-by: Jeffy Chen
---
Changes in v2: None
drivers/gpu/drm/rockchip/analogix_dp-rockchip.c | 14 --
1 file changed, 12
From: Tomasz Figa
The driver that instantiates the bridge should own the drvdata, as all
driver model callbacks (probe, remove, shutdown, PM ops, etc.) are also
owned by its driver struct. Moreover, storing two different pointer
types in driver data depending on driver
Make edp display works on chromebook kevin(at least for boot animation).
Also solve some issues i meet during the bringup.
Changes in v2:
Use device link to correct the suspend/resume and shutdown ordering,
instead of converting rockchip spi's suspend/resume PM callbacks to
late suspend/resume
On Mon, 16 Oct 2017, Dave Airlie wrote:
> From: Dave Airlie
>
> This adds the infrastructure needed to quirk displays
> using edid and to mark them a non-standard.
>
> A non-standard display is one which doesn't work like
> a normal rectangular monitor or
2017년 09월 29일 19:05에 Andrzej Hajda 이(가) 쓴 글:
> mixer_resources adds only unnecessary redirection, removing it makes the
> code shorter and cleaner.
>
> Signed-off-by: Andrzej Hajda
> Reviewed-by: Tobias Jakobi
> ---
>
Make edp display works on chromebook kevin(at least for boot animation).
Also solve some issues i meet during the bringup.
Jeffy Chen (4):
arm64: dts: rockchip: Enable edp disaplay on kevin
backlight: pwm_bl: Add device link for pwm_bl and pwm
drm/rockchip: Fix error handling path in
Hi,
On Fri, Oct 13, 2017 at 05:59:26PM +0300, Laurent Pinchart wrote:
> The DSS private data structure is currently stored as a global variable.
> While no platform with multiple DSS devices currently exists nor is
> planned, this doesn't comply with the kernel device model and should
> thus be
1 - 100 of 147 matches
Mail list logo