heavy gpu job could occupy memory long time, which lead other user fail to get
memory.
basically pick up Christian idea:
1. Reserve the BO in DC using a ww_mutex ticket (trivial).
2. If we then run into this EBUSY condition in TTM check if the BO we need
memory for (or rather the ww_mutex of it
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
drivers/iommu/intel-iommu.c | 2 +-
drivers/iommu/intel_irq_remapping.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/intel-iommu.c b/drivers/iommu/intel-iommu.c
in
Hi Lee,
On v1 of this series Thierry suggested that this patch would be good to
also go through MFD tree. Would you be able to also pick this patch?
Bellow is his comment on v1 version of this patch:
https://patchwork.ozlabs.org/patch/1049006/
Thank you,
Claudiu Beznea
On 05.03.2019 12:07, Clau
Le mercredi 24 avril 2019 à 17:06 +0200, Daniel Vetter a écrit :
> On Wed, Apr 24, 2019 at 4:41 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Wed, 2019-04-24 at 16:39 +0200, Michel Dänzer wrote:
> > > On 2019-04-24 2:01 p.m., Nicolas Dufresne wrote:
> > > > Le mercredi 24 avril 2019 à 10:31 +0
Hi Thierry Reding：
*Could you please help to check whether there is any problem with the
sign-off identity**?*
*Thanks*
Jerry Han 于2019年4月25日周四 上午11:27写道：
> Support Boe Himax8279d 8.0" 1200x1920 TFT LCD panel, it is a MIPI DSI
> panel.
>
> V8:
> - Modify communication address
>
> V7:
> - Add t
On Wed, 24 Apr 2019, Peter Zijlstra wrote:
> On Thu, Apr 18, 2019 at 10:41:37AM +0200, Thomas Gleixner wrote:
> > There is only one caller of check_prev_add() which hands in a zeroed struct
> > stack trace and a function pointer to save_stack(). Inside check_prev_add()
> > the stack_trace struct is
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
arch/powerpc/platforms/powernv/npu-dma.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/arch/powerpc/platforms/powernv/npu-dma.c
b/arch/powerpc/platforms/powernv/npu-dma.c
in
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_pci.c
b/drivers/net/ethernet/stmicro/stmmac/stmmac
On Wed, Apr 24, 2019 at 07:40:07AM -0300, Mauro Carvalho Chehab wrote:
> Personally, I don't care much with monospaced fonts on this table. After
> all, if I want to see it monospaced, I can simply click at the
> "View page source" at the browser, and it will display the file as a
> plain old monos
In several places in the kernel we find PCI_DEVID used like this:
PCI_DEVID(dev->bus->number, dev->devfn) Therefore create a helper
for it.
Signed-off-by: Heiner Kallweit
---
include/linux/pci.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/include/linux/pci.h b/include/linux/pci.h
in
Add new backlight bindings for the TI LM3630A dual-string white LED.
Signed-off-by: Brian Masney
Reviewed-by: Rob Herring
---
Changes since v5:
- Change 'lm3630a_bl@38' in examples to 'led-controller@38'
Changes since v4:
- Drop $ref from led-sources
- Drop description from reg of i2c address
-
lm3630a_bank_a_update_status() and lm3630a_bank_b_update_status()
both return the brightness value if the brightness was successfully
updated. Writing to these attributes via sysfs would cause a 'Bad
address' error to be returned. These functions should return 0 on
success, so let's change it to co
In several places in the kernel we find PCI_DEVID used like this:
PCI_DEVID(dev->bus->number, dev->devfn) Therefore create a helper
for it.
v2:
- apply the change to all affected places in the kernel
Heiner Kallweit (9):
PCI: add helper pci_dev_id
PCI: use helper pci_dev_id
r8169: use new h
Hi Brendan,
KUNIT_ASSERT_NOT_ERR_OR_NULL() should be replaced to
KUNIT_EXPECT_NOT_ERR_OR_NULL(), right?
On Thu, Apr 04, 2019 at 03:06:49PM -0700, Brendan Higgins wrote:
> Add documentation for KUnit, the Linux kernel unit testing framework.
> - Add intro and usage guide for KUnit
> - Add API refe
Here is a patch series that fixes a single bug and adds fwnode support
to the lm3630a driver. This work was tested on a LG Nexus 5 (hammerhead)
phone. My status page at https://masneyb.github.io/nexus-5-upstream/
describes what is working so far with the upstream kernel.
See the individual patches
Support Boe Himax8279d 8.0" 1200x1920 TFT LCD panel, it is a MIPI DSI
panel.
V8:
- Modify communication address
V7:
- Add the information of the reviewer
- Remove unnecessary delays, The udelay_range code gracefully returns
without hitting the scheduler on a delay of 0. (Derek)
- Merge the sa
Add fwnode support to the lm3630a driver and optionally allow
configuring the label, default brightness level, and maximum brightness
level. The two outputs can be controlled by bank A and B independently
or bank A can control both outputs.
If the platform data was not configured, then the driver
On Thu, Apr 04, 2019 at 03:06:46PM -0700, Brendan Higgins wrote:
> From: Avinash Kondareddy
>
> Tests how tests interact with test managed resources in their lifetime.
>
> Signed-off-by: Avinash Kondareddy
> Signed-off-by: Brendan Higgins
> ---
> kunit/test-test.c | 122 ++
Em Tue, 23 Apr 2019 23:38:16 +0200
Borislav Petkov escreveu:
> On Tue, Apr 23, 2019 at 05:05:02PM -0300, Mauro Carvalho Chehab wrote:
> > That's my view about how that specific file would be after
> > converted to ReST:
> >
> >
> > https://git.linuxtv.org/mchehab/experimental.git/tree/Docum
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
drivers/platform/chrome/chromeos_laptop.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/platform/chrome/chromeos_laptop.c
b/drivers/platform/chrome/chromeos_laptop.c
index 24326eec
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
drivers/pci/msi.c| 6 +++---
drivers/pci/search.c | 10 +++---
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/pci/msi.c b/drivers/pci/msi.c
index 73986825d..e039b740f 100644
---
The Boe Himax8279d is a 8.0" panel with a 1200x1920 resolution and
connected to DSI using four lanes.
V8:
- Modify communication address
V7:
- Add the information of the reviewer
V6:
- Add the information of the reviewer
V5:
- Added changelog
V4:
- None
V3:
- None
V2:
- Add compatible device
Em Wed, 24 Apr 2019 16:54:10 +0200
Borislav Petkov escreveu:
> On Wed, Apr 24, 2019 at 07:40:07AM -0300, Mauro Carvalho Chehab wrote:
> > Personally, I don't care much with monospaced fonts on this table. After
> > all, if I want to see it monospaced, I can simply click at the
> > "View page sour
Hi Thierry Reding：
*Could you please help to check whether there is any problem with the
sign-off identity**?*
*Thanks*
Jerry Han 于2019年4月25日周四 上午11:18写道：
> The Boe Himax8279d is a 8.0" panel with a 1200x1920 resolution and
> connected to DSI using four lanes.
>
> V8:
> - Modify communication
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
drivers/iommu/amd_iommu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iommu/amd_iommu.c b/drivers/iommu/amd_iommu.c
index f467cc4b4..5cb201422 100644
--- a/drivers/iommu/amd_iommu
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
drivers/gpu/drm/amd/amdkfd/kfd_topology.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
b/drivers/gpu/drm/amd/amdkfd/kfd_topology.c
index 2cb09e
On Tue, Apr 23, 2019 at 04:06:40PM -0600, Jonathan Corbet wrote:
> Remember that most of our docs are 99% RST even though they were written
> by people who had never even heard of RST. I really don't think it's a
> big deal - a far smaller cognitive load than trying to keep up with any
> given sub
Use new helper pci_dev_id() to simplify the code.
Signed-off-by: Heiner Kallweit
---
drivers/net/ethernet/realtek/r8169.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/realtek/r8169.c
b/drivers/net/ethernet/realtek/r8169.c
index efaea1a0a..ae476fe8d
Le mercredi 24 avril 2019 à 18:54 +0200, Michel Dänzer a écrit :
> On 2019-04-24 5:44 p.m., Nicolas Dufresne wrote:
> > Le mercredi 24 avril 2019 à 17:06 +0200, Daniel Vetter a écrit :
> > > On Wed, Apr 24, 2019 at 4:41 PM Paul Kocialkowski
> > > wrote:
> > > > On Wed, 2019-04-24 at 16:39 +0200, M
Le mercredi 24 avril 2019 à 10:31 +0200, Michel Dänzer a écrit :
> On 2019-04-19 10:38 a.m., Paul Kocialkowski wrote:
> > On Thu, 2019-04-18 at 20:30 -0400, Nicolas Dufresne wrote:
> > > Le jeudi 18 avril 2019 à 10:18 +0200, Daniel Vetter a écrit :
> > > > > It would be cool if both could be used c
Clang warns:
drivers/gpu/drm/arm/display/komeda/komeda_dev.c:76:38: warning: suggest
braces around initialization of subobject [-Wmissing-braces]
union komeda_config_id config_id = {0,};
^
{}
1 warning
On Thu, Apr 25, 2019 at 11:28:40AM +0800, zhoucm1 wrote:
>
>
> On 2019年04月25日 03:22, Eric Anholt wrote:
> > "Zhou, David(ChunMing)" writes:
> >
> > > Will linux be only mesa-linux? I thought linux is an open linux.
> > > Which will impact our opengl/amdvlk(MIT open source), not sure Rocm:
> >
Dave, Daniel
A single fix for a layer violation requested by Cristoph.
The following changes since commit c2d311553855395764e2e5bf401d987ba65c2056:
drm/vmwgfx: Don't double-free the mode stored in par->set_mode (2019-03-20
07:57:01 +0100)
are available in the Git repository at:
git://peop
https://bugs.freedesktop.org/show_bug.cgi?id=110313
--- Comment #4 from Daniel Vetter ---
(In reply to Arek Hiler from comment #3)
> This seems like a test deficiency. We are polling on udev monitor FD in
> anticipation of an events. According the the log linked in the previous
> comments we get
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #83 from Tom B ---
I have a similar problem with my Radeon VII. My testing/experiments are
outlined here: https://bugs.freedesktop.org/show_bug.cgi?id=110510 sorry for
the long post!
However my bug seems slightly different albeit re
On Tue, 05 Mar 2019, claudiu.bez...@microchip.com wrote:
> From: Claudiu Beznea
>
> Add compatible string for SAM9X60 HLCDC's PWM.
>
> Signed-off-by: Claudiu Beznea
> Acked-by: Thierry Reding
> ---
> drivers/pwm/pwm-atmel-hlcdc.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/d
The Intel CI [1] was not happy with the previous version and I don't
know which part it didn't like. So I'll split up the series and feed it
piece by piece until I know where the problem is.
Noralf.
[1] https://patchwork.freedesktop.org/series/58597/
Noralf Trønnes (1):
drm/fb-helper: Avoid ra
drm_fb_helper_is_bound() is used to check if DRM userspace is in control.
This is done by looking at the fb on the primary plane. By the time
fb-helper gets around to committing, it's possible that the facts have
changed.
Avoid this race by holding the drm_device->master_mutex lock while
committin
Hi, Christian,
On Wed, 2019-04-24 at 16:20 +0200, Thomas Hellström wrote:
> On Wed, 2019-04-24 at 14:10 +, Koenig, Christian wrote:
> > Am 24.04.19 um 14:00 schrieb Thomas Hellstrom:
> > > Add a pointer to the struct vm_operations_struct in the
> > > bo_device,
> > > and
> > > assign that poin
On 21.04.2019 10:25, Jonas Karlman wrote:
> When ddc-i2c-bus property is used, a NULL pointer dereference is reported:
>
> [ 31.041669] Unable to handle kernel NULL pointer dereference at virtual
> address 0008
> [ 31.041671] pgd = 4d3c16f6
> [ 31.041673] [0008] *pgd=
> [ 3
Hi Dave, Daniel,
please consider merging these imx-drm fixes for v5.1.
regards
Philipp
The following changes since commit dc4060a5dc2557e6b5aa813bf5b73677299d62d2:
Linux 5.1-rc5 (2019-04-14 15:17:41 -0700)
are available in the Git repository at:
git://git.pengutronix.de/pza/linux tags/imx
Am 25.04.2019 10:35 schrieb Thomas Hellstrom :
Hi, Christian,
On Wed, 2019-04-24 at 16:20 +0200, Thomas Hellström wrote:
> On Wed, 2019-04-24 at 14:10 +, Koenig, Christian wrote:
> > Am 24.04.19 um 14:00 schrieb Thomas Hellstrom:
> > > Add a pointer to the struct vm_operations_struct in the
Hi Matt,
Thank you for the patch.
On Wed, Apr 24, 2019 at 02:21:40PM +, Matt Redfearn wrote:
> The Synopsys manual states that software should wait for all active
> lanes to reach stop state (User manual section 3.1.5). Currently the
> driver only waits for / checks that the clock lane is in
Hi Matt,
Thank you for the patch.
On Wed, Apr 24, 2019 at 02:22:00PM +, Matt Redfearn wrote:
> The DRM documentation states that post_disable is an optional callback.
> As such an implementing device may not populate it. To avoid panicing
> the kernel by calling a NULL function pointer, we sh
On Thu, Apr 25, 2019 at 10:31 AM Noralf Trønnes wrote:
>
> The Intel CI [1] was not happy with the previous version and I don't
> know which part it didn't like. So I'll split up the series and feed it
> piece by piece until I know where the problem is.
You can also send stuff to intel-gfx-try...
On Wed, 2019-04-17 at 15:50 +0200, Lucas Stach wrote:
> Move buffer setup and starting of the FE loop in the kernel ringbuffer
> into a separate function. This is a preparation to start the FE later
> in the submit process.
>
> Signed-off-by: Lucas Stach
Reviewed-by: Philipp Zabel
regards
Phil
On Wed, Apr 24, 2019 at 02:22:18PM +, Matt Redfearn wrote:
> The Synopsys MIPI DSI IP contains a video test pattern generator which
> is helpful in debugging video timing with connected displays.
> Add a debugfs directory containing files which allow the VPG to be
> enabled and disabled, and it
On Wed, 2019-04-17 at 15:50 +0200, Lucas Stach wrote:
> In preparation to having a context per process, etnaviv_gem_mapping_get
> should not use the current GPU context, but needs to be told which
> context to use.
>
> Signed-off-by: Lucas Stach
Reviewed-by: Philipp Zabel
regards
Philipp
_
Op 06-03-2019 om 23:43 schreef Rodrigo Siqueira:
> On 03/01, Maarten Lankhorst wrote:
>> Convert vkms to using __drm_atomic_helper_crtc_reset(), instead of
>> writing its own version. Instead of open coding destroy_state(),
>> call it directly for freeing the old state.
>>
>> Signed-off-by: Maarten
On Wed, 2019-04-17 at 14:21 +0200, Lucas Stach wrote:
> If there is a match in the HW DB, the function is left early, before
> inititalizing the idle mask. Fix this by doing the init earlier, as
> only old GPUs, not present in the HW DB need a different idle mask.
>
> Signed-off-by: Lucas Stach
The pointer p aquired with drmModeGetPlane() is not free in error
path. Fix possible memory leak by calling drmModeFreePlane() in
the error path.
Signed-off-by: Seung-Woo Kim
---
tests/kms/libkms-test-plane.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/tests/kms/l
* Thomas Gleixner wrote:
> - if (unlikely(!ret))
> + if (unlikely(!ret)) {
> + if (!trace->nr_entries) {
> + /*
> + * If save_trace fails here, the printing might
> + * trigger a WARN but because of the !nr_entries
On Thu, 25 Apr 2019 at 10:49, Seung-Woo Kim wrote:
>
> The pointer p aquired with drmModeGetPlane() is not free in error
> path. Fix possible memory leak by calling drmModeFreePlane() in
> the error path.
>
> Signed-off-by: Seung-Woo Kim
Reviewed-by: Emil Velikov
and pushed to master.
Thanks
On Wed, 24 Apr 2019 at 18:08, John Stultz wrote:
>
> Recently I've been trying to sync the AOSP libdrm tree with
> the upstream freedesktop branch.
>
> Thanks to input from Sean, Alistair and Marissa, we've managed
> to drop a bunch of stale patches AOSP was carrying, and get
> the AOSP libdrm upd
Op 26-02-2019 om 17:17 schreef Matt Roper:
> On Tue, Feb 26, 2019 at 08:26:36AM +0100, Maarten Lankhorst wrote:
>> Hey,
>>
>> Op 21-02-2019 om 01:28 schreef Matt Roper:
>>> Some display controllers can be programmed to present non-black colors
>>> for pixels not covered by any plane (or pixels cove
https://bugs.freedesktop.org/show_bug.cgi?id=109607
--- Comment #12 from Arek Hiler ---
This is an infrastructure deficiency coming from technical limitations. It is
especially bad as it requires us to create a catch-all bug for incompletes,
that may obscure some serious problems.
To mitigate th
Den 25.04.2019 11.25, skrev Daniel Vetter:
> On Thu, Apr 25, 2019 at 10:31 AM Noralf Trønnes wrote:
>>
>> The Intel CI [1] was not happy with the previous version and I don't
>> know which part it didn't like. So I'll split up the series and feed it
>> piece by piece until I know where the probl
On 24.04.2019 16:22, Matt Redfearn wrote:
> The DRM documentation states that post_disable is an optional callback.
> As such an implementing device may not populate it. To avoid panicing
> the kernel by calling a NULL function pointer, we should NULL check it
> before blindy calling it.
>
> Signed
Since the OOM interrupt directly deals with the binner bo, it doesn't
make sense to try and handle it without a binner buffer registered.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/vc4/vc4_irq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_irq.c b/driv
Changes since v6:
* Removed vc4_v3d_bin_bo_put from error paths;
* Added WARN_ON_ONCE when no bin BO at refcount release.
Changes since v5:
* Fix more locking mistakes;
* Introduce get/put helpers;
* Grabbed a reference when submitting an exec job with a binner slot.
* Addressed misc comments.
Ch
In preparation for wrapping the binner bo allocation helper with
put/get helpers, pass the vc4 dev directly and drop the vc4 prefix.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/vc4/vc4_v3d.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/gpu/drm/
Check that we have a V3D device registered before attempting to
allocate a binner buffer object.
Signed-off-by: Paul Kocialkowski
---
drivers/gpu/drm/vc4/vc4_v3d.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_v3d.c b/drivers/gpu/drm/vc4/vc4_v3d.c
index 7c490106e
The binner BO is not required until the V3D is in use, so avoid
allocating it at probe and do it on the first non-dumb BO allocation.
Keep track of which clients are using the V3D and liberate the buffer
when there is none left, using a kref. Protect the logic with a
mutex to avoid race conditions
https://bugs.freedesktop.org/show_bug.cgi?id=110514
Martin Peres changed:
What|Removed |Added
Component|DRM/Intel |IGT
Priority|medium
https://bugs.freedesktop.org/show_bug.cgi?id=110514
--- Comment #2 from CI Bug Log ---
The CI Bug Log issue associated to this bug has been updated.
### New filters associated
* CML: igt@* - skip - Test requirement: is_i915_device(fd) &&
has_known_intel_chipset(fd), Skip
(No new failures asso
Hi Laurent,
Thanks for the review!
On 25/04/2019 10:31, Laurent Pinchart wrote:
> On Wed, Apr 24, 2019 at 02:22:18PM +, Matt Redfearn wrote:
>> The Synopsys MIPI DSI IP contains a video test pattern generator which
>> is helpful in debugging video timing with connected displays.
>> Add a deb
Hi Andrzej,
On 25/04/2019 13:13, Andrzej Hajda wrote:
> On 24.04.2019 16:22, Matt Redfearn wrote:
>> The DRM documentation states that post_disable is an optional callback.
>> As such an implementing device may not populate it. To avoid panicing
>> the kernel by calling a NULL function pointer, we
On Tue, Feb 12, 2019 at 05:02:30PM -0500, Lyude Paul wrote:
> On a very specific subset of ThinkPad P50 SKUs, particularly ones that
> come with a Quadro M1000M chip instead of the M2000M variant, the BIOS
> seems to have a very nasty habit of not always resetting the secondary
> Nvidia GPU between
https://bugs.freedesktop.org/show_bug.cgi?id=110514
--- Comment #3 from CI Bug Log ---
The CI Bug Log issue associated to this bug has been updated.
### New filters associated
* CML: igt@kms_addfb_basic@* - skip - Test requirement: gen >= 9, SKIP
-
https://intel-gfx-ci.01.org/tree/drm-tip/Pat
Hi Daniel, Dave,
Here is a new drm-misc-fixes PR.
Thanks!
Maxime
drm-misc-fixes-2019-04-25:
- sun4i: Fix module loading / unloading
- vc4: Fix a compilation error and memory leak
- dw-hdmi: Fix an overflow on Rockchip and SCDC configuration
The following changes since commit 1a07a94b47b1f528f39c
On Thu, Apr 25, 2019 at 11:45:14AM +0200, Thomas Gleixner wrote:
> @@ -2788,29 +2798,32 @@ static void __ftrace_trace_stack(struct
>*/
> preempt_disable_notrace();
>
> - use_stack = __this_cpu_inc_return(ftrace_stack_reserve);
> + stackidx = __this_cpu_inc_return(ftrace_stac
On Thu, Apr 25, 2019 at 11:45:17AM +0200, Thomas Gleixner wrote:
> Simplify the stack retrieval code by using the storage array based
> interface.
>
> Signed-off-by: Thomas Gleixner
> Reviewed-by: Steven Rostedt (VMware)
> ---
> kernel/trace/trace_stack.c | 37
On Thu, Apr 25, 2019 at 11:44:53AM +0200, Thomas Gleixner wrote:
> This is an update to V2 which can be found here:
>
> https://lkml.kernel.org/r/20190418084119.056416...@linutronix.de
>
> Changes vs. V2:
>
> - Fixed the kernel-doc issue pointed out by Mike
>
> - Removed the '-1' oddity f
On Thu, Apr 25, 2019 at 11:45:11AM +0200, Thomas Gleixner wrote:
> There is only one caller which hands in save_trace as function pointer.
>
> Signed-off-by: Thomas Gleixner
Acked-by: Peter Zijlstra (Intel)
___
dri-devel mailing list
dri-devel@lists.f
https://bugs.freedesktop.org/show_bug.cgi?id=110510
--- Comment #4 from Tom B ---
Unfortunately this workaround does not work.
As soon as I launch a game on either monitor the whole system freezes despite
the performance setting.
Nothing appeared in journalctl this time but it seems like the sa
wait_for_completion_timeout() returns 0 on timeout and aleast 1 otherwise
so checking for < makes no sense here.
Signed-off-by: Nicholas Mc Guire
---
Problem located with an experimental coccinelle script
While this check does no harm in this form - it should be fixed anyway
to comply with the
On Wed, Apr 24, 2019 at 02:59:00PM -0700, Eric Anholt wrote:
> Sean Paul writes:
>
> > From: Sean Paul
> >
> > Sphinx really wants colons after arguments :/
> >
> > Fixes the following warnings:
> > drm_gem.c:1384: warning: Function parameter or member 'fence_array' not
> > described in 'drm_ge
On 2019-04-24 7:43 p.m., Nicolas Dufresne wrote:
> Le mercredi 24 avril 2019 à 18:54 +0200, Michel Dänzer a écrit :
>> On 2019-04-24 5:44 p.m., Nicolas Dufresne wrote:
>>> Le mercredi 24 avril 2019 à 17:06 +0200, Daniel Vetter a écrit :
On Wed, Apr 24, 2019 at 4:41 PM Paul Kocialkowski
w
Em Tue, 16 Apr 2019 22:25:33 +0200
Arnd Bergmann escreveu:
> The .ioctl and .compat_ioctl file operations have the same prototype so
> they can both point to the same function, which works great almost all
> the time when all the commands are compatible.
>
> One exception is the s390 architectur
On Thu, Apr 25, 2019 at 5:22 PM Mauro Carvalho Chehab
wrote:
> Em Tue, 16 Apr 2019 22:25:33 +0200 Arnd Bergmann escreveu:
>
> If I understand your patch description well, using compat_ptr_ioctl
> only works if the driver is not for s390, right?
No, the purpose of compat_ptr_ioctl() is to make su
From: Emil Velikov
In dma_buf_attach() we allocate memory w/o a mutex being held, thus in
the error path we should kfree() it after the mutex_unlock.
The inverse function dma_buf_deattach() gets this right.
Cc: Sumit Semwal
Signed-off-by: Emil Velikov
---
drivers/dma-buf/dma-buf.c | 2 +-
1
https://bugs.freedesktop.org/show_bug.cgi?id=110355
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
From: Emil Velikov
Currently drm_gem_prime_fd_to_handle() consists of illegible amount of
goto labels, for no obvious reason.
Split it in two (as below) making the code far simpler and obvious.
drm_gem_prime_fd_to_handle()
- prime mtx handling
- fd/dmabuf refcounting
- hash table lookup
import
From: Emil Velikov
Currently drm_gem_prime_handle_to_fd() consists of illegible amount of
goto labels, for no obvious reason.
Split it in two (as below) making the code far simpler and obvious.
drm_gem_prime_handle_to_fd()
- prime mtx handling
- drm_gem_object lookup and refcounting
- creati
Em Thu, 25 Apr 2019 16:35:34 +0100
Al Viro escreveu:
> On Thu, Apr 25, 2019 at 12:21:53PM -0300, Mauro Carvalho Chehab wrote:
>
> > If I understand your patch description well, using compat_ptr_ioctl
> > only works if the driver is not for s390, right?
>
> No; s390 is where "oh, just set ->co
On Thu, Apr 25, 2019 at 5:35 PM Al Viro wrote:
>
> On Thu, Apr 25, 2019 at 12:21:53PM -0300, Mauro Carvalho Chehab wrote:
>
> > If I understand your patch description well, using compat_ptr_ioctl
> > only works if the driver is not for s390, right?
>
> No; s390 is where "oh, just set ->compat_ioct
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #37 from Talha Khan ---
The issue occurs (and workaround works) on kernels 5.0.8 and 5.0.9.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
On Thu, Apr 25, 2019 at 04:48:50PM +0100, Emil Velikov wrote:
> From: Emil Velikov
>
> In dma_buf_attach() we allocate memory w/o a mutex being held, thus in
> the error path we should kfree() it after the mutex_unlock.
>
> The inverse function dma_buf_deattach() gets this right.
>
> Cc: Sumit
Hi Emil.
Thanks for the patch - it looks like a good simplification.
The changes introduced in import_buf_to_handle() changes the logic
a little to avoid goto - this hurts readability.
It would be better to keep the current structure and use goto label
to hanlde the error situations.
Then error h
Hi Emil.
Thans, again a nice simplification.
But the export_handle_to_buf now have to mutex_unlock.
Please use proper goto error handlign with a single
unlock in the end of the fuction.
This makes it simple to check that we always do the unlock.
Likewise in next function. Avoid two mutex_unlock, w
Paul Kocialkowski writes:
> The binner BO is not required until the V3D is in use, so avoid
> allocating it at probe and do it on the first non-dumb BO allocation.
>
> Keep track of which clients are using the V3D and liberate the buffer
> when there is none left, using a kref. Protect the logic
Hi Matt,
On Thu, Apr 25, 2019 at 12:39:27PM +, Matt Redfearn wrote:
> On 25/04/2019 13:13, Andrzej Hajda wrote:
> > On 24.04.2019 16:22, Matt Redfearn wrote:
> >> The DRM documentation states that post_disable is an optional callback.
> >> As such an implementing device may not populate it. To
On Thu, Apr 25, 2019 at 08:59:15PM +0300, Laurent Pinchart wrote:
> On Thu, Apr 25, 2019 at 12:39:27PM +, Matt Redfearn wrote:
> > On 25/04/2019 13:13, Andrzej Hajda wrote:
> >> On 24.04.2019 16:22, Matt Redfearn wrote:
> >>> The DRM documentation states that post_disable is an optional callbac
On Mon, Apr 22, 2019 at 10:27:14AM -0300, Mauro Carvalho Chehab wrote:
> Convert the PM documents to ReST, in order to allow them to
> build with Sphinx.
This is massively CCed covering a large range of subsystems and is patch
25 of a 79 patch series so I've no context for what's going on here or
Hi Heiner,
On Wed, Apr 24, 2019 at 09:17:19PM +0200, Heiner Kallweit wrote:
> Use new helper pci_dev_id() to simplify the code.
>
> Signed-off-by: Heiner Kallweit
Acked-By: Benson Leung
> ---
> drivers/platform/chrome/chromeos_laptop.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
https://bugs.freedesktop.org/show_bug.cgi?id=110517
Bug ID: 110517
Summary: Running any OpenGL related command with DRI_PRIME=1
crashes the system
Product: DRI
Version: DRI git
Hardware: x86-64 (AMD64)
OS: L
https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #38 from Adrian Garay ---
(In reply to Alex Deucher from comment #33)
> (In reply to Talha Khan from comment #31)
> > I moved the raven_dcmu.bin file to another directory, but unfortunately I am
> > still unable to boot any kernel ne
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #15 from Jaap Buurman ---
That's bad to hear :( Worth a try though. How often do you experience freezes
by the way? And is this for all games, or are some games completely stable? For
me, I am getting crashes in Kerbal Space Program,
Dave, Daniel
A single fix for a layer violation requested by Cristoph.
The following changes since commit c2d311553855395764e2e5bf401d987ba65c2056:
drm/vmwgfx: Don't double-free the mode stored in par->set_mode (2019-03-20
07:57:01 +0100)
are available in the Git repository at:
git://peop
On Wed, Apr 24, 2019 at 11:58 AM Masayoshi Mizuma wrote:
>
> Hi Brendan,
>
> KUNIT_ASSERT_NOT_ERR_OR_NULL() should be replaced to
> KUNIT_EXPECT_NOT_ERR_OR_NULL(), right?
Generally speaking, no.
There may be places that I have used it improperly, but I think it is
generally okay to use.
If you
1 - 100 of 117 matches
Mail list logo
