https://bugs.freedesktop.org/show_bug.cgi?id=104655
--- Comment #5 from omin...@autistici.org ---
I have installed Ubuntu 16.04 so I could try this with AMDGPU-PRO. The 240 Hz
distortion still occurs.
--
You are receiving this mail because:
You are the assignee for the bug.__
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on v4.15-rc8 next-20180119]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #12 from Barto (mister.free...@laposte.net) ---
Created attachment 273757
--> https://bugzilla.kernel.org/attachment.cgi?id=273757&action=edit
workaround by reverting changes made by the bad commit
I created a patch, it's a workarou
Hi Rob,
Thanks for the review.
> -Original Message-
> From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf
> Of Rob Herring
> Sent: Friday, January 19, 2018 4:31 PM
> To: Hyun Kwon
> Cc: devicet...@vger.kernel.org; Laurent Pinchart
> ; Michal Simek
> ; dri-devel@lis
Hi Rob,
Thanks for the review.
> -Original Message-
> From: Rob Herring [mailto:r...@kernel.org]
> Sent: Friday, January 19, 2018 3:33 PM
> To: Hyun Kwon
> Cc: dri-devel@lists.freedesktop.org; devicet...@vger.kernel.org; Michal
> Simek ; Daniel Vetter ;
> Laurent Pinchart
> Subject: Re:
Hi Daniel,
I love your patch! Yet something to improve:
[auto build test ERROR on drm/drm-next]
[also build test ERROR on v4.15-rc8 next-20180119]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Update i915_context_status to include priority.
Signed-off-by: Matt Roper
---
drivers/gpu/drm/i915/i915_debugfs.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_debugfs.c
b/drivers/gpu/drm/i915/i915_debugfs.c
index cc659b4b2a45..075b269ac63b 100644
--- a/drivers
Most DRM drivers will want to handle the CGROUP_SETPARAM ioctl by looking up a
driver-specific per-cgroup data structure (or allocating a new one) and storing
the supplied parameter value into the data structure (possibly after doing some
checking and sanitization on the provided value). Let's pro
Drivers that handle processes on a per-cgroup basis need to be able to lookup
the cgroup that a process belongs to.
Cc: Tejun Heo
Cc: cgro...@vger.kernel.org
Signed-off-by: Matt Roper
---
include/linux/cgroup.h | 5 -
kernel/cgroup/cgroup-internal.h | 3 ---
kernel/cgroup/cgroup.c
Cc: Tejun Heo
Cc: cgro...@vger.kernel.org
Signed-off-by: Matt Roper
---
include/drm/drm_file.h | 28
1 file changed, 28 insertions(+)
diff --git a/include/drm/drm_file.h b/include/drm/drm_file.h
index 0e0c868451a5..08855a99069c 100644
--- a/include/drm/drm_file.h
++
GPU contexts are usually created with "normal" priority as a starting point and
then may be adjusted from their either via explicit methods (context_set_param)
or implicit methods (boosts/penalization due to runtime behavior). Let's allow
a system integrator to override this starting GPU priority
Drivers may wish to access a cgroup's inode to perform permission checks on
driver-specific operations.
Cc: Tejun Heo
Cc: cgro...@vger.kernel.org
Signed-off-by: Matt Roper
---
fs/kernfs/inode.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/kernfs/inode.c b/fs/kernfs/inode.c
index a3430
cgroups are a convenient mechanism for system integrators to organize processes
into a logical hierarchy for system configuration purposes. cgroups can be
used to control resources (memory, cpu time share, etc.) or apply other types
of subsystem-specific policy (network priorty, BPF programs, etc.
Drivers may wish to limit their own cgroup operations to cgroups in the
cgroup-v2 hierarchy. Let's make this helper function usable outside the cgroup
core code.
Cc: Tejun Heo
Cc: cgro...@vger.kernel.org
Signed-off-by: Matt Roper
---
include/linux/cgroup.h | 2 ++
kernel/cgroup/cgroup
Drivers or other kernel subsystems may allow subsystem-specific policy and
configuration to be applied to cgroups. If these subsystems track private data
on a per-cgroup basis, they need a way to be notified about cgroup destruction
so that they can clean up their own internal data for that cgroup
cgroups are core kernel mechanism that allows a system integrator /
system administrator to collect OS processes into a hierarchy of groups
according to their intended role in the overall system; resource
management and policy configuration can then be applied to each cgroup
independently.
The DRM
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #11 from dwagner ---
(In reply to Peter Weber from comment #8)
> The DP of the RX 560 works fine at 3480x2180@60Hz, but via HDMI it fails
...
> HINT: Don't used "DEEP COLOR" (LG OPTION for 8/10BIT COLOR?) with HDMI or
> everything is
https://bugzilla.kernel.org/show_bug.cgi?id=198511
Barto (mister.free...@laposte.net) changed:
What|Removed |Added
Attachment #273743|0 |1
is obsolete
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #10 from Barto (mister.free...@laposte.net) ---
I think I found the real "first bad commit",
it's :
commit 648bc3574716400acc06f99915815f80d9563783
Author: Christian König
Date: Thu Jul 6 09:59:43 2017 +0200
drm/ttm: add tran
On Mon, Jan 15, 2018 at 05:57:06PM -0800, Hyun Kwon wrote:
> This add a dt binding for ZynqMP DP subsystem.
>
> Signed-off-by: Hyun Kwon
> ---
> v2
> - Group multiple ports under 'ports'
> - Replace linux specific terms with generic hardware descriptions
> ---
> ---
> .../bindings/display/xlnx/x
On Wed, Jan 17, 2018 at 09:20:28AM +0100, Daniel Vetter wrote:
> On Mon, Jan 15, 2018 at 05:57:05PM -0800, Hyun Kwon wrote:
> > Xilinx has various platforms for display, where users can create
> > using multiple IPs in the programmable FPGA fabric, or where
> > some hardened piepline is available o
On Mon, Jan 15, 2018 at 05:57:04PM -0800, Hyun Kwon wrote:
> The dt binding for Xilinx display pipeline. The pipeline can be
> composed with multiple and different types of sub-devices. This node
> is to represent the entire pipeline as a single entity.
>
> Signed-off-by: Hyun Kwon
> ---
> v2
> -
On Mon, Jan 15, 2018 at 06:21:39PM +0800, Hean-Loong, Ong wrote:
> From: Ong, Hean Loong
>
> Device tree binding for Intel FPGA Video and Image Processing Suite. The
> binding involved would be generated from the Altera (Intel) Qsys system. The
> bindings would set the max width, max height, bu
On Mon, Jan 15, 2018 at 06:21:39PM +0800, Hean-Loong, Ong wrote:
> From: Ong, Hean Loong
"dt-bindings: display: ..."
>
> Device tree binding for Intel FPGA Video and Image Processing Suite. The
> binding involved would be generated from the Altera (Intel) Qsys system. The
> bindings would set
On Sat, Jan 13, 2018 at 01:14:19AM +0200, Laurent Pinchart wrote:
> The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
> corresponding device tree bindings.
>
> Signed-off-by: Laurent Pinchart
> ---
> Changes since v1:
>
> - Move the SoC name before the IP name in compatible s
On Fri, Jan 19, 2018 at 09:42:14PM +, Pandiyan, Dhinakaran wrote:
> On Thu, 2018-01-18 at 23:26 -0800, Rodrigo Vivi wrote:
> > On Fri, Jan 12, 2018 at 09:57:07PM +, Dhinakaran Pandiyan wrote:
> > > The frame counter may have got reset between disabling and enabling vblank
> > > interrupts d
Hi Dave,
A few more fixes for 4.16, nothing major.
The following changes since commit ad8cec7df5d4bf3b1109fabbb1d61663857045ae:
drm/amd/pp: Implement get_max_high_clocks for CI/VI (2018-01-10 15:44:55
-0500)
are available in the git repository at:
git://people.freedesktop.org/~agd5f/linu
On Fri, Jan 12, 2018 at 04:30:34PM +0100, Philippe Cornu wrote:
> Add the DPI/RGB input pixel clock in mandatory properties
> because it really offers a better preciseness for timing
> computations.
> Note: Fix also the DSI panel example where "ref" & "pclk"
> clocks were swapped.
>
> Signed-off-b
On Fri, Jan 19, 2018 at 10:02:12PM +, Pandiyan, Dhinakaran wrote:
>
>
>
> On Fri, 2018-01-19 at 00:01 -0800, Rodrigo Vivi wrote:
> > On Fri, Jan 12, 2018 at 09:57:06PM +, Dhinakaran Pandiyan wrote:
> > > The HW frame counter can get reset if device enters a low power state
> > > after
>
Looks good. This change is Reviewed-by: Felix Kuehling
Regards,
Felix
On 2018-01-18 07:39 PM, Gustavo A. R. Silva wrote:
> Use ARRAY_SIZE instead of dividing sizeof array with sizeof an element.
>
> This issue was detected with the help of Coccinelle.
>
> Signed-off-by: Gustavo A. R. Silva
>
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #9 from Barto (mister.free...@laposte.net) ---
(In reply to Barto from comment #8)
> yes you are right, something went wrong with the bisect,
>
> because I revet commit cf2623d9 then the bug is still here
I meant "if I revert commit
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #8 from Barto (mister.free...@laposte.net) ---
Yes you (In reply to Alex Deucher from comment #7)
> I think something went wrong with your bisect. That commit touched a
> completely different driver that's not even loaded on your syst
On Fri, 2018-01-19 at 00:01 -0800, Rodrigo Vivi wrote:
> On Fri, Jan 12, 2018 at 09:57:06PM +, Dhinakaran Pandiyan wrote:
> > The HW frame counter can get reset if device enters a low power state after
> > vblank interrupts were disabled. This messes up any following vblank count
> > update
On Thu, 2018-01-18 at 23:26 -0800, Rodrigo Vivi wrote:
> On Fri, Jan 12, 2018 at 09:57:07PM +, Dhinakaran Pandiyan wrote:
> > The frame counter may have got reset between disabling and enabling vblank
> > interrupts due to DMC putting the hardware to DC5/6 state if PSR was
> > active. The frame
On Thu, 2018-01-18 at 23:36 -0800, Rodrigo Vivi wrote:
> On Fri, Jan 12, 2018 at 09:57:03PM +, Dhinakaran Pandiyan wrote:
> > drm_vblank_count() has a u32 type returning what is a 64-bit vblank count.
> > The effect of this is when drm_wait_vblank_ioctl() tries to widen the user
> > space reque
On Fri, Jan 12, 2018 at 02:58:50AM +0200, Laurent Pinchart wrote:
> The internal LVDS encoders now have their own DT bindings, representing
> them as part of the DU is deprecated.
>
> Signed-off-by: Laurent Pinchart
> ---
> .../devicetree/bindings/display/renesas,du.txt | 26
> +
On Fri, Jan 12, 2018 at 12:44:45PM +0200, Laurent Pinchart wrote:
> Hi Geert,
>
> On Friday, 12 January 2018 11:49:28 EET Geert Uytterhoeven wrote:
> > On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > > The internal LVDS encoders now have their own DT bindings, representing
> > > them
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #7 from Alex Deucher (alexdeuc...@gmail.com) ---
I think something went wrong with your bisect. That commit touched a
completely different driver that's not even loaded on your system.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #6 from Barto (mister.free...@laposte.net) ---
Created attachment 273743
--> https://bugzilla.kernel.org/attachment.cgi?id=273743&action=edit
bisect log
here is the bisect log
--
You are receiving this mail because:
You are watchi
https://bugzilla.kernel.org/show_bug.cgi?id=198511
--- Comment #5 from Barto (mister.free...@laposte.net) ---
I did the bisect,
the first bad commit is :
commit cf2623d951c1c52923a776e01cf2e2afc9d042a0
Author: Rex Zhu
Date: Mon Sep 4 18:11:52 2017 +0800
drm/amd/powerplay: refine powerpla
Add support for the R-Car V3M (R8A77970) SoC to the LVDS encoder driver.
Note that there are some differences with the other R-Car gen3 SoCs, e.g.
LVDPLLCR has the same layout as in the R-Car gen2 SoCs...
Signed-off-by: Sergei Shtylyov
---
drivers/gpu/drm/rcar-du/rcar_lvds.c | 21
Document the R-Car V3M (R8A77970) SoC in the R-Car LVDS bindings.
Signed-off-by: Sergei Shtylyov
---
Documentation/devicetree/bindings/display/bridge/renesas,lvds.txt |1 +
1 file changed, 1 insertion(+)
Index: linux/Documentation/devicetree/bindings/display/bridge/renesas,lvds.txt
===
Hello!
Here's the set of 3 patches against the 'drm-next' branch of David Airlie's
'linux.git' repo plus the patch fixing LVDS startup for R-Car gen2/3 and
Laurent Picnahrt's patches creating the R-Car LVDS bridge driver posted
recently. The main purpose of these patches is to add the R-Car V3M (R
After the recent corrections to the R-Car gen2/3 LVDS startup code, already
similar enough at their ends rcar_lvds_enable_gen{2|3}() started asking for
a merge and it's becoming actually necessary with the addition of the R-Car
V3M (R8A77970) support -- this gen3 SoC has gen2-like LVDPLLCR layout.
https://bugs.freedesktop.org/show_bug.cgi?id=104001
--- Comment #19 from mikhail.v.gavri...@gmail.com ---
I am sorry for misunderstanding.
Every time when I see new commits in branch I hope that this issue may be
fixed.
And every time I rebuild kernel for testing.
And after it I every time I repro
Am 19.01.2018 um 13:20 schrieb Michal Hocko:
On Fri 19-01-18 13:13:51, Michal Hocko wrote:
On Fri 19-01-18 12:37:51, Christian König wrote:
[...]
The per file descriptor badness is/was just the much easier approach to
solve the issue, because the drivers already knew which client is currently
u
On 2018-01-19 12:37 PM, Christian König wrote:
> Am 19.01.2018 um 11:40 schrieb Michal Hocko:
>> On Fri 19-01-18 09:39:03, Christian König wrote:
>>> Am 19.01.2018 um 09:20 schrieb Michal Hocko:
>> [...]
OK, in that case I would propose a different approach. We already
have rss_stat. So w
https://bugs.freedesktop.org/show_bug.cgi?id=104412
--- Comment #10 from S.H. ---
(In reply to Peter Weber from comment #8)
> Hello!
>
> I'm using a LG 27UD88-W, which featurese 1 x DP, 1 x USB-C (DP) and 2 x
> HDMI. In my desktop is a Radeon RX 560 which offers DP "1.4" and HDMI "2.0b"
> and I
Hi Laurent,
On Wed, Jan 17, 2018 at 11:55:30PM +0200, Laurent Pinchart wrote:
> The plane cleanup handler currently calls drm_plane_helper_disable(),
> which is a legacy helper function. Replace it with a call to
> drm_atomic_helper_shutdown() at removal time.
>
> Signed-off-by: Laurent Pinchart
https://bugs.freedesktop.org/show_bug.cgi?id=104216
--- Comment #11 from Germano Massullo ---
Disabling Firefox hardware acceleration seems to work as bug workaround
https://support.mozilla.org/en-US/kb/upgrade-graphics-drivers-use-hardware-acceleration#w_turning-off-hardware-acceleration
--
Yo
From: Sricharan R
Finally add the device link between the master device and
smmu, so that the smmu gets runtime enabled/disabled only when the
master needs it. This is done from add_device callback which gets
called once when the master is added to the smmu.
Signed-off-by: Sricharan R
---
driv
This series provides the support for turning on the arm-smmu's
clocks/power domains using runtime pm. This is done using the
recently introduced device links patches, which lets the smmu's
runtime to follow the master's runtime pm, so the smmu remains
powered only when the masters use it.
It also
On Fri 19-01-18 12:37:51, Christian König wrote:
[...]
> The per file descriptor badness is/was just the much easier approach to
> solve the issue, because the drivers already knew which client is currently
> using which buffer objects.
>
> I of course agree that file descriptors can be shared bet
From: Sricharan R
The smmu device probe/remove and add/remove master device callbacks
gets called when the smmu is not linked to its master, that is without
the context of the master device. So calling runtime apis in those places
separately.
Signed-off-by: Sricharan R
[vivek: Cleanup pm runtim
While handling the concerned iommu, there should not be a
need to power control the drm devices from iommu interface.
If these drm devices need to be powered around this time,
the respective drivers should take care of this.
Replace the pm_runtime_get/put_sync() with
pm_runtime_get/put_suppliers()
qcom,smmu-v2 is an arm,smmu-v2 implementation with specific
clock and power requirements. This smmu core is used with
multiple masters on msm8996, viz. mdss, video, etc.
Add bindings for the same.
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/iommu/arm,smmu.txt | 43 +++
Thank you very very much.
Sorry for the disturbance, to all.
Enrico
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
On Fri 19-01-18 13:13:51, Michal Hocko wrote:
> On Fri 19-01-18 12:37:51, Christian König wrote:
> [...]
> > The per file descriptor badness is/was just the much easier approach to
> > solve the issue, because the drivers already knew which client is currently
> > using which buffer objects.
> >
>
The device link allows the pm framework to tie the supplier and
consumer. So, whenever the consumer is powered-on the supplier
is powered-on first.
There are however cases in which the consumer wants to power-on
the supplier, but not itself.
E.g., A Graphics or multimedia driver wants to power-on
On Fri 19-01-18 09:39:03, Christian König wrote:
> Am 19.01.2018 um 09:20 schrieb Michal Hocko:
[...]
> > OK, in that case I would propose a different approach. We already
> > have rss_stat. So why do not we simply add a new counter there
> > MM_KERNELPAGES and consider those in oom_badness? The ru
From: Sricharan R
The smmu needs to be functional only when the respective
master's using it are active. The device_link feature
helps to track such functional dependencies, so that the
iommu gets powered when the master device enables itself
using pm_runtime. So by adapting the smmu driver for
r
On 2018-01-19 11:02 AM, Michel Dänzer wrote:
> On 2018-01-19 10:58 AM, Christian König wrote:
>> Am 19.01.2018 um 10:32 schrieb Michel Dänzer:
>>> On 2018-01-19 09:39 AM, Christian König wrote:
Am 19.01.2018 um 09:20 schrieb Michal Hocko:
> OK, in that case I would propose a different appr
2018-01-17 22:55 GMT+01:00 Laurent Pinchart
:
> Hello,
>
> This patch series removes a few cargo-cult constructs from a set of atomic
> drivers.
>
> Patches 01/12 and 02/12 remove the unneeded .mode_set() and .mode_set_base()
> CRTC handlers from the arc and atmel-hlcdc drivers.
>
> Patches 03/12 t
https://bugs.freedesktop.org/show_bug.cgi?id=104216
--- Comment #10 from Germano Massullo ---
Created attachment 136847
--> https://bugs.freedesktop.org/attachment.cgi?id=136847&action=edit
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=104216
--- Comment #9 from Germano Massullo ---
Created attachment 136846
--> https://bugs.freedesktop.org/attachment.cgi?id=136846&action=edit
LIBGL_DEBUG=verbose firefox
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=98520
--- Comment #41 from MirceaKitsune ---
(In reply to wbrana from comment #40)
Hi. I do not run Ubuntu, just openSUSE Tumbleweed. However they finally
upgraded to Mesa 17.3.2 recently, so I may test more games soon and see if
there are any crashes
On Fri, 19 Jan 2018, Daniel Thompson wrote:
> On Fri, Jan 19, 2018 at 10:39:16AM +, Meghana Madhyastha wrote:
> > Add helper functions backlight_enable and backlight_disable to
> > enable/disable a backlight device. These helper functions can
> > then be used by different drm and tinydrm drive
Newer GPU cores added a new clock input, which allows to gate the slave (AHB)
interface independently from other parts of the GPU. Add it to the supported
clocks.
Signed-off-by: Lucas Stach
---
Documentation/devicetree/bindings/display/etnaviv/etnaviv-drm.txt | 3 ++-
1 file changed, 2 insertion
On 01/19/2018 01:02 AM, Gustavo A. R. Silva wrote:
Return statements in functions returning bool should use
true/false instead of 1/0.
This issue was detected with the help of Coccinelle.
Signed-off-by: Gustavo A. R. Silva
Reviewed-by: Thomas Hellström
I'll queue this for 4.17.
Thanks,
Tho
https://bugs.freedesktop.org/show_bug.cgi?id=98520
--- Comment #40 from wbr...@gmail.com ---
Does it still occur with recent distros like Ubuntu 17.10?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
With different SoCs gaining support for etnaviv it doesn't make much sense
to add specific compatibles for the generic GPU subsystem node, which is
only used to find all GPU core nodes.
Add a generic compatible, that can be used by all new implementations.
Signed-off-by: Lucas Stach
---
Documen
While the clocks were documented as required, the driver always treated them
as optional and there are existing Marvell Dove DTs, which would break if
changed to required. Accept reality and document the clocks as optional.
Signed-off-by: Lucas Stach
---
.../devicetree/bindings/display/etnaviv/e
Am 19.01.2018 um 11:40 schrieb Michal Hocko:
On Fri 19-01-18 09:39:03, Christian König wrote:
Am 19.01.2018 um 09:20 schrieb Michal Hocko:
[...]
OK, in that case I would propose a different approach. We already
have rss_stat. So why do not we simply add a new counter there
MM_KERNELPAGES and c
https://bugzilla.kernel.org/show_bug.cgi?id=198513
Matt (m.mcn...@gmail.com) changed:
What|Removed |Added
Resolution|CODE_FIX|INVALID
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=198513
Matt (m.mcn...@gmail.com) changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|-
On Fri, Jan 19, 2018 at 10:37:58AM +, Meghana Madhyastha wrote:
> Move drm helper functions from tinydrm-helpers to linux/backlight for
> ease of use by callers in other drivers.
>
> changes in v17:
> -set fb_blank along with clearing the BL_CORE_FBBLANK bit
> -rebase with drm-misc-next
> -fi
On Fri, Jan 19, 2018 at 10:44:33AM +, Meghana Madhyastha wrote:
> Add devm_of_find_backlight and the corresponding release
> function because some drivers use devres versions of functions
> for acquiring device resources.
>
> Signed-off-by: Meghana Madhyastha
Acked-by: Daniel Thompson
> -
On Fri, Jan 19, 2018 at 10:42:15AM +, Meghana Madhyastha wrote:
> Add of_find_backlight, a helper function which is a generic version
> of tinydrm_of_find_backlight that can be used by other drivers to avoid
> repetition of code and simplify things.
>
> Signed-off-by: Meghana Madhyastha
Didn
Add SPDX identifiers to OriseTech OTM8009a panel driver.
Signed-off-by: Philippe Cornu
---
drivers/gpu/drm/panel/panel-orisetech-otm8009a.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/panel/panel-orisetech-otm8009a.c
b/drivers/gpu/drm/panel/panel-oris
On Fri, Jan 19, 2018 at 10:39:16AM +, Meghana Madhyastha wrote:
> Add helper functions backlight_enable and backlight_disable to
> enable/disable a backlight device. These helper functions can
> then be used by different drm and tinydrm drivers to avoid
> repetition of code and also to enforce
Replace of_find_backlight_by_node and of the code around it
with of_find_backlight helper to avoid repetition of code.
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-remove put_device() to avoid double put
as we are using the devm version
drivers/gpu/drm/omapdrm/displays/panel-dpi.c |
Replace of_find_backlight_by_node and of the code around it
with of_find_backlight helper to avoid repetition of code.
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-remove put_device() to avoid double put
as we are using the devm version
drivers/gpu/drm/panel/panel-innolux-p079zca.c
Use backlight_enable/disable helpers instead of changing
the property and calling backlight_update_status for cleaner
and simpler code and also to avoid repetitions.
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-remove redundant NULL check
drivers/gpu/drm/panel/panel-innolux-p079zca.c
Use backlight_enable/disable helpers instead of changing
the property and calling backlight_update_status for cleaner
and simpler code and also to avoid repetitions.
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-remove redundant NULL check
drivers/gpu/drm/omapdrm/displays/panel-dpi.c |
Call devm_of_find_backlight (the devres version) instead of
of_find_backlight.
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-convert st7735r callers from tinydrm specific helpers
to new generic backlight helpers
drivers/gpu/drm/tinydrm/mi0283qt.c | 2 +-
drivers/gpu/drm/tinydrm/st7735
Add devm_of_find_backlight and the corresponding release
function because some drivers use devres versions of functions
for acquiring device resources.
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-fix checkpath errors/warnings
-rename devm_backlight_put to
devm_backlight_release
dri
Remove tinydrm_of_find_backlight from tinydrm-helpers.c. We now have
a generic of_find_backlight defined in backlight.c. Let the callers
of tinydrm_of_find_backlight call of_find_backlight. Also, remove
select BACKLIGHT_LCD_SUPPORT and select BACKLIGHT_CLASS_DEVICE from
tinydrm/Kconfig as it is a h
Add of_find_backlight, a helper function which is a generic version
of tinydrm_of_find_backlight that can be used by other drivers to avoid
repetition of code and simplify things.
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-rebase with drm-misc-next
-convert st7735r callers from tinydr
Hi Archit,
Many thanks for this documentation add-on.
I wonder if an extra example of "2 DSI hosts driving a dual-channel DSI
peripheral controlled by the mipi bus" could be useful? well, I am not
really convinced it is necessary and maybe this extra example could be
added later when someone w
Remove tinydrm_enable/disable_backlight and let the callers call the
more generic backlight_enable/disable helpers
Signed-off-by: Meghana Madhyastha
---
changes in v17:
-rebase with drm-misc-next
drivers/gpu/drm/tinydrm/core/tinydrm-helpers.c | 55 --
drivers/gpu/drm/tin
Add helper functions backlight_enable and backlight_disable to
enable/disable a backlight device. These helper functions can
then be used by different drm and tinydrm drivers to avoid
repetition of code and also to enforce a uniform and consistent
way to enable/disable a backlight device.
Signed-o
Move drm helper functions from tinydrm-helpers to linux/backlight for
ease of use by callers in other drivers.
changes in v17:
-set fb_blank along with clearing the BL_CORE_FBBLANK bit
-rebase with drm-misc-next
-fix checkpath errors/warnings
-Make the gpio_backlight issue appear as a comment in
Hi Archit,
Many thanks for this documentation update.
Reviewed-by: Philippe Cornu
Philippe :-)
On 01/18/2018 05:53 AM, Archit Taneja wrote:
> Add a section that describes dt-bindings for peripherals that support
> MIPI DSI, but have a different bus as the primary control bus, or no
> control b
https://bugs.freedesktop.org/show_bug.cgi?id=103443
Marta Löfstedt changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=103443
Marta Löfstedt changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this mail
On 2018-01-19 10:58 AM, Christian König wrote:
> Am 19.01.2018 um 10:32 schrieb Michel Dänzer:
>> On 2018-01-19 09:39 AM, Christian König wrote:
>>> Am 19.01.2018 um 09:20 schrieb Michal Hocko:
On Thu 18-01-18 12:01:32, Eric Anholt wrote:
> Michal Hocko writes:
>
>> On Thu 18-01-1
On 2018年01月19日 16:25, Michal Hocko wrote:
[removed the broken quoting - please try to use an email client which
doesn't mess up the qouted text]
On Fri 19-01-18 06:01:26, He, Roger wrote:
[...]
I think you are misunderstanding here.
Actually for now, the memory in TTM Pools already has mm_shr
Am 19.01.2018 um 10:32 schrieb Michel Dänzer:
On 2018-01-19 09:39 AM, Christian König wrote:
Am 19.01.2018 um 09:20 schrieb Michal Hocko:
On Thu 18-01-18 12:01:32, Eric Anholt wrote:
Michal Hocko writes:
On Thu 18-01-18 18:00:06, Michal Hocko wrote:
On Thu 18-01-18 11:47:48, Andrey Grodzov
On Fri, Jan 19, 2018 at 08:38:20AM +0100, Enrico Mioso wrote:
> I forgot one last question. Is there any way I can force the system
> to switch to the ATI card without installing a graphical environment,
> just out of curiosity?
As you've observed correctly, your particular machine isn't capable o
https://bugs.freedesktop.org/show_bug.cgi?id=104683
--- Comment #3 from Michel Dänzer ---
(In reply to Dieter Nützel from comment #2)
> If this is unrelated I'll open my own bug.
Please do.
--
You are receiving this mail because:
You are the assignee for the bug.___
1 - 100 of 141 matches
Mail list logo
