Rodrigo Vivi writes:
> "Pandiyan, Dhinakaran" writes:
>
>> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
>>> Hi Andy,
>>>
>>> thanks for getting involved with PSR and sorry for not replying sooner.
>>>
>>> I first saw this patch on that bugzilla entry but only now I stop to
>>> really t
the free mem space and the lower limit both include two parts:
system memory and swap space.
For the OOM triggered by TTM, that is the case as below:
first swap space is full of swapped out pages and soon
system memory also is filled up with ttm pages. and then
any memory allocation request will r
if it is true, allocate TTM pages regardless of zone global memory
account limit. For example suspend, We should avoid TTM memory
allocate failure to lead to whole process fail.
Signed-off-by: Roger He
---
drivers/gpu/drm/ttm/ttm_bo.c | 13 -
1 file changed, 8 insertions(+), 5 delet
set TTM_OPT_FLAG_FORCE_ALLOC when we are servicing for page
fault routine.
for ttm_mem_global_reserve if in page fault routine, allow the gtt
pages reservation always. because page fault routing already grabbed
system memory and the allowance of this exception is harmless.
Otherwise, it will trigg
FYI, we noticed the following commit (built with gcc-4.9):
commit: fc7168134273b29c0bd2e2fcdf5fdc286154a042 ("drm: Multiple Null pointer
dereference [null-pointer-deref] (CWE 476) problems:")
url:
https://github.com/0day-ci/linux/commits/Joe-Moriarty/drm-Multiple-Null-pointer-dereference-null-po
I can't think of an use case when we don't want this to succeed.
That is true. seems I can simplify more here.
Thanks
Roger(Hongbo.He)
-Original Message-
From: Koenig, Christian
Sent: Thursday, February 08, 2018 8:58 PM
To: He, Roger ; amd-...@lists.freedesktop.org;
dri-devel@li
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #16 from Matthew Scheirer ---
I get this as well with a 290 on 4.15 ONLY when DC is enabled. Its a dirty
enough taint to leave btrfs volumes in inconsistent states so its straight
crashing the kernel.
Feb 08 17:06:08 system kernel:
swiotlb expands our card accessing range, but its path always is slower
than ttm pool allocation.
So add condition to use it.
v2: move a bit later
Change-Id: I1802645833155a9cd808913f863981173a82145f
Signed-off-by: Chunming Zhou
Reviewed-by: Monk Liu
Reviewed-by: Christian König
---
drivers/gp
get the max io mapping address of system memory to see if it is over
our card accessing range.
v2: move checking later
Change-Id: Ibc38dbd34a20af5b4a4b1ed154c14e1c58aa4c55
Signed-off-by: Chunming Zhou
Reviewed-by: Monk Liu
Reviewed-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h
it will be used to check if the driver needs swiotlb
v2: Don't use inline, instead, move function to drm_memory.c (Mechel Daenzer
)
Change-Id: Idbe47af8f12032d4803bb3d47273e807f19169c3
Signed-off-by: Chunming Zhou
Reviewed-by: Monk Liu
Reviewed-by: Christian König
---
drivers/gpu/drm/drm_memo
https://bugs.freedesktop.org/show_bug.cgi?id=104963
--- Comment #3 from Will ---
Chiming in to say I've had the same issue for an extremely frustratingly long
time. I haven't been able to run anything newer than 14.04 on this machine
until today. I can confirm that the radeon.dpm setting doesn't
On Mon, Feb 05, 2018 at 03:34:27PM +0100, Heiko Stuebner wrote:
> From: Zheng Yang
>
> The phy is used so far in two Rockchip socs the rk3228 and the rk3328.
>
> Signed-off-by: Zheng Yang
> Signed-off-by: Heiko Stuebner
> ---
> .../bindings/phy/phy-rockchip-inno-hdmi.txt| 42
> ++
On Mon, Feb 05, 2018 at 10:45:31AM +0100, Philippe Cornu wrote:
> Some boards use a dedicated voltage regulator for this panel.
> Add & document this related optional power-supply property.
>
> Signed-off-by: Philippe Cornu
> ---
> Documentation/devicetree/bindings/display/panel/orisetech,otm800
Hi Daniel,
On Tue, 2018-01-30 at 02:27:07 -0800, Daniel Vetter wrote:
> On Thu, Jan 25, 2018 at 06:03:59PM -0800, Hyun Kwon wrote:
> > Multiple pixels can be grouped as a single unit and form a 'macro-pixel'.
> > This is to model formats where multiple pixels are stored together
> > in a specific
Hi Daniel,
On Tue, 2018-01-30 at 02:22:40 -0800, Daniel Vetter wrote:
> On Thu, Jan 25, 2018 at 06:03:59PM -0800, Hyun Kwon wrote:
> > Multiple pixels can be grouped as a single unit and form a 'macro-pixel'.
> > This is to model formats where multiple pixels are stored together
> > in a specific
"Pandiyan, Dhinakaran" writes:
> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
>> Hi Andy,
>>
>> thanks for getting involved with PSR and sorry for not replying sooner.
>>
>> I first saw this patch on that bugzilla entry but only now I stop to
>> really think why I have written the cod
On Thu, 2018-02-08 at 17:01 -0800, Andy Lutomirski wrote:
>
>
> > On Feb 8, 2018, at 4:39 PM, Pandiyan, Dhinakaran
> > wrote:
> >
> >
> >> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
> >> Hi Andy,
> >>
> >> thanks for getting involved with PSR and sorry for not replying sooner.
https://bugs.freedesktop.org/show_bug.cgi?id=105018
ragnaros39...@yandex.com changed:
What|Removed |Added
Keywords||regression
Priority
https://bugs.freedesktop.org/show_bug.cgi?id=105018
Bug ID: 105018
Summary: Kernel panic when waking up after screen goes blank.
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
> On Feb 8, 2018, at 4:39 PM, Pandiyan, Dhinakaran
> wrote:
>
>
>> On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
>> Hi Andy,
>>
>> thanks for getting involved with PSR and sorry for not replying sooner.
>>
>> I first saw this patch on that bugzilla entry but only now I stop to
>>
This allows for importing buffers allocated from the
hikey and hikey960 gralloc implelementations.
Feedback or comments would be greatly appreciated!
Cc: Marissa Wall
Cc: Sean Paul
Cc: Dmitry Shmidt
Cc: Robert Foss
Cc: Matt Szczesiak
Cc: Liviu Dudau
Cc: David Hanna
Cc: Rob Herring
Change-
https://bugs.freedesktop.org/show_bug.cgi?id=104142
--- Comment #5 from JohnDoe ---
I ran into this bug when upgrading to 4.15.1. Anything I can do to help?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
On Thu, 2018-02-08 at 14:48 -0800, Rodrigo Vivi wrote:
> Hi Andy,
>
> thanks for getting involved with PSR and sorry for not replying sooner.
>
> I first saw this patch on that bugzilla entry but only now I stop to
> really think why I have written the code that way.
>
> So some clarity below.
On Wed, Feb 7, 2018 at 12:01 PM, Ville Syrjälä
wrote:
> On Wed, Feb 07, 2018 at 06:28:42PM +0200, Ville Syrjälä wrote:
>> On Sun, Feb 04, 2018 at 06:50:45PM -0500, Ilia Mirkin wrote:
>> > In case anyone's curious about 30bpp framebuffer support, here's the
>> > current status:
>> >
>> > Kernel:
>>
https://bugs.freedesktop.org/show_bug.cgi?id=92827
--- Comment #10 from Michael Zapf ---
I now believe there is a general problem with amdgpu's new DC.
On another system, without an AV receiver in the chain, my display resolution
is reset to 1368x768 when I turn off the monitor and back on. Tha
Hi Andy,
thanks for getting involved with PSR and sorry for not replying sooner.
I first saw this patch on that bugzilla entry but only now I stop to
really think why I have written the code that way.
So some clarity below.
On Mon, Feb 05, 2018 at 10:07:09PM +, Andy Lutomirski wrote:
> The
El Thu, Feb 08, 2018 at 04:44:21PM -0500 Harry Wentland ha dit:
> On 2018-02-08 04:03 PM, Harry Wentland wrote:
> > On 2018-02-08 03:53 PM, Matthias Kaehlcke wrote:
> >> calcs uses the compiler option -mpreferred-stack-boundary=4 to configure
> >> a stack alignment of 16 bytes. Clang uses the opti
Hi Kieran,
On Thursday, 8 February 2018 01:30:43 EET Kieran Bingham wrote:
> On 07/02/18 21:59, Laurent Pinchart wrote:
> > On Wednesday, 7 February 2018 17:14:09 EET Kieran Bingham wrote:
> >> On 29/01/18 10:26, Laurent Pinchart wrote:
> >>> On Monday, 22 January 2018 14:50:00 EET Kieran Bingham
On 2018-02-08 04:03 PM, Harry Wentland wrote:
> On 2018-02-08 03:53 PM, Matthias Kaehlcke wrote:
>> calcs uses the compiler option -mpreferred-stack-boundary=4 to configure
>> a stack alignment of 16 bytes. Clang uses the option -mstack-alignment
>> instead, which expects as parameter the alignment
Which is used in wraps.
---
meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meson.build b/meson.build
index 1342a5b3..4aaeb7e1 100644
--- a/meson.build
+++ b/meson.build
@@ -294,7 +294,7 @@ libdrm = shared_library(
ext_libdrm = declare_dependency(
link_with :
From: Markus Elfring
Date: Thu, 8 Feb 2018 22:23:57 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 1 -
1 file changed, 1 dele
On 2018-02-08 03:53 PM, Matthias Kaehlcke wrote:
> calcs uses the compiler option -mpreferred-stack-boundary=4 to configure
> a stack alignment of 16 bytes. Clang uses the option -mstack-alignment
> instead, which expects as parameter the alignment in bytes, and not a
> power of two like -mpreferre
The following patch(s) are bugs found by the static compiler
'Parfait'. Care was taken to make sure false positive results
were removed from this patchset.
Parfait Overview
https://labs.oracle.com/pls/apex/f?p=labs:49:P49_PROJECT_ID:13
Joe Moriarty (1):
drm: Multiple Null
DML uses the compiler option -mpreferred-stack-boundary=4 to configure
a stack alignment of 16 bytes. Clang uses the option -mstack-alignment
instead, which expects as parameter the alignment in bytes, and not a
power of two like -mpreferred-stack-boundary.
Probe for both compiler options and use
calcs uses the compiler option -mpreferred-stack-boundary=4 to configure
a stack alignment of 16 bytes. Clang uses the option -mstack-alignment
instead, which expects as parameter the alignment in bytes, and not a
power of two like -mpreferred-stack-boundary.
Probe for both compiler options and us
Use a variable for common CFLAGS instead of specifying the same flags
for every source file.
Signed-off-by: Matthias Kaehlcke
---
Changes in v3:
- Use variable for compiler options instead of subdir-ccflags-y
drivers/gpu/drm/amd/display/dc/dml/Makefile | 17 +
1 file changed, 9
Use a variable for common CFLAGS instead of specifying the same flags
for every source file.
Signed-off-by: Matthias Kaehlcke
---
Changes in v3:
- patch added
drivers/gpu/drm/amd/display/dc/calcs/Makefile | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/dr
From: Markus Elfring
Date: Thu, 8 Feb 2018 21:10:58 +0100
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected functions.
Signed-off-by: Markus Elfring
---
drivers
From: Markus Elfring
Date: Thu, 8 Feb 2018 21:01:24 +0100
The script "checkpatch.pl" pointed information out like the following.
WARNING: Comparisons should place the constant on the right side
of the test
WARNING: else is not generally useful after a break or return
Thus fix the affected sourc
From: Markus Elfring
Date: Thu, 8 Feb 2018 20:32:39 +0100
Omit an extra message for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/amd/powerplay/hwmgr/cz_hwmgr.c | 4 +---
drivers/gpu/
From: Markus Elfring
Date: Thu, 8 Feb 2018 21:37:42 +0100
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete an error message for a failed memory allocation in three functions
Adjust layout for source code from five if statements
D
https://bugs.freedesktop.org/show_bug.cgi?id=104919
Andy Furniss changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
On Wed, Feb 07, 2018 at 01:49:59PM +0100, Giulio Benetti wrote:
> Hi,
>
> Il 07/02/2018 11:39, Maxime Ripard ha scritto:
> > On Wed, Jan 24, 2018 at 08:37:28PM +0100, Giulio Benetti wrote:
> > Also, how was it tested? This seems quite weird that we haven't caught
> > that one sooner, and I
https://bugzilla.kernel.org/show_bug.cgi?id=197327
--- Comment #5 from Eugene (ken20...@ukr.net) ---
Created attachment 274071
--> https://bugzilla.kernel.org/attachment.cgi?id=274071&action=edit
dmesg_GA-MA790FX-DQ6
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=197327
Eugene (ken20...@ukr.net) changed:
What|Removed |Added
CC||ken20...@ukr.net
--- Comment
On Thu, Feb 08, 2018 at 10:27:54AM +0100, Andrzej Hajda wrote:
> On 07.02.2018 22:43, Rob Herring wrote:
> > On Mon, Feb 05, 2018 at 10:06:35AM +0100, Andrzej Hajda wrote:
> >> On 05.02.2018 07:08, Rob Herring wrote:
> >>> On Wed, Jan 31, 2018 at 02:44:31PM +0100, Andrzej Hajda wrote:
> These
On Thu, Feb 8, 2018 at 12:31 PM, Jordan Crouse wrote:
> Convert the existing GPU show function to use the GPU state to
> dump the information rather than reading it directly from the hardware.
> This will require an additional step to capture the state before
> dumping it for the existing nodes bu
El Thu, Feb 08, 2018 at 09:33:53AM -0500 Harry Wentland ha dit:
> On 2018-02-07 08:51 PM, Matthias Kaehlcke wrote:
> > Use subdir-ccflags instead of specifying the same flags for every source
> > file.
> >
> > Signed-off-by: Matthias Kaehlcke
> > Reviewed-by: Guenter Roeck
> > ---
> > Changes i
On Thu, Feb 8, 2018 at 11:48 AM, Sean Paul wrote:
> This patch adds a new subnode to simple-panel allowing us to override
> the typical timing expressed in the panel's display_timing.
>
> Changes in v2:
> - Split out the binding into a new patch (Rob)
> - display-timings is a new section (Rob)
>
On Thu, Feb 8, 2018 at 11:48 AM, Sean Paul wrote:
> In preparation for a new subnode section in a follow-on patch, add
> explicit headings to the existings sections for simple-panel.
>
> Changes in v2:
> - Added
> Changes in v3:
> - None
>
> Cc: Doug Anderson
> Cc: Eric Anholt
> Cc: Heiko Stue
On Thu, Feb 8, 2018 at 11:48 AM, Sean Paul wrote:
> Add a note in the documentation explaining when it's appropriate to use
> the display-timings subnode on its own, as well as the preferred name to
> use (panel-timing).
>
> Changes in v3:
> - Added
>
> Cc: Doug Anderson
> Cc: Eric Anholt
> Cc:
From: Markus Elfring
Date: Thu, 8 Feb 2018 19:30:06 +0100
Omit an extra message for a memory allocation failure in this function.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/drm_fb_cma_helper.c | 5 ++---
1 file changed, 2 insert
The Parfait (version 2.1.0) static code analysis tool found multiple NULL
pointer derefernce problems.
- drivers/gpu/drm/drm_dp_mst_topology.c
The call to drm_dp_calculate_rad() in function drm_dp_port_setup_pdt()
could result in a NULL pointer being returned to port->mstb due to a
failure to allo
From: Markus Elfring
Date: Thu, 8 Feb 2018 18:42:51 +0100
Omit an extra message for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/exynos/exynos_drm_g2d.c | 6 ++
1 file changed, 2
Quoting Jordan Crouse (2018-02-08 17:31:50)
> The i915 DRM driver very cleverly used ascii85 encoding for their
> GPU state file. Move the encode functions to a general header file to
> support other drivers that might be interested in the same
> functionality.
>
> [v2 - Update the API to be clean
Add a note in the documentation explaining when it's appropriate to use
the display-timings subnode on its own, as well as the preferred name to
use (panel-timing).
Changes in v3:
- Added
Cc: Doug Anderson
Cc: Eric Anholt
Cc: Heiko Stuebner
Cc: Jeffy Chen
Cc: Rob Herring
Cc: Stéphane Marche
In preparation for a new subnode section in a follow-on patch, add
explicit headings to the existings sections for simple-panel.
Changes in v2:
- Added
Changes in v3:
- None
Cc: Doug Anderson
Cc: Eric Anholt
Cc: Heiko Stuebner
Cc: Jeffy Chen
Cc: Rob Herring
Cc: Stéphane Marchesin
Cc: Thie
Hello!
Here's v3 of the set. I've reintroduced the single display timing node
in the dt binding from v1, and left the improved docs and patch split
from v2. I've also added a patch to clarify that a single display timing
node should always be named panel-timing, which was feedback from v1.
Cover
Convert the sharp lq123p1jx31 from using a fixed mode to specifying a
display timing with min/typ/max values. This allows us to capture the
timings set forth in the datasheet as well as the additional values that
we've cleared with the display vendor to avoid interference with the
digitizer on the
This patch adds a new subnode to simple-panel allowing us to override
the typical timing expressed in the panel's display_timing.
Changes in v2:
- Split out the binding into a new patch (Rob)
- display-timings is a new section (Rob)
- Use the full display-timings subnode instead of picking the
This patch adds an override mode for kevin devices. The mode increases
both back porches to allow a pixel clock of 2kHz as opposed to the
'typical' value of 252750kHz. This is needed to avoid interference with
the touch digitizer on these laptops.
Changes in v2:
- Wrap the timing in display-t
This patch adds the ability to override the typical display timing for a
given panel. This is useful for devices which have timing constraints
that do not apply across the entire display driver (eg: to avoid
crosstalk between panel and digitizer on certain laptops). The rules are
as follows:
- pan
Add the contents of each ringbuffer to the GPU state and dump the
data in the crash file encoded with ascii85. To save space only
the used portions of the ringbuffer are dumped.
Signed-off-by: Jordan Crouse
---
Documentation/gpu/drm-msm-crash-dump.txt | 5
drivers/gpu/drm/msm/adreno/adreno
HLSQ, SP and TP registers are only accessible from a special
aperture and to make matters worse the aperture is blocked from
the CPU on targets that can support secure rendering. Luckily the
GPU hardware has its own purpose built register dumper that can
access the registers from the aperture. Add
Capture the GPU state on a GPU hang and store it for later playback
via the devcoredump facility. Only one crash state is stored at a
time on the assumption that the first hang is usually the most
interesting. The existing crash state can be cleared after capturing
it and then a new one will be cap
This is revision 3 of my stack implementing a GPU crash state for drm/msm
(https://patchwork.freedesktop.org/series/36097/).
The goal is to store and provide enough information to debug software
and hardware issues on the Adreno hardware in a semi human-readable
format that can also be parsed by s
Convert the existing GPU show function to use the GPU state to
dump the information rather than reading it directly from the hardware.
This will require an additional step to capture the state before
dumping it for the existing nodes but it will greatly facilitate reusing
the same code for dumping
Add the infrastructure to capture the state current state of the
GPU and store it in memory. This is useful for storing the state
of a hung GPU so it can be dumped later.
For now grab the same basic ringbuffer information and registers
that are provided by the debugfs 'gpu' node but obviously this
Add a drm printer suitable for use with the read callback for
devcoredump or any other file operation read() function that
isn't otherwise covered by seq_file.
Signed-off-by: Jordan Crouse
---
drivers/gpu/drm/drm_print.c | 54 +
include/drm/drm_print.h
Convert the format of the 'show' debugfs file and the crash
dump to a format resembling YAML. This should be easier to
parse and be more flexible for future changes and expansions.
Signed-off-by: Jordan Crouse
---
Documentation/gpu/drm-msm-crash-dump.txt | 29 +
driv
The i915 DRM driver very cleverly used ascii85 encoding for their
GPU state file. Move the encode functions to a general header file to
support other drivers that might be interested in the same
functionality.
[v2 - Update the API to be cleaner for the caller suggested by
Chris Wilson]
Signed-off
Hi Philippe,
Thank you for the patch.
On Thursday, 8 February 2018 16:58:05 EET Philippe Cornu wrote:
> Add SPDX identifiers to the Synopsys DesignWare MIPI DSI
> host controller driver.
>
> Signed-off-by: Philippe Cornu
Reviewed-by: Laurent Pinchart
> ---
> Changes in v2: Update to "GPL-2.0
On Thu, Feb 8, 2018 at 4:46 AM, Kai-Heng Feng
wrote:
> The affected system (0x0813) is pretty similar to another one (0x0812),
> it also needs to use ATPX power control.
>
> Signed-off-by: Kai-Heng Feng
Applied. thanks!
Alex
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_atpx_handler.c | 1 +
> 1
+Thierry and Archit for the drm_panel/panel_bridge bits.
Hi all,
I'm resurrecting this thread because Eric asked me to find a solution
to this problem :-).
On Mon, 20 Nov 2017 08:53:05 +0100
Andrzej Hajda wrote:
> On 18.11.2017 02:16, Eric Anholt wrote:
> > Andrzej Hajda writes:
> >
> >> On
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #26 from Bong Cosca ---
(In reply to Michel Dänzer from comment #25)
>
> Where do you see that?
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the bug.___
dr
On 02/08/2018 02:11 PM, Bartlomiej Zolnierkiewicz wrote:
>
> Hi,
>
> [ dri-devel ML & arch/[score,um] Maintainers added to Cc: ]
>
> On Friday, February 02, 2018 08:59:57 AM Christian Borntraeger wrote:
>> On 02/01/2018 07:41 PM, Farhan Ali wrote:
>>> The 'commit e25df1205f37 ("[S390] Kconfig:
Hi Laurent, Benjamin & Philippe,
I sent an updated version of the patch following your comments
Big thank you,
Philippe :-)
On 02/08/2018 03:09 PM, Philippe Ombredanne wrote:
> Benjamin,
>
> On Wed, Jan 24, 2018 at 9:57 AM, Benjamin Gaignard
> wrote:
>> 2018-01-24 0:32 GMT+01:00 Laurent Pincha
Hi Benjamin,
and many thanks for having applied the 2 patches.
Philippe :-)
On 02/08/2018 10:40 AM, Benjamin Gaignard wrote:
> 2018-02-06 10:12 GMT+01:00 Yannick FERTRE :
>> Reviewed-by: Yannick Fertré
>>
>>
>> On 02/01/2018 11:42 AM, Philippe Cornu wrote:
>>> ltdc supports natively some color fo
Add SPDX identifiers to the Synopsys DesignWare MIPI DSI
host controller driver.
Signed-off-by: Philippe Cornu
---
Changes in v2: Update to "GPL-2.0+" following comments from Laurent
Pinchart, Benjamin Gaignard & Philippe Ombredanne.
drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 6 +-
1 f
From: Markus Elfring
Date: Thu, 8 Feb 2018 15:17:48 +0100
The script "checkpatch.pl" pointed information out like the following.
WARNING: void function return statements are not generally useful
Thus remove such a statement in the affected function.
Signed-off-by: Markus Elfring
---
drivers/
From: Markus Elfring
Date: Thu, 8 Feb 2018 15:08:39 +0100
Replace the specification of data structures by pointer dereferences
as the parameter for the operator "sizeof" to make the corresponding size
determination a bit safer according to the Linux coding style convention.
This issue was detect
From: Markus Elfring
Date: Thu, 8 Feb 2018 14:55:49 +0100
Omit an extra message for a memory allocation failure in these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/gma500/framebuffer.c | 4 +---
drivers/gpu/drm/gma5
https://bugs.freedesktop.org/show_bug.cgi?id=105005
--- Comment #8 from Michel Dänzer ---
(In reply to Dmitry from comment #7)
> After rebooting done due to this problem. Without the screen it is
> problematic to do, immediately after.
If you have another computer, you can do it via ssh.
> 4.1
From: Markus Elfring
Date: Thu, 8 Feb 2018 15:27:38 +0100
Three update suggestions were taken into account
from static source code analysis.
Markus Elfring (3):
Delete an error message for a failed memory allocation in two functions
Improve four size determinations
Delete an unnecessary re
On 2018-02-07 08:51 PM, Matthias Kaehlcke wrote:
> Use subdir-ccflags instead of specifying the same flags for every source
> file.
>
> Signed-off-by: Matthias Kaehlcke
> Reviewed-by: Guenter Roeck
> ---
> Changes in v2:
> - added 'Reviewed-by: Guenter Roeck ' tag
>
> drivers/gpu/drm/amd/displ
The Raydium Semiconductor Corporation RM68200 is a 5.5" 720x1280
TFT LCD panel connected using a MIPI-DSI video interface.
Philippe Cornu (2):
dt-bindings/display/panel: Add support for Raydium rm68200 dsi panel
drm/panel: Add support for Raydium rm68200 panel driver
.../bindings/display/pan
The Raydium Semiconductor Corporation RM68200 is a 5.5" 720x1280
TFT LCD panel connected using a MIPI-DSI video interface.
Signed-off-by: Philippe Cornu
---
.../bindings/display/panel/raydium,rm68200.txt | 25 ++
1 file changed, 25 insertions(+)
create mode 100644
Docum
This patch adds Raydium Semiconductor Corporation rm68200
5.5" 720x1280 TFT LCD panel driver (MIPI-DSI video mode).
Signed-off-by: Philippe Cornu
---
drivers/gpu/drm/panel/Kconfig | 8 +
drivers/gpu/drm/panel/Makefile| 1 +
drivers/gpu/drm/panel/panel-raydium-
https://bugs.freedesktop.org/show_bug.cgi?id=104082
Stratos Zolotas changed:
What|Removed |Added
CC||str...@gmail.com
--- Comment #15 from
On Wednesday, January 31, 2018 08:51:23 PM Mathieu Malaterre wrote:
> Bartlomiej,
>
> On Wed, Jan 31, 2018 at 12:57 PM, Bartlomiej Zolnierkiewicz
> wrote:
> > On Tuesday, January 30, 2018 02:14:10 PM Mathieu Malaterre wrote:
> >> Bartlomiej,
> >>
> >> On Wed, Jan 3, 2018 at 3:47 PM, Bartlomiej Zo
Hi Philippe,
On Saturday, 3 February 2018 00:41:26 EET Philippe CORNU wrote:
> On 01/29/2018 11:40 AM, Laurent Pinchart wrote:
> > On Monday, 29 January 2018 12:17:37 EET Philippe CORNU wrote:
> >> On 01/29/2018 10:46 AM, Laurent Pinchart wrote:
> >>> On Thursday, 25 January 2018 17:55:04 EET Phil
Hi,
[ dri-devel ML & arch/[score,um] Maintainers added to Cc: ]
On Friday, February 02, 2018 08:59:57 AM Christian Borntraeger wrote:
> On 02/01/2018 07:41 PM, Farhan Ali wrote:
> > The 'commit e25df1205f37 ("[S390] Kconfig: menus with depends on
> > HAS_IOMEM.")'
> > added the HAS_IOMEM depend
Am 08.02.2018 um 10:06 schrieb Roger He:
if true, allocate TTM pages regardless of zone global memory
account limit. For suspend, We should avoid TTM memory allocate
failure then result in suspend failure.
Why the extra parameter for amdgpu_bo_evict_vram ?
I can't think of an use case when we
Am 08.02.2018 um 10:05 schrieb Roger He:
set TTM_OPT_FLAG_FORCE_ALLOC when we are servicing for page
fault routine.
for ttm_mem_global_reserve if in page fault routine, allow the gtt
pages reservation always. because page fault routing already grabbed
system memory and the allowance of this exce
Register the omapdrm device when we know that dss device probe going
to succeed. This avoids DSS6 and DSS2 omapdrm device registration from
colliding with each other.
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/omapdrm/dss/core.c | 26 ++
drivers/gpu/drm/omapdrm/dss/dss
From: Tomi Valkeinen
The new DSS6 driver needs some structs and defines which are currently
in dss.h, which is for the old DSS driver.
Move the required structs and defines from dss.h to omapdss.h.
Signed-off-by: Tomi Valkeinen
Signed-off-by: Jyri Sarha
---
drivers/gpu/drm/omapdrm/dss/dss.h
On 08/02/18 13:43, Jyri Sarha wrote:
> Argh, sorry I forgot about these in the previous post. (And the comment
> for "drm/omap: Fail probe if irq registration fails").
>
> On 02/08/18 10:53, Tomi Valkeinen wrote:
>> On 07/02/18 16:11, Jyri Sarha wrote:
>>> The new omapdss API is HW independent and
https://bugs.freedesktop.org/show_bug.cgi?id=105005
--- Comment #7 from Dmitry ---
After rebooting done due to this problem. Without the screen it is problematic
to do, immediately after.
4.14.15-1
--
You are receiving this mail because:
You are the assignee for the bug.___
Argh, sorry I forgot about these in the previous post. (And the comment
for "drm/omap: Fail probe if irq registration fails").
On 02/08/18 10:53, Tomi Valkeinen wrote:
> On 07/02/18 16:11, Jyri Sarha wrote:
>> The new omapdss API is HW independent and cleans up some of the DSS5
>> specific hacks f
drivers/dma-buf/sw_sync.c:248: warning: No description found for parameter 'obj'
drivers/dma-buf/sw_sync.c:248: warning: No description found for parameter
'value'
drivers/dma-buf/sw_sync.c:248: warning: Excess function parameter 'parent'
description in 'sync_pt_create'
drivers/dma-buf/sw_sync.c:
1 - 100 of 172 matches
Mail list logo