From: Markus Elfring
Date: Mon, 27 Nov 2017 21:30:06 +0100
Replace the specification of a data structure by a pointer dereference
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 det
From: Markus Elfring
Date: Mon, 27 Nov 2017 21:27:51 +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/video/fbdev/aty/radeon_backlight.c | 4 +---
1 file changed, 1
From: Markus Elfring
Date: Mon, 27 Nov 2017 21:37:52 +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: Mon, 27 Nov 2017 21:50:28 +0100
Return directly after a call of the function "kmalloc" failed
at the beginning.
Signed-off-by: Markus Elfring
---
drivers/video/fbdev/aty/radeon_backlight.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vi
From: Markus Elfring
Date: Mon, 27 Nov 2017 22:03:03 +0100
* Replace a goto statement by a direct call of the function "kfree"
in an if branch.
* Delete the jump label "error" which became unnecessary with
this refactoring.
Signed-off-by: Markus Elfring
---
drivers/video/fbdev/aty/radeon_
Hi,
On Mon, Nov 27, 2017 at 4:07 PM Ray Strode wrote:
...
> This commit changes the driver to reapply the cursor any time a new
> primary is created. It achieves this by keeping a reference to the
> cursor bo on the qxl_crtc struct.
So i forgot this is on top of a small leak fix, too.
For clarit
> There is the generic stack dump on OOM so the module/line
> is already known.
Can such an implementation detail become better documented
than in C source code?
> The existence of these messages increases code size which
> also make the OOM condition slightly more likely.
Interesting view …
From: Ray Strode
QXL associates mouse state with its primary plane.
Destroying a primary plane and putting a new one in place has the side
effect of destroying the cursor as well.
This commit changes the driver to reapply the cursor any time a new
primary is created. It achieves this by keeping
From: Ray Strode
This series includes a small leak fix and a fix for an initial invisible
cursor on wayland sessions.
Ray Strode (2):
drm/qxl: unref cursor bo when finished with it
drm/qxl: reapply cursor after resetting primary
drivers/gpu/drm/qxl/qxl_display.c | 63 ++
From: Ray Strode
qxl_cursor_atomic_update allocs a bo for the cursor that
it never frees up at the end of the function.
This commit fixes that.
Signed-off-by: Ray Strode
---
drivers/gpu/drm/qxl/qxl_display.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/dr
On Fri, Nov 24, 2017 at 5:32 AM, Christian König
wrote:
> Fixes interface changes done in the following commits:
> drm/ttm: add operation ctx to ttm_bo_validate v2
> drm/ttm: add context to driver move callback as well
>
> I missed this driver because it is in the staging area.
>
> Signed-off-by:
On Mon, Nov 27, 2017 at 7:21 AM, Christian König
wrote:
> This reverts "drm/ttm: Fix configuration error around populate_and_map()
> functions".
>
> This fix has gone into the wrong direction. Those helpers should be
> available even when neither CONFIG_INTEL_IOMMU nor CONFIG_SWIOTLB are
> set.
>
On Thu, Oct 26, 2017 at 09:44:14AM +, Philippe CORNU wrote:
> On 10/26/2017 06:13 AM, Archit Taneja wrote:
> > On 10/26/2017 06:39 AM, Brian Norris wrote:
> >> somebody already working on refactoring existing Rockchip code to use
> >> this?
> >
> > I don't know. If rockchip isn't interested in
(Dropping Mark, whose Rockchip address is dead; and fixing Chris's email again)
On Mon, Nov 27, 2017 at 4:29 PM, Brian Norris wrote:
> On Thu, Oct 26, 2017 at 09:44:14AM +, Philippe CORNU wrote:
>> On 10/26/2017 06:13 AM, Archit Taneja wrote:
>> > On 10/26/2017 06:39 AM, Brian Norris wrote:
>
Forward Error Correction is supported on DP 1.4.
This patch adds corresponding DPCD register definitions.
v2: Add dri-devel to the CC list
Cc: dri-devel@lists.freedesktop.org
Cc: Ville Syrjala
Cc: Jani Nikula
Cc: Manasi Navare
Signed-off-by: Anusha Srivatsa
---
include/drm/drm_dp_helper.h |
Bridge drivers/helpers shouldn't be clobbering the drvdata, since a
parent driver might need to own this. Instead, let's return our
'dw_mipi_dsi' object and have callers pass that back to us for removal.
Signed-off-by: Brian Norris
---
drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 36 +
We now have a generic dw-mipi-dsi bridge driver.So we send
this patchs to moving rockchip dw-mipi-dsi driver to that
in order to add new features(dual mipi support).
Update ROCKCHIP DSI controller driver that uses the Synopsys
DesignWare MIPI DSI host controller bridge.
Nickey Yang (3):
dt-bindi
This patch update documentation of device tree bindings for the rockchip
DSI controller based on the Synopsys DesignWare MIPI DSI host controller.
Signed-off-by: Nickey Yang
---
.../display/rockchip/dw_mipi_dsi_rockchip.txt | 23 ++
1 file changed, 19 insertions(+), 4 de
Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare
MIPI DSI host controller bridge.
Signed-off-by: Nickey Yang
---
drivers/gpu/drm/rockchip/Kconfig|2 +-
drivers/gpu/drm/rockchip/Makefile |2 +-
drivers/gpu/drm/rockchip/dw-mipi-dsi.c
This patch update mipi node for RK3399 DSI controller
based on the Synopsys DesignWare MIPI DSI host controller.
Signed-off-by: Nickey Yang
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399
https://bugs.freedesktop.org/show_bug.cgi?id=103783
--- Comment #13 from Rene Barbosa ---
Hey,
Is your system using 'pcieport' module?
I've added it to RUNTIME_PM_DRIVER_BLACKLIST in TLP's configuration and now the
problem is fixed!
Not sure why it's happening in Linux 4.13+ and not in 4.4 wi
On Mon, 2017-11-27 at 22:48 +0100, SF Markus Elfring wrote:
> It seems that I got no responses so far for clarification requests
> according to the documentation in a direction I hoped for.
That's because you are pretty unresponsive to
direction.
You've gotten _many_ replies to your patches to
wh
Hi Nickey,
Several people already made comments on the initial version of this
patch [1], and I don't think you've caught them all here yet. I'll
repeat a few. Not sure if I've caught them all.
[1]
https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/780120
On Tue, Nov 28,
We now have a generic dw-mipi-dsi bridge driver.So we send
this patchs to moving rockchip dw-mipi-dsi driver to that
in order to add new features(dual mipi support).
Update ROCKCHIP DSI controller driver that uses the Synopsys
DesignWare MIPI DSI host controller bridge.
ChangeLog:
v2:
add err_p
This patch update documentation of device tree bindings for the rockchip
DSI controller based on the Synopsys DesignWare MIPI DSI host controller.
Signed-off-by: Nickey Yang
---
.../display/rockchip/dw_mipi_dsi_rockchip.txt | 23 ++
1 file changed, 19 insertions(+), 4 de
Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare
MIPI DSI host controller bridge.
Signed-off-by: Nickey Yang
---
drivers/gpu/drm/rockchip/Kconfig|2 +-
drivers/gpu/drm/rockchip/Makefile |2 +-
drivers/gpu/drm/rockchip/dw-mipi-dsi.c
This patch update mipi node for RK3399 DSI controller
based on the Synopsys DesignWare MIPI DSI host controller.
Signed-off-by: Nickey Yang
---
arch/arm64/boot/dts/rockchip/rk3399.dtsi | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/rockchip/rk3399
El Mon, Nov 27, 2017 at 05:05:38PM -0800 Brian Norris ha dit:
> Bridge drivers/helpers shouldn't be clobbering the drvdata, since a
> parent driver might need to own this. Instead, let's return our
> 'dw_mipi_dsi' object and have callers pass that back to us for removal.
>
> Signed-off-by: Brian
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: f3769c94f4e6a794dbb72601936199d9b258f7b7
commit: f4d284ea58186199a9e2757dd9571d8386172141 [413/475] drm/ttm: add
operation ctx to ttm_bo_validate v2
reproduce:
# apt-get install sparse
git checkout f
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: f3769c94f4e6a794dbb72601936199d9b258f7b7
commit: f4d284ea58186199a9e2757dd9571d8386172141 [413/475] drm/ttm: add
operation ctx to ttm_bo_validate v2
config: i386-allmodconfig (attached as .config)
compiler: gcc-7 (D
From: Jeffrey Mouroux
New fourcc codes have been added to support new YUV semi-planar
and packed formats (including greyscale) needed by new Xilinx
Video IP. This patch includes recognition of these new formats
in the DRM framework library functions.
Signed-off-by: Jeffrey Mouroux
Signed-off-b
From: Jeffrey Mouroux
The Xilinx Video Mixer and Xilinx Video Framebuffer DMA IP
support video memory formats that are not represented in the
current DRM fourcc library. This patch adds those missing
fourcc codes.
Signed-off-by: Jeffrey Mouroux
Signed-off-by: Hyun Kwon
---
include/uapi/drm/d
Hi,
This series is to add new drm formats needed by some Xilinx IPs.
Some formats have unique characteristics such as pixels not being
byte-aligned. For instance, some 10bit formats have 2bit padding
after every 3-10bit components:
32b[0]: 10b comp0 - 10b comp1 - 10b comp2 - 2b padding
From: Satish Kumar Nagireddy
'cpp_scale' can be used as a multiplying factor to calculate
bytes per component based on color format.
For eg. scaling factor of YUV420 8 bit format is 1
so multiplying factor is 1 (8/8)
scaling factor of YUV420 10 bit format is 1.25 (10/8)
'padding_
tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next
head: f3769c94f4e6a794dbb72601936199d9b258f7b7
commit: 67e032a0a9a8e26db6960aae59e7a319ac900f95 [417/475] drm/ttm: add context
to driver move callback as well
config: i386-allmodconfig (attached as .config)
compiler: gcc-
Hi Brian,
Below comments fixed in
patch-v2：https://patchwork.kernel.org/patch/10078527/
but ："get_drvdata()"
Thanks for review.
Nickey.
On 2017年11月28日 09:51, Brian Norris wrote:
Hi Nickey,
Several people already made comments on the initial version of this
patch [1], and I don't think you'
https://bugs.freedesktop.org/show_bug.cgi?id=103949
Bug ID: 103949
Summary: REG_WAIT timeout - dce110_stream_encoder_dp_blank
line:930 - 4.15-rc1
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: Li
https://bugs.freedesktop.org/show_bug.cgi?id=103949
--- Comment #1 from Barry G ---
Created attachment 135744
--> https://bugs.freedesktop.org/attachment.cgi?id=135744&action=edit
Xorg.0.log file
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=103808
--- Comment #8 from Shmerl ---
Marek pushed this fix:
https://cgit.freedesktop.org/mesa/mesa/commit/?id=b5444877c0820b7848c07d1bc4e9a706f90894a5
I've just tested it with The Witcher 3 in Wine, and flickering is gone along
with performance drop!
Hi Nickey,
Thanks for the quick version 2. You've fixed most of the the problems I
pointed out, but you've missed at least one.
On Tue, Nov 28, 2017 at 09:55:24AM +0800, Nickey Yang wrote:
> Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare
> MIPI DSI host controller bridge
This looks okay to me.
Reviewed-by: Sinclair Yeh
On Thu, Nov 23, 2017 at 09:05:00PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Use drm_mode_get_hv_timing() to fill out the plane clip rectangle.
>
> Note that this replaces crtc_state->adjusted_mode usage with
> crtc_state->mode. The
Is it better to enable SWIOTLB? Are there any advantages with SWIOTLB enabled?
— Christian
Sent from my iPhone
> On 27. Nov 2017, at 15:53, Michel Dänzer wrote:
>
>> On 2017-11-27 01:17 PM, Tom St Denis wrote:
>>> On 27/11/17 07:02 AM, Michel Dänzer wrote:
On 2017-11-27 12:50 PM, Christia
Hi Linus,
I sent this last week as a follow on to the one you pulled, the tag
hasn't changed but the pull request has as you pulled the old tag.
This has a TTM regression fix for some virt gpus (bochs vga), a few
i915 stable fixes,
one vc4 fix, one uapi fix.
Dave.
The following changes since co
On 11/28/2017 06:35 AM, Brian Norris wrote:
Bridge drivers/helpers shouldn't be clobbering the drvdata, since a
parent driver might need to own this. Instead, let's return our
'dw_mipi_dsi' object and have callers pass that back to us for removal.
Reviewed-by: Archit Taneja
Signed-off-by:
Hi,
Thanks a lot for working on this. Some comments below.
On 11/28/2017 07:25 AM, Nickey Yang wrote:
Add the ROCKCHIP DSI controller driver that uses the Synopsys DesignWare
MIPI DSI host controller bridge.
Signed-off-by: Nickey Yang
---
drivers/gpu/drm/rockchip/Kconfig|
>> It seems that I got no responses so far for clarification requests
>> according to the documentation in a direction I hoped for.
>
> That's because you are pretty unresponsive to direction.
From which places did you get this impression?
> You've gotten _many_ replies to your patches
I got t
201 - 246 of 246 matches
Mail list logo
