On 01/10/2018 02:02 AM, Brian Norris wrote:
This takes care of 2 TODOs in this driver, by using the common DSI
packet-marshalling code instead of our custom short/long write code.
This both saves us some duplicated code and gets us free support for
command types that weren't already part of our
On 01/10/2018 08:03 PM, Andrzej Hajda wrote:
On 09.01.2018 21:32, Brian Norris wrote:
We're filling the "remainder" word with little-endian data, then writing
it out to IO registers with endian-correcting writel(). That probably
won't work on big-endian systems.
Let's mark the "remainder" var
-Original Message-
From: Andrey Grodzovsky [mailto:andrey.grodzov...@amd.com]
Sent: Saturday, January 13, 2018 6:29 AM
To: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org
Cc: Koenig, Christian ; He, Roger
; Grodzovsky, Andrey
Subject: [PATCH 2/2] drm/amdgpu: Use new TTM f
-Original Message-
From: Andrey Grodzovsky [mailto:andrey.grodzov...@amd.com]
Sent: Saturday, January 13, 2018 6:29 AM
To: dri-devel@lists.freedesktop.org; amd-...@lists.freedesktop.org
Cc: Koenig, Christian ; He, Roger
; Grodzovsky, Andrey
Subject: [PATCH 1/2] drm/ttm: Allow page allo
Hi Thierry,
On Tue, Jan 16, 2018 at 2:16 AM, Thierry Escande
wrote:
> From: Tomasz Figa
>
> Currently PSR flush is triggered from CRTC's .atomic_begin() callback,
> which is executed after modeset disables and enables and before plane
> updates are committed. Since PSR flush and re-enable can be
Hi Thierry,
On Tue, Jan 16, 2018 at 2:15 AM, Thierry Escande
wrote:
> From: Tomasz Figa
>
> Current code implements prepare_fb and cleanup_fb callbacks only to
> grab/release fb references, which is already done by atomic framework
> when creating/destryoing plane state.
AFAICT this is already
https://bugs.freedesktop.org/show_bug.cgi?id=104599
--- Comment #6 from Mario Kleiner ---
(In reply to Tapani Pälli from comment #4)
> (In reply to Mario Kleiner from comment #3)
> > This is running the new GNOME based Ubuntu GUI with Gnome-Shell Wayland,
> > right?
> >
> > With "Windows control
Unfortunately no. in order to support reclocking on Fermi with powergating
(which is important; since you can't test clockgating very well without it) we
are going to need to do some more investigation. Unlike Kepler and later
generations, Fermi seems to require some extra maintanence of it's clock
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--- Comment #7 from mikhail.v.gavri...@gmail.com ---
Created attachment 136745
--> https://bugs.freedesktop.org/attachment.cgi?id=136745&action=edit
dmesg with 4.15.0-rc2 amd-staging-drm-next
--
You are receiving this mail because:
You are th
otherwise -ETIME is missed.
Change-Id: Ic5580a74d8027cc468c6135f8cf2f81817993423
Signed-off-by: Chunming Zhou
---
xf86drm.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/xf86drm.c b/xf86drm.c
index 8a327170..3881bd9f 100644
--- a/xf86drm.c
+++ b/xf86drm.c
@@ -4241,7 +4241,7
Hi Thierry,
On Tue, Jan 16, 2018 at 2:16 AM, Thierry Escande
wrote:
> From: Tomasz Figa
>
> Current implementation of unbind dereferences the drvdata pointer
> assuming that it's its own data, however the ownership belongs to the
> analogix code, which means that the pointer is dereferenced with
This is a wrapper around the ZynqMP Display and DisplayPort drivers.
Signed-off-by: Hyun Kwon
---
- Change the SPDX identifier format
---
---
drivers/gpu/drm/xlnx/Kconfig| 11 +++
drivers/gpu/drm/xlnx/Makefile | 3 +
drivers/gpu/drm/xlnx/zynqmp_dpsub.c | 149
This driver creates DRM encoder and connector for ZynqMP DisplayPort.
Signed-off-by: Hyun Kwon
---
v2
- Change the SPDX identifier format
- Split drm properties into a separate patch
---
---
drivers/gpu/drm/xlnx/zynqmp_dp.c | 1738 ++
drivers/gpu/drm/xlnx/zynq
Xilinx ZynqMP has a hardened display pipeline. The pipeline can
be logically partitioned into 2 parts: display controller and
DisplayPort encoder / transmitter. This driver handles the display
controller part of the pipeline that handles buffer management and
blending.
Signed-off-by: Hyun Kwon
--
Add drm properties for DisplayPort synchronous mode and bpc
configurations.
Signed-off-by: Hyun Kwon
---
v2
- Split from the original patch
---
---
drivers/gpu/drm/xlnx/zynqmp_dp.c | 116 ++-
1 file changed, 114 insertions(+), 2 deletions(-)
diff --git a/driv
Add drm properties for global alpha, output color, background color,
and test pattern generation.
Signed-off-by: Hyun Kwon
---
v2
- Split from the original patch
- Some props are important feature to be included
---
---
drivers/gpu/drm/xlnx/zynqmp_disp.c | 191 +++
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/xlnx,zynqmp-dpsub.txt| 98 ++
1 file changed, 98 inserti
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
- Remove linux specific terms
- Elaborate details, ex regarding port binding
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 on the chip. Furthermore,
hardened pipeline can also interact with soft logics in FPGA.
The Xilinx DRM KMS is to integrate multiple subd
在 2018/1/9 18:56, Maxime Ripard 写道:
Now that the core has a drm format helper to tell if a format embeds an
alpha component in it, let's use it.
Cc: Mark Yao
Signed-off-by: Maxime Ripard
---
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 13 +
1 file changed, 1 insertion(+), 12 d
That's right, there's still more power saving to go! This enables the
third level of clockgating, SLCG (this stands for... we don't actually
know what this stands for yet :\). While the register values look a
little different, programming them is exactly the same as BLCG.
Additionally, it should be
This is mostly the same as Kepler1, but we save even more power!
Signed-off-by: Lyude Paul
---
drivers/gpu/drm/nouveau/include/nvkm/subdev/fb.h | 1 +
drivers/gpu/drm/nouveau/nvkm/engine/device/base.c | 8 +--
drivers/gpu/drm/nouveau/nvkm/engine/gr/gk110.c| 68
driver
This enables the second level of clockgating for Kepler1: BLCG
(presumably, this stands for block-level clockgating). This is a deeper
level of power savings then just CG_CTRL. Setting it up is as simple as
loading some mmio packs, and turning it on and off is still controlled
through CG_CTRL.
We
This adds support for enabling automatic clockgating on nvidia GPUs for
Kepler1, referred to as "CG" throughout the driver. This is one of two
powersaving levels that Kepler1 supports.
This introduces two therm helpers for controlling basic clockgating:
nvkm_therm_clkgate_enable() - enable
It's here! After a lot of investigation, rewrites, and traces, I present
the patch series to implement all known levels of clockgating for
Kepler1 and Kepler2 GPUs.
Starting with Fermi GPUs (this is probably present on earlier GPUs as
well, but with a far less easy to manage interface), nvidia add
On 01/15/2018 11:32 PM, Laurent Pinchart wrote:
The LVDS encoders used to be described in DT as part of the DU. They now
have their own DT node, linked to the DU using the OF graph bindings.
This allows moving internal LVDS encoder support to a separate driver
modelled as a DRM bridge. Backward
Hi Sergei,
On Monday, 15 January 2018 22:25:16 EET Sergei Shtylyov wrote:
> On 01/13/2018 02:14 AM, Laurent Pinchart wrote:
> > The LVDS encoders used to be described in DT as part of the DU. They now
> > have their own DT node, linked to the DU using the OF graph bindings.
> > This allows moving
Hi Frank,
On Monday, 15 January 2018 22:12:33 EET Frank Rowand wrote:
> On 01/15/18 11:22, Laurent Pinchart wrote:
> > On Monday, 15 January 2018 21:12:44 EET Frank Rowand wrote:
> >> On 01/15/18 09:09, Rob Herring wrote:
> >>> +Frank
> >>>
> >>> On Fri, Jan 12, 2018 at 5:14 PM, Laurent Pinchart
Hello!
On 01/13/2018 02:14 AM, Laurent Pinchart wrote:
The LVDS encoders used to be described in DT as part of the DU. They now
have their own DT node, linked to the DU using the OF graph bindings.
This allows moving internal LVDS encoder support to a separate driver
modelled as a DRM bridge. B
Hi Frank,
On Monday, 15 January 2018 21:12:44 EET Frank Rowand wrote:
> On 01/15/18 09:09, Rob Herring wrote:
> > +Frank
> >
> > On Fri, Jan 12, 2018 at 5:14 PM, Laurent Pinchart wrote:
> >> The internal LVDS encoders now have their own DT bindings. Before
> >> switching the driver infrastructure
https://bugs.freedesktop.org/show_bug.cgi?id=104603
Adam Jackson changed:
What|Removed |Added
Assignee|dri-devel@lists.freedesktop |intel-3d-bugs@lists.freedes
https://bugs.freedesktop.org/show_bug.cgi?id=104603
--- Comment #1 from Adam Jackson ---
A lot of it is xscreensaver, which still thinks glVertex3f is a great way to
upload geometry, which is why basically all its glx hacks are CPU-bound with
Mesa. In this particular case (at least on the haswell
Hi Rob,
(CC'ing Geert)
On Monday, 15 January 2018 19:09:53 EET Rob Herring wrote:
> +Frank
>
> On Fri, Jan 12, 2018 at 5:14 PM, Laurent Pinchart wrote:
> > The internal LVDS encoders now have their own DT bindings. Before
> > switching the driver infrastructure to those new bindings, implement
>
Function should constantly check if cable is connected and finish
in finite time.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/sil-sii8620.c | 31 ---
1 file changed, 20 insertions(+), 11 deletions(-)
diff --git a/drivers/gpu/drm/bridge/sil-sii8620.c
b/dr
Chip has known bug which causes I2C client state machine to frequently
enter non-idle mode after chip reset. Let's ask I2C adapter to perform
bus recovery to mitigate this bug.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/sil-sii8620.c | 5 +
1 file changed, 5 insertions(+)
diff
Hi all,
The patchset contains few fixes for sii8620 driver.
I2C recovery will be effective only if I2C adapter support I2C recovery,
patches for HSI2C (I2C adapter used by sii8620 device on TM2/TM2e platforms)
are already sent [1].
[1]: https://marc.info/?l=linux-i2c&m=151205223005257
Regards
An
There is no need to flip reset pin twice. Also delays can be changed to
values present in vendor's code.
Signed-off-by: Andrzej Hajda
---
drivers/gpu/drm/bridge/sil-sii8620.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/bridge/sil-sii8620.c
b/drive
On 15.01.2018 15:40, Philippe CORNU wrote:
> Hi Andrzej,
>
> On 01/15/2018 02:52 PM, Andrzej Hajda wrote:
>> On 12.01.2018 17:25, Philippe Cornu wrote:
>>> The pixel clock is optional. When available, it offers a better
>>> preciseness for timing computations and allows to reduce the extra dsi
>>>
+Frank
On Fri, Jan 12, 2018 at 5:14 PM, Laurent Pinchart
wrote:
> The internal LVDS encoders now have their own DT bindings. Before
> switching the driver infrastructure to those new bindings, implement
> backward-compatibility through live DT patching.
Uhh, we just got rid of TI's patching and
On Mon, 15 Jan 2018, Bartlomiej Zolnierkiewicz wrote:
> On Friday, January 05, 2018 04:42:58 PM Nicolas Pitre wrote:
> >
> > When this method is set, the caller expects struct console_font fields
> > to be properly initialized when it returns. Leave it unset otherwise
> > nonsensical (leaked kern
https://bugs.freedesktop.org/show_bug.cgi?id=104624
--- Comment #1 from Harry Wentland ---
(In reply to Vedran Miletić from comment #0)
> This is a regression, DOOM used to work.
Are you able to bisect?
--
You are receiving this mail because:
You are the assignee for the bug.__
When NVMEM is configured as a loadable module, and adreno
is built-in, we get a link failure:
drivers/gpu/drm/msm/adreno/a5xx_gpu.o: In function `a5xx_gpu_init':
a5xx_gpu.c:(.text+0x15cc): undefined reference to `nvmem_cell_get'
a5xx_gpu.c:(.text+0x15da): undefined reference to `nvmem_cell_read'
a
Quoting Hans de Goede (2018-01-15 15:56:26)
> Hi,
>
> On 15-01-18 16:48, Chris Wilson wrote:
> > Commit 404d1a3edc38 ("drm: Add panel orientation quirks, v6.")
> > introduced a new internal Kconfig option for DRM and placed in the
> > middle of the DRM option sequence without including a depends o
Using a Kconfig 'select' statement for a user-visible symbol that other
drivers depend on often causes circular dependencies. A new one showed
up when I wanted to add an NVMEM dependency to the DRM_MSM driver:
drivers/i2c/Kconfig:7:error: recursive dependency detected!
drivers/i2c/Kconfig:7: symb
https://bugs.freedesktop.org/show_bug.cgi?id=104611
--- Comment #1 from Harry Wentland ---
Does this reproduce consistently or intermittently?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-deve
Hi,
On 15-01-18 16:48, Chris Wilson wrote:
Commit 404d1a3edc38 ("drm: Add panel orientation quirks, v6.")
introduced a new internal Kconfig option for DRM and placed in the
middle of the DRM option sequence without including a depends on DRM.
This has the unfortunate side-effect of breaking the
Commit 404d1a3edc38 ("drm: Add panel orientation quirks, v6.")
introduced a new internal Kconfig option for DRM and placed in the
middle of the DRM option sequence without including a depends on DRM.
This has the unfortunate side-effect of breaking the DRM menuconfig to
not include the existing DRM
On Tue, Jan 09, 2018 at 02:28:33PM +0100, Maxime Ripard wrote:
> Hi Laurent,
>
> On Tue, Jan 09, 2018 at 02:29:58PM +0200, Laurent Pinchart wrote:
> > On Tuesday, 9 January 2018 12:56:20 EET Maxime Ripard wrote:
> > > There's a bunch of drivers that duplicate the same function to know if a
> > > pa
On Wednesday, January 10, 2018 05:36:32 PM Arnd Bergmann wrote:
> Kbuild complains about the lack of a license tag in this driver:
>
> WARNING: modpost: missing MODULE_LICENSE() in
> drivers/video/fbdev/mmp/mmp_disp.o
>
> This adds the license, author and description tags.
>
> Signed-off-by: Ar
On Mon, Jan 15, 2018 at 10:01 AM, Lloyd Atkinson
wrote:
> On 1/15/2018 9:48 AM, Rob Clark wrote:
>> On Fri, Jan 12, 2018 at 3:55 PM, Lloyd Atkinson
>> wrote:
>>> Move null checks of pointer arguments to the beginning of the
>>> modeset init function since they are referenced immediately
>>> inst
On 12/01/2018 21:42, Jernej Škrabec wrote:
> Hi all,
>
> Dne sreda, 10. januar 2018 ob 20:25:04 CET je Jernej Skrabec napisal(a):
>> Parts of PHY code could be useful also for custom PHYs. For example,
>> Allwinner A83T has custom PHY which is probably Synopsys gen2 PHY
>> with few additional memo
On Friday, January 05, 2018 04:42:58 PM Nicolas Pitre wrote:
>
> When this method is set, the caller expects struct console_font fields
> to be properly initialized when it returns. Leave it unset otherwise
> nonsensical (leaked kernel stack) values are returned to user space.
>
> Signed-off-by:
On 1/15/2018 9:48 AM, Rob Clark wrote:
> On Fri, Jan 12, 2018 at 3:55 PM, Lloyd Atkinson
> wrote:
>> Move null checks of pointer arguments to the beginning of the
>> modeset init function since they are referenced immediately
>> instead of after they have already been used.
>>
>> Signed-off-by: L
https://bugs.freedesktop.org/show_bug.cgi?id=104639
--- Comment #1 from Michel Dänzer ---
Can you try bisecting? Make sure to test each commit for plenty of time before
marking it as good.
--
You are receiving this mail because:
You are the assignee for the bug._
On Fri, Jan 12, 2018 at 3:55 PM, Lloyd Atkinson wrote:
> Move null checks of pointer arguments to the beginning of the
> modeset init function since they are referenced immediately
> instead of after they have already been used.
>
> Signed-off-by: Lloyd Atkinson
> ---
> drivers/gpu/drm/msm/dsi/d
On Fri, Jan 12, 2018 at 3:55 PM, Lloyd Atkinson wrote:
> Check DSI instance id argument against the proper boundary size
> to protect against invalid configuration of the DSI id.
>
> Signed-off-by: Lloyd Atkinson
> ---
> drivers/gpu/drm/msm/dsi/dsi_manager.c | 2 +-
> 1 file changed, 1 insertion
Hi Andrzej,
On 01/15/2018 02:52 PM, Andrzej Hajda wrote:
> On 12.01.2018 17:25, Philippe Cornu wrote:
>> The pixel clock is optional. When available, it offers a better
>> preciseness for timing computations and allows to reduce the extra dsi
>> bandwidth in burst mode (from ~20% to ~10-12%, hw pl
On Fri, Jan 12, 2018 at 3:55 PM, Lloyd Atkinson wrote:
> Add checks for failure after retrieving the src_pll, since it
> may fail. This prevents an invalid pointer dereference later in
> msm_dsi_pll_get_clk_provider.
>
> Signed-off-by: Lloyd Atkinson
> ---
> drivers/gpu/drm/msm/dsi/dsi_manager.c
Den 10.01.2018 19.59, skrev Noralf Trønnes:
Fix a few things that came up during the tinydrm review but wasn't
addressed at the time.
Noralf.
Thanks for review and testing, series applied to drm-misc.
Noralf.
Changes since version 2:
- s/mipi_dbi_por_conditional/mipi_dbi_poweron_reset_cond
On Mon, 15 Jan 2018, Thierry Reding wrote:
> On Mon, Jan 15, 2018 at 01:47:07PM +0100, Julia Lawall wrote:
> > From: Fengguang Wu
> >
> > Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
> > drm_*_unreference() helpers.
> >
> > Generated by: scripts/coccinelle/api/drm-ge
Quoting Thierry Reding (2018-01-12 16:04:22)
> On Fri, Jan 12, 2018 at 03:38:56PM +, Chris Wilson wrote:
> > Quoting Thierry Reding (2018-01-12 15:14:38)
> > > On Fri, Jan 12, 2018 at 10:40:16AM +, Chris Wilson wrote:
> > > > Quoting Thierry Reding (2018-01-11 22:22:46)
> > > > > From: Thie
On 12.01.2018 17:25, Philippe Cornu wrote:
> The pixel clock is optional. When available, it offers a better
> preciseness for timing computations and allows to reduce the extra dsi
> bandwidth in burst mode (from ~20% to ~10-12%, hw platform dependent).
>
> Signed-off-by: Philippe Cornu
> ---
> C
On Mon, Jan 15, 2018 at 01:47:07PM +0100, Julia Lawall wrote:
> From: Fengguang Wu
>
> Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
> drm_*_unreference() helpers.
>
> Generated by: scripts/coccinelle/api/drm-get-put.cocci
>
> Signed-off-by: Fengguang Wu
> Signed-off
Hi Andrzej,
On 01/15/2018 10:12 AM, Andrzej Hajda wrote:
> On 12.01.2018 15:48, Philippe Cornu wrote:
>> The function mipi_dsi_device_transfer() returns the number of transmitted
>> or received bytes on success or a negative error code on failure.
>>
>> The functions mipi_dsi_shutdown_peripheral()
https://bugs.freedesktop.org/show_bug.cgi?id=104639
Bug ID: 104639
Summary: kernel 4.15-rc8 reboots randomly with RX 560
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
From: Fengguang Wu
Use drm_*_get() and drm_*_put() helpers instead of drm_*_reference() and
drm_*_unreference() helpers.
Generated by: scripts/coccinelle/api/drm-get-put.cocci
Signed-off-by: Fengguang Wu
Signed-off-by: Julia Lawall
---
tree: https://github.com/thierryreding/linux for-4.16/
Hi Dave,
a couple of minor fixes for 4.16:
- fix NULL pointer dereference
- fix compiler warning on large define values
- remove unnecessary call to execute_queues_cpsch
Thanks,
Oded
The following changes since commit 9be712ef4612268c28b9f1e2d850d3ceab06ef66:
Merge tag 'drm/tegra/for-4.16-rc
Hello!
On 01/13/2018 02:14 AM, Laurent Pinchart wrote:
The internal LVDS encoder now has DT bindings separate from the DU. Port
the device tree over to the new model.
Signed-off-by: Laurent Pinchart
[...]
diff --git a/arch/arm/boot/dts/r8a7790.dtsi b/arch/arm/boot/dts/r8a7790.dtsi
index 62b
Hello!
On 01/13/2018 02:14 AM, Laurent Pinchart wrote:
The internal LVDS encoder now has DT bindings separate from the DU. Port
the device tree over to the new model.
Signed-off-by: Laurent Pinchart
[...]
diff --git a/arch/arm/boot/dts/r8a7791.dtsi b/arch/arm/boot/dts/r8a7791.dtsi
index 678
https://bugs.freedesktop.org/show_bug.cgi?id=104599
--- Comment #5 from zebulon ---
I can't help you anymore. I removed oibaf repo and switch back to original
ubuntu driver.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=99321
neel84...@gmail.com changed:
What|Removed |Added
Resolution|FIXED |NOTABUG
--
You are receiving this
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, buts per pixel and memory port
width. The device tree binding only supports
From: Ong, Hean Loong
The FPGA FrameBuffer Soft IP could be seen as the GPU and the DRM driver patch
here is allocating memory for information to be streamed from the ARM/Linux to
the display port.
Basically the driver just wraps the information such as the pixels to be drawn
by the FPGA Fram
From: Ong Hean Loong
Driver for Intel FPGA Video and Image Processing Suite Frame Buffer II.
The driver only supports the Intel Arria10 devkit and its variants.
This driver can be either loaded staticlly or in modules.
The OF device tree binding is located at:
Documentation/devicetree/bindings/di
From: Ong Hean Loong
Intel FPGA Video and Image Processing Suite Frame Buffer II
driver config for Arria 10 devkit and its variants
Signed-off-by: Ong, Hean Loong
---
arch/arm/configs/socfpga_defconfig |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/config
On 14/01/18 21:07, Wolfram Sang wrote:
The documentation was wrong, gpiod_get_direction() returns 0/1 instead
of the GPIOF_* flags. The docs were fixed with commit 94fc73094abe47
("gpio: correct docs about return value of gpiod_get_direction"). Now,
fix this user (until a better, system-wide so
https://bugs.freedesktop.org/show_bug.cgi?id=104608
--- Comment #2 from Michel Dänzer ---
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e97f12f359775de4fabfb507f836ebffa20f4986
should help for this.
--
You are receiving this mail because:
You are the assignee for
On Mon, Jan 15, 2018 at 11:47:59AM +0800, Shawn Guo wrote:
> The structure should really be sw_sync_create_fence_data rather than
> sw_sync_ioctl_create_fence which is the function name.
>
> Signed-off-by: Shawn Guo
Applied, thanks for your patch.
-Daniel
> ---
> drivers/dma-buf/sw_sync.c | 4
On Fri, Jan 12, 2018 at 01:57:07PM -0800, 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 counter also could have stalled if PSR is active in cases
> wh
On Fri, Jan 12, 2018 at 01:57:03PM -0800, 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 requested vblank sequence using this clipped 32-bit count(when the
>
https://bugs.freedesktop.org/show_bug.cgi?id=104631
Michel Dänzer changed:
What|Removed |Added
Component|libdrm |New Accounts
Assignee|dri-dev
On Fri, Jan 12, 2018 at 12:09:39AM +0200, Laurent Pinchart wrote:
> Hi Maxime,
>
> On Friday, 12 January 2018 00:06:06 EET Laurent Pinchart wrote:
> > On Thursday, 11 January 2018 15:12:56 EET Maxime Ripard wrote:
> > > On Thu, Jan 11, 2018 at 03:05:01PM +0200, Laurent Pinchart wrote:
> > >> On We
On 12.01.2018 15:48, Philippe Cornu wrote:
> The function mipi_dsi_device_transfer() returns the number of transmitted
> or received bytes on success or a negative error code on failure.
>
> The functions mipi_dsi_shutdown_peripheral(), mipi_dsi_turn_on_peripheral() &
> mipi_dsi_set_maximum_return_
We accidentally passed the wrong variable to PTR_ERR().
Fixes: a0c1214e4764 ("drm/sun4i: Add LVDS support")
Signed-off-by: Dan Carpenter
diff --git a/drivers/gpu/drm/sun4i/sun4i_tcon.c
b/drivers/gpu/drm/sun4i/sun4i_tcon.c
index b78fed809992..3c15cf24b503 100644
--- a/drivers/gpu/drm/sun4i/sun4i
On Mon, Jan 15, 2018 at 11:11:13AM +0300, Dan Carpenter wrote:
> We accidentally passed the wrong variable to PTR_ERR().
>
> Fixes: a0c1214e4764 ("drm/sun4i: Add LVDS support")
> Signed-off-by: Dan Carpenter
Applied, thanks!
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel eng
Hi Geert,
On Monday, 15 January 2018 10:30:23 EET Geert Uytterhoeven wrote:
> On Sat, Jan 13, 2018 at 12:14 AM, Laurent Pinchart wrote:
> > The LVDS encoders used to be described in DT as part of the DU. They now
> > have their own DT node, linked to the DU using the OF graph bindings.
> > This al
Hi Laurent,
On Sat, Jan 13, 2018 at 12:14 AM, Laurent Pinchart
wrote:
> The LVDS encoders used to be described in DT as part of the DU. They now
> have their own DT node, linked to the DU using the OF graph bindings.
> This allows moving internal LVDS encoder support to a separate driver
> modell
Hi Geert,
On Monday, 15 January 2018 10:05:59 EET Geert Uytterhoeven wrote:
> On Mon, Jan 15, 2018 at 7:59 AM, Laurent Pinchart wrote:
> > On Monday, 15 January 2018 08:55:29 EET Simon Horman wrote:
> >> On Fri, Jan 12, 2018 at 03:29:48PM +0200, Laurent Pinchart wrote:
> >>> On Friday, 12 January
On Fri, Jan 12, 2018 at 03:48:25PM +0200, Laurent Pinchart wrote:
> Hi Geert,
>
> On Friday, 12 January 2018 11:47:03 EET Geert Uytterhoeven wrote:
> > On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > > This patch series addresses a design mistake that dates back from the
> > > initial
On Fri, Jan 12, 2018 at 02:58:48AM +0200, Laurent Pinchart wrote:
> Hello,
>
> This patch series addresses a design mistake that dates back from the initial
> DU support. Support for the LVDS encoders, which are IP cores separate from
> the DU, was bundled in the DU driver. Worse, both the DU and
On Fri, Jan 12, 2018 at 02:58:53AM +0200, Laurent Pinchart wrote:
> The HDMI encoder is connected to the RGB output of the DU, which is
> port@0, not port@1. Fix the incorrect DT description.
>
> Signed-off-by: Laurent Pinchart
Should this have the following tag?
Fixes: c5af8a4248d3 ("ARM: dts:
The documentation was wrong, gpiod_get_direction() returns 0/1 instead
of the GPIOF_* flags. The docs were fixed with commit 94fc73094abe47
("gpio: correct docs about return value of gpiod_get_direction"). Now,
fix this user (until a better, system-wide solution is in place).
Signed-off-by: Wolfra
Hi Simon,
On Monday, 15 January 2018 09:56:03 EET Simon Horman wrote:
> On Fri, Jan 12, 2018 at 02:58:53AM +0200, Laurent Pinchart wrote:
> > The HDMI encoder is connected to the RGB output of the DU, which is
> > port@0, not port@1. Fix the incorrect DT description.
> >
> > Signed-off-by: Lauren
On Fri, Jan 12, 2018 at 03:29:48PM +0200, Laurent Pinchart wrote:
> Hi Geert,
>
> On Friday, 12 January 2018 12:13:18 EET Geert Uytterhoeven wrote:
> > On Fri, Jan 12, 2018 at 1:58 AM, Laurent Pinchart wrote:
> > > The Renesas R-Car Gen2 and Gen3 SoCs have internal LVDS encoders. Add
> > > corresp
On Mon, Jan 15, 2018 at 08:59:38AM +0200, Laurent Pinchart wrote:
> Hi Simon,
>
> On Monday, 15 January 2018 08:55:29 EET Simon Horman wrote:
> > On Fri, Jan 12, 2018 at 03:29:48PM +0200, Laurent Pinchart wrote:
> > > On Friday, 12 January 2018 12:13:18 EET Geert Uytterhoeven wrote:
> > >> On Fri,
On Mon, Jan 15, 2018 at 09:00:59AM +0200, Laurent Pinchart wrote:
> Hi Simon,
>
> On Monday, 15 January 2018 08:57:48 EET Simon Horman wrote:
> > On Fri, Jan 12, 2018 at 03:48:25PM +0200, Laurent Pinchart wrote:
> > > On Friday, 12 January 2018 11:47:03 EET Geert Uytterhoeven wrote:
> > >> On Fri,
The documentation was wrong, gpiod_get_direction() returns 0/1 instead of the
GPIOF_* flags. The docs were fixed with commit 94fc73094abe47 ("gpio: correct
docs about return value of gpiod_get_direction"). Now, fix the users who got it
as wrong as I did when developing bus recovery for the R-Car I2
Hi Laurent,
On Mon, Jan 15, 2018 at 7:59 AM, Laurent Pinchart
wrote:
> On Monday, 15 January 2018 08:55:29 EET Simon Horman wrote:
>> On Fri, Jan 12, 2018 at 03:29:48PM +0200, Laurent Pinchart wrote:
>> > On Friday, 12 January 2018 12:13:18 EET Geert Uytterhoeven wrote:
>> >> As this is a new bin
98 matches
Mail list logo
