On Fri, Jan 26, 2018 at 02:16:47PM +0100, Thierry Escande wrote:
> From: Lin Huang
>
> There was a 1ms delay to detect the hpd signal, which is too short to
> detect a short pulse. This patch extends this delay to 100ms.
The commit message doesn't align with the code here.
That's right, there's still more power saving to go! Starting with
kepler 2, nvidia hardware has an additional level of clockgating known
as second level clockgating. The details of this are not exact, but it
seems to work by waiting for a collection of dependent hardware blocks
to be gated
This adds the NvPmEnableGating config option to nouveau, which can be
used to enable or disable clockgating for supported chipsets. Enabling
can be done by passing
config=NvPmEnableGating=1
To nouveau. If your chipset supports it, you'll see a message in your
kernel log indicating that
Same as the previous patch, but for Kepler2 now
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| 62
The series is Reviewed-by: Felix Kuehling
Regards,
Felix
On 2018-01-29 08:55 AM, Tom St Denis wrote:
> Various TTM cleanups (mostly no functional changes).
>
> Notably patch #1 fixes a bug in the access_kmap() function.
>
> The rest are either coding style fixes or
On Fri, Jan 26, 2018 at 02:16:51PM +0100, Thierry Escande wrote:
> From: Lin Huang
>
> AUX errors are caused by many different reasons. We may not know what
> happened in aux channel on failure, so let's reset aux channel if some
> errors occurred.
>
> Cc: 征增 王
This enables BLCG optimization for kepler1. When using clockgating,
nvidia's firmware has a set of registers which are initially programmed
by the vbios with various engine delays and other mysterious settings
that are safe enough to bring up the GPU. However, the values used by
the vbios are more
Next version of my patchseries for adding clockgating support for
kepler1 and 2 on nouveau. The first version of this series can be found
here:
https://patchwork.freedesktop.org/series/36504/
One small change:
- Set therm->clkgate_enabled to false until the last patch, where we
introduce the
This adds support for enabling automatic clockgating on nvidia GPUs for
Kepler1. While this is not technically a clockgating level, it does
enable clockgating using the clockgating values initially set by the
vbios (which should be safe to use).
This introduces two therm helpers for controlling
On 01/29/2018 10:02 PM, Rob Herring wrote:
>> Document the R-Car V3M (R8A77970) SoC in the R-Car DU bindings.
>>
>> Signed-off-by: Sergei Shtylyov
>>
>> ---
>> Changes in version 2:
>> - documented R8A77970 DU ports;
>> - patch split from the main R8A77970 DU
On Fri, Jan 19, 2018 at 09:29:20PM +0300, Sergei Shtylyov wrote:
> 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
On Thu, Jan 18, 2018 at 10:23:54AM +0530, 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 bus at all. Add an example for a peripheral with a non-DSI
> control bus.
>
>
On Mon, Jan 22, 2018 at 12:49:56PM +, Kieran Bingham wrote:
> From: Jean-Michel Hautbois
>
> The ADV7604 has thirteen 256-byte maps that can be accessed via the main
> I²C ports. Each map has it own I²C address and acts as a standard slave
> device on the
On Mon, Jan 29, 2018 at 03:40:34PM -0500, Alex Deucher wrote:
> On Mon, Jan 29, 2018 at 3:34 PM, wrote:
> > As far as I can remember, not for the new features ofc, DCE programming for
> > GCN1
> > is very similar if not mostly the same than DCE programming for
On Mon, Jan 22, 2018 at 04:35:47PM +0100, Philippe Cornu wrote:
> In the dsi panel example, clock names in the "clock-names"
> field have been swapped:
> * "pclk" (peripheral clock) is < 1 CLK_F469_DSI> on stm32f4
> * "ref" (dsi phy pll ref clock) is <_hse> on stm32f4
>
> Signed-off-by: Philippe
On Fri, Jan 26, 2018 at 02:16:27PM +0100, Thierry Escande wrote:
> Hi,
>
> This patchset includes cleanups, improvements, and bug fixes for
> Rockchip DRM driver and PSR support.
>
> this patchset depends and needs to be applied on top of Rockchip rk3399
> eDP support [1].
>
> [1]
On Fri, Jan 26, 2018 at 02:16:49PM +0100, Thierry Escande wrote:
> From: Lin Huang
>
> We need to check the dpcd write/read return value to see whether the
> write/read was successful
>
> Cc: Kristian H. Kristensen
> Signed-off-by: Lin Huang
On Fri, Jan 26, 2018 at 02:16:55PM +0100, Thierry Escande wrote:
> From: zain wang
>
> Register ANALOGIX_DP_FUNC_EN_1(offset 0x18), Rockchip is different to
> Exynos:
>
> on Exynos edp phy,
> BIT 7 MASTER_VID_FUNC_EN_N
> BIT 6 reserved
> BIT 5
On Mon, Jan 29, 2018 at 5:35 PM, wrote:
> On Mon, Jan 29, 2018 at 03:40:34PM -0500, Alex Deucher wrote:
>> On Mon, Jan 29, 2018 at 3:34 PM, wrote:
>> > As far as I can remember, not for the new features ofc, DCE programming
>> > for GCN1
On Mon, Jan 29, 2018 at 04:14:41PM -0500, Sean Paul wrote:
> On Fri, Jan 26, 2018 at 02:16:49PM +0100, Thierry Escande wrote:
> > From: Lin Huang
> >
> > We need to check the dpcd write/read return value to see whether the
> > write/read was successful
> >
> > Cc: Kristian
On Fri, Jan 26, 2018 at 02:16:56PM +0100, Thierry Escande wrote:
> From: zain wang
>
> It's too early to detect fast link training, if other step after it
> failed, we will set fast_link flag to 1, and retry set_bridge again. In
> this case we will power down and power up
On Fri, Jan 26, 2018 at 02:17:04PM +0100, Thierry Escande wrote:
> From: "Kristian H. Kristensen"
>
> To improve PSR exit latency, we speculatively start exiting when we
> receive input events. Occasionally, this may lead to false positives,
> but most of the time we get a
On Fri, Jan 12, 2018 at 11:51:33AM +0530, Nautiyal, Ankit K wrote:
> From: Ankit Nautiyal
>
> If the user mode does not support aspect-ratio, and requests for
> a modeset, then the flag bits representing aspect ratio in the
> given user-mode must be rejected.
>
On Fri, Jan 19, 2018 at 12:05:58AM +0300, Sergei Shtylyov wrote:
> Document the R-Car V3M (R8A77970) SoC in the R-Car DU bindings.
>
> Signed-off-by: Sergei Shtylyov
>
> ---
> Changes in version 2:
> - documented R8A77970 DU ports;
> - patch split from the
On Tue, Nov 14, 2017 at 08:32:48PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> I recently realized that we're not validating the mode flags/type
> passed in from userspace. Let's try to fix that.
>
> I'd also like to entirely eliminate some of the more
On Thu, Jan 18, 2018 at 10:23:55AM +0530, Archit Taneja wrote:
> Add binding info for peripherals that support dual-channel DSI. Add
> corresponding optional bindings for DSI host controllers that may
> be configured in this mode. Add an example of an I2C controlled
> device operating in
On Mon, Jan 29, 2018 at 12:26:00PM +0200, Laurent Pinchart wrote:
> Hi Kieran,
>
> Thank you for the patch.
>
> On Monday, 22 January 2018 14:50:00 EET Kieran Bingham wrote:
> > The ADV7511 has four 256-byte maps that can be accessed via the main I²C
> > ports. Each map has it own I²C address
On Fri, Jan 26, 2018 at 02:16:28PM +0100, Thierry Escande wrote:
> From: Tomasz Figa
>
> This patch removes unused fields from vop structure.
>
> Signed-off-by: Tomasz Figa
> Signed-off-by: Sean Paul
> Signed-off-by: Thierry
On Mon, Jan 29, 2018 at 2:31 PM, wrote:
> On Mon, Jan 29, 2018 at 01:58:46PM -0500, Alex Deucher wrote:
>> It's similar, but there is still a bunch of DCE specific code. No one
>> has written that DC code for DCE 6 yet. One could use the DC DCE8
>> code as a guide,
On Mon, Jan 29, 2018 at 02:39:53PM -0500, Alex Deucher wrote:
> On Mon, Jan 29, 2018 at 2:31 PM, wrote:
> > On Mon, Jan 29, 2018 at 01:58:46PM -0500, Alex Deucher wrote:
> >> It's similar, but there is still a bunch of DCE specific code. No one
> >> has written that
On Fri, Jan 19, 2018 at 05:13:42PM +0530, Vivek Gautam wrote:
> 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
On Thu, Jan 18, 2018 at 10:23:54AM +0530, 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 bus at all. Add an example for a peripheral with a non-DSI
> control bus.
>
>
Hi Lee,
Here's the pull request for Meghana's patch set. It's based on 4.15, and just
contains the backlight portion of the set. I couldn't include the rest as it
depends on patches that only exist in drm-misc-next atm.
Thanks for coordinating with me on this!
On Wed, Jan 17, 2018 at 09:14:15PM +0100, Jernej Skrabec wrote:
> This commit adds all necessary compatibles and descriptions needed to
> implement A83T HDMI pipeline.
>
> Mixer is already properly described, so only compatible is added.
>
> However, A83T TV TCON, which is connected to HDMI,
On Mon, Jan 29, 2018 at 12:56 PM, wrote:
> Hi,
>
> I'm an owner of tahiti xt gpu, and I wonder what are the reasons the new
> display code is not available for gcn1 hardware?
No one has written the code.
Alex
___
dri-devel
On Mon, Jan 22, 2018 at 12:50:01PM +, Kieran Bingham wrote:
> The ADV7511 has four 256-byte maps that can be accessed via the main I²C
> ports. Each map has it own I²C address and acts as a standard slave
> device on the I²C bus.
>
> Allow a device tree node to override the default addresses
https://bugs.freedesktop.org/show_bug.cgi?id=103107
--- Comment #12 from Ricardo Perez ---
This tests continue failing on CFL QA
igt@gem_ctx_param@invalid-param-get
igt@gem_ctx_param@invalid-param-set
IGT-Version: 1.21-g37bd27f (x86_64) (Linux:
On Mon, Jan 29, 2018 at 01:04:08PM -0500, Alex Deucher wrote:
> On Mon, Jan 29, 2018 at 12:56 PM, wrote:
> > Hi,
> >
> > I'm an owner of tahiti xt gpu, and I wonder what are the reasons the new
> > display code is not available for gcn1 hardware?
>
> No one has
On Fri, Jan 12, 2018 at 11:51:34AM +0530, Nautiyal, Ankit K wrote:
> From: Ankit Nautiyal
>
> We parse the EDID and add all the modes in the connector's
> modelist. This adds CEA modes with aspect ratio information
> too, regadless of if user space requested this
On Mon, Jan 29, 2018 at 1:45 PM, wrote:
> On Mon, Jan 29, 2018 at 01:04:08PM -0500, Alex Deucher wrote:
>> On Mon, Jan 29, 2018 at 12:56 PM, wrote:
>> > Hi,
>> >
>> > I'm an owner of tahiti xt gpu, and I wonder what are the reasons the
On Mon, Jan 29, 2018 at 3:34 PM, wrote:
> On Mon, Jan 29, 2018 at 02:39:53PM -0500, Alex Deucher wrote:
>> On Mon, Jan 29, 2018 at 2:31 PM, wrote:
>> > On Mon, Jan 29, 2018 at 01:58:46PM -0500, Alex Deucher wrote:
>> >> It's similar, but
https://bugs.freedesktop.org/show_bug.cgi?id=104806
Matt Turner changed:
What|Removed |Added
Blocks||104757
Referenced
https://bugs.freedesktop.org/show_bug.cgi?id=104834
Jani Nikula changed:
What|Removed |Added
Component|General |DRM/Intel
Hi,
I'm an owner of tahiti xt gpu, and I wonder what are the reasons the new
display code is not available for gcn1 hardware?
regards,
--
Sylvain
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
Hi Laurent,
And many thanks for your comments :)
On 01/29/2018 10:46 AM, Laurent Pinchart wrote:
> Hi Philippe,
>
> (CC'ing Daniel Vetter)
>
> Thank you for the patch.
>
> On Thursday, 25 January 2018 17:55:04 EET Philippe Cornu wrote:
>> The "adjusted_mode" clock value (ie the real pixel
2018-01-29 11:43 GMT+01:00 Laurent Pinchart :
> Hi Philippe,
>
> On Thursday, 25 January 2018 18:01:01 EET Philippe Cornu wrote:
>> There is a difference between the panel/bridge requested pixel clock
>> value and the real one due to the hw platform clock
ttm module needs it to determine its internal parameter setting.
Signed-off-by: Roger He
---
include/linux/swap.h | 6 ++
mm/swapfile.c| 15 +++
2 files changed, 21 insertions(+)
diff --git a/include/linux/swap.h b/include/linux/swap.h
index
Hi Linus,
Thank you for the patch.
On Monday, 29 January 2018 11:55:31 EET Linus Walleij wrote:
> Why is the argument to ->mode_valid() called "crtc"?
> I guess a copy/paste error. Fix it.
I confirm it's a mistake, so you can probably replace "guess" with a word
carrying a bit more confidence
On Mon, Jan 29, 2018 at 11:02 AM, Geert Uytterhoeven
wrote:
> JFYI, when comparing v4.15[1] to v4.15-rc9+1[3], the summaries are:
> - build errors: +1/-0
+ /home/kisskb/slave/src/drivers/gpu/drm/i915/selftests/i915_syncmap.c:
error: 'err' may be used uninitialized in
Hi Philippe,
On Thursday, 25 January 2018 18:01:01 EET Philippe Cornu wrote:
> There is a difference between the panel/bridge requested pixel clock
> value and the real one due to the hw platform clock preciseness (pll,
> dividers...). This patch updates the adjusted_mode clock value with
> the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
Version|17.1|17.3
to indicate whether we are serving for page fault routine when in
ttm_mem_global_reserve.
for ttm_mem_global_reserve if in page fault routine, allow success
always. because page fault routing already grabbed system memory
successfully and allow this exception is harmless.
Otherwise, it will
separate swapped memory account from zone->used_mem because swapped
ttm pages can be flushed into SWAP disk/file under high memory pressure.
add check conditon in ttm_mem_global_reserve to prevent triggering OOM.
because if SWAP disk/file is full, all swapped ttm page would stay in
system memory
On 01/25/2018 05:01 PM, Philippe Cornu wrote:
> There is a difference between the panel/bridge requested pixel clock
> value and the real one due to the hw platform clock preciseness (pll,
> dividers...). This patch updates the adjusted_mode clock value with
> the real hw clock value so then
Hi Philippe,
(CC'ing Daniel Vetter)
Thank you for the patch.
On Thursday, 25 January 2018 17:55:04 EET Philippe Cornu wrote:
> The "adjusted_mode" clock value (ie the real pixel clock) is more
> accurate than "mode" clock value (ie the panel/bridge requested
> clock value). It offers a better
Why is the argument to ->mode_valid() called "crtc"?
I guess a copy/paste error. Fix it.
Signed-off-by: Linus Walleij
---
include/drm/drm_bridge.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/drm/drm_bridge.h b/include/drm/drm_bridge.h
https://bugs.freedesktop.org/show_bug.cgi?id=104831
--- Comment #2 from Martin Bednar ---
Will check. At earliest tomorrow evening though...
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
Hi Kieran,
Thank you for the patch.
On Monday, 22 January 2018 14:50:00 EET Kieran Bingham wrote:
> The ADV7511 has four 256-byte maps that can be accessed via the main I²C
> ports. Each map has it own I²C address and acts as a standard slave
> device on the I²C bus.
>
> Allow a device tree
On Fri, 26 Jan 2018, Randy Dunlap wrote:
> On 01/26/2018 01:48 AM, Lee Jones wrote:
> > On Wed, 24 Jan 2018, 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
> >>
https://bugs.freedesktop.org/show_bug.cgi?id=104831
Bug ID: 104831
Summary: CAYMAN:KDE applications SIGSEGV
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=104831
Mike Lothian changed:
What|Removed |Added
CC||m...@fireburn.co.uk
2018-01-29 10:46 GMT+01:00 Yannick FERTRE :
> On 01/25/2018 05:01 PM, Philippe Cornu wrote:
>> There is a difference between the panel/bridge requested pixel clock
>> value and the real one due to the hw platform clock preciseness (pll,
>> dividers...). This patch updates
Hi Philippe,
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 Philippe Cornu wrote:
> >
> >> The "adjusted_mode" clock value (ie the real pixel clock) is more
> >> accurate than "mode"
On Fri, 26 Jan 2018, Randy Dunlap wrote:
> On 01/25/2018 06:58 PM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20180119:
>>
>
> on x86_64:
> drivers/gpu/drm/i915/intel_panel.o: In function
> `intel_backlight_device_register':
> intel_panel.c:(.text+0x28d4):
https://bugs.freedesktop.org/show_bug.cgi?id=100745
--- Comment #10 from Dimitrios Liappis ---
This is a real problem for me as well, for some time now, with amdgpu (Radeon
RX560), Fedora-27, gnome-shell and Dell P2715Q monitor. It happens both on Xorg
and Wayland.
Hi,
On 18/01/18 15:43, Boris Brezillon wrote:
> Add a driver for Cadence DPI -> DSI bridge.
>
> This driver only support a subset of Cadence DSI bridge capabilities.
>
> Here is a non-exhaustive list of missing features:
> * burst mode
> * DPHY init/configuration steps
> * support for
Hi,
On Fri, Jan 26, 2018 at 04:55:54PM +0100, Giulio Benetti wrote:
> > > > > It behaves the same way as A20, so as I mean IO polarity,
> > > > > all signals(except D0-D23), are inverted.
> > > > > For A33 I've used A33-OLinuXino.
> > > > > For A20 our LiNova1.
> > > >
> > > > Indeed, HSYNC and
https://bugzilla.kernel.org/show_bug.cgi?id=198603
--- Comment #2 from Bruno Pagani (bruno.n.pag...@gmail.com) ---
So I got overheating again, but the dmesg output was the same as in OP. The old
log should probably be disregarded.
My hope is that fixing the cause of this WARNING will also fix
On Mon, Jan 29, 2018 at 10:22:54AM +0800, Chen-Yu Tsai wrote:
> On Mon, Jan 22, 2018 at 6:35 PM, Maxime Ripard
> wrote:
> > Since we now have a way to enforce the zpos, check for the number of alpha
> > planes, the only missing part is to assign our pipe
https://bugs.freedesktop.org/show_bug.cgi?id=104806
Tapani Pälli changed:
What|Removed |Added
See Also|
https://bugzilla.kernel.org/show_bug.cgi?id=198603
--- Comment #1 from Bruno Pagani (bruno.n.pag...@gmail.com) ---
Some update: overheating and the error message seems not correlated anymore.
The error message is happening every time I unplug (even after only 5s), and I
have yet to see
https://bugs.freedesktop.org/show_bug.cgi?id=104834
Bug ID: 104834
Summary: does not boot opensuse on fujitsu-siemens platform on
cpu t2400-t7200
Product: DRI
Version: XOrg git
Hardware: x86 (IA32)
OS:
https://bugs.freedesktop.org/show_bug.cgi?id=104730
--- Comment #5 from EoD ---
This does not seem to have made it into mesa 18.0.0-rc3.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
On Mon, 29 Jan 2018 13:56:21 +0200
Tomi Valkeinen wrote:
> > +static ssize_t cdns_dsi_transfer(struct mipi_dsi_host *host,
> > +const struct mipi_dsi_msg *msg)
> > +{
> > + struct cdns_dsi *dsi = to_cdns_dsi(host);
> > + u32 cmd, sts, val,
On Friday, 2018-01-26 09:45:14 -0800, Dylan Baker wrote:
> Reviewed-by: Dylan Baker
Thanks :)
Is that for this patch or the series?
>
> Quoting Eric Engestrom (2018-01-26 03:30:47)
> > Signed-off-by: Eric Engestrom
> > ---
> > meson.build | 8
https://bugs.freedesktop.org/show_bug.cgi?id=100745
--- Comment #12 from Michel Dänzer ---
(In reply to Dimitrios Liappis from comment #10)
> The nuisance here is this almost always crashes gnome-shell. Attached
> coredump excerpt.
FWIW, that's most likely a
Hi Eric,
On Tue, Jan 23, 2018 at 07:35:10AM +1100, Eric Anholt wrote:
> Maxime Ripard writes:
>
> > Now that the drm_format_info has a alpha field to tell if a format embeds
> > an alpha component in it, let's use it.
> >
> > Cc: Eric Anholt
>
@@ -1107,9 +1108,11 @@ int ttm_pool_populate(struct ttm_tt *ttm, struct
ttm_operation_ctx *ctx)
return ret;
}
+ in_pagefault = ttm->page_flags | TTM_PAGE_FLAG_PAGEFAULT;
That should probably be "ttm->page_flags & TTM_PAGE_FLAG_PAGEFAULT;".
for (i = 0; i <
On Mon, 29 Jan 2018 14:14:09 +0100
Boris Brezillon wrote:
> On Mon, 29 Jan 2018 13:56:21 +0200
> Tomi Valkeinen wrote:
>
> > > +
> > > +static void cdns_dsi_init_link(struct cdns_dsi *dsi)
> > > +{
> > > + struct cdns_dsi_output
Remove redundant store of return code.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
Add missing {} braces.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo_util.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo_util.c
Add missing {} braces.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_tt.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/ttm/ttm_tt.c b/drivers/gpu/drm/ttm/ttm_tt.c
The dual ret/retval was more complex than need be. Now
we drop the retval variable and assign the appropriate VM
codes to ret instead.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo_vm.c | 28
Add missing {} braces.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_page_alloc_dma.c
Hey John,
On 01/26/2018 08:29 PM, John Stultz wrote:
On Wed, Jan 24, 2018 at 11:32 AM, Rob Herring wrote:
On Wed, Jan 24, 2018 at 1:05 PM, John Stultz wrote:
On Wed, Jan 24, 2018 at 7:23 AM, Sean Paul wrote:
On Tue,
https://bugzilla.kernel.org/show_bug.cgi?id=198603
--- Comment #3 from Bruno Pagani (bruno.n.pag...@gmail.com) ---
Created attachment 273913
--> https://bugzilla.kernel.org/attachment.cgi?id=273913=edit
dmesg output from the boot
I’m attaching the full dmesg output.
At 43.x is when I plug the
On Mon, 29 Jan 2018 13:56:21 +0200
Tomi Valkeinen wrote:
> > +
> > +static void cdns_dsi_init_link(struct cdns_dsi *dsi)
> > +{
> > + struct cdns_dsi_output *output = >output;
> > + unsigned long sysclk_period, ulpout;
> > + u32 val;
> > + int i;
> > +
> > + if
Explicitly return errors in ttm_tt_alloc_page_directory() and
ttm_dma_tt_alloc_page_directory() instead of relying on
further logic to detect errors.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_tt.c | 16
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
(v2): Remove stray ; noticed by Felix
---
drivers/gpu/drm/ttm/ttm_bo.c | 13 -
1 file changed, 8 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c
https://bugs.freedesktop.org/show_bug.cgi?id=100745
--- Comment #11 from Dimitrios Liappis ---
Created attachment 137017
--> https://bugs.freedesktop.org/attachment.cgi?id=137017=edit
gnome-shell coredump after amdgpu displayport link status failed
--
You are
Correct missing {} style.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_page_alloc_dma.c
The buf pointer was not being incremented inside the loop
meaning the same block of data would be read or written
repeatedly.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
(v2) Change 'buf' pointer to uint8_t* type
---
Hoist the comparison of the ret to -EDEADLK above
the two code paths to simplify the function.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_execbuf_util.c | 14 --
1 file changed, 8
Flip the logic of the comparison and remove
the redudant variable for the pool address.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
(v2): Remove {} bracing.
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 15 ++-
1 file
Various TTM cleanups (mostly no functional changes).
Notably patch #1 fixes a bug in the access_kmap() function.
The rest are either coding style fixes or simplifications.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
Correct indentation and {} brace style.
Signed-off-by: Tom St Denis
Reviewed-by: Christian König
---
drivers/gpu/drm/ttm/ttm_bo.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/ttm/ttm_bo.c
On 29/01/18 15:14, Boris Brezillon wrote:
>> You don't disable the dsi_sys_clk neither in the ok nor in the error paths.
>
> Hm, it shouldn't be enabled in the first place: the runtime resume
> hook takes care of enabling it, and we don't need this clock to access
> IP registers (which is all we
In dma_fence_release() there is a WARN_ON which could be triggered by
several cases of wrong dma-fence usage. This patch adds a comment to
explain two use-cases to help driver developers that use dma-fence
and trigger that WARN_ON to better understand the reasons for it.
Signed-off-by: Oded
Updated IGT results seem sane:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_7698/shards.html
Would someone be able to apply this patch?
Thanks,
Leo
On 2018-01-17 03:18 PM, Sean Paul wrote:
On Wed, Jan 17, 2018 at 10:39 AM, Maarten Lankhorst
wrote:
Op
https://bugs.freedesktop.org/show_bug.cgi?id=104611
--- Comment #7 from Harry Wentland ---
Did you have a chance to capture a repro dmesg with dc_log=1?
--
You are receiving this mail because:
You are the assignee for the
1 - 100 of 143 matches
Mail list logo