On 25/02/18 11:22, Lukas Wunner wrote:
> On Thu, Feb 22, 2018 at 07:42:46PM +0200, Jyri Sarha wrote:
>> Put consumer device to deferred probe list if it is unbound due to a
>> dropped link to a supplier.
>>
>> When a device link supplier is unbound (either manually or because one
>> of its own supp
This patch implements preemption feature for A6xx targets, this allows
the GPU to switch to a higher priority ringbuffer if one is ready. A6XX
hardware as such supports multiple levels of preemption granularities,
ranging from coarse grained(ringbuffer level) to a more fine grained
such as draw-cal
This patch adds the following two opcodes:
CP_SET_MARKER opcode is a way to tell CP the current mode of GPU
operation(useful if preemption is in use).
CP_SET_PSEUDO_REG opcode will instruct CP to set a bunch of internal
CP registers, again useful for the preemption save/restore sequence.
Signed-
This patch simply increases the number of available ringbuffers,
therefore enabling preemption.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/adreno/a6xx_gpu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/msm/adreno/a6xx_gpu.c
b/drivers/gpu/drm/msm
This patch adds a bit of infrastructure to give the different Adreno
targets the flexibility to setup the submitqueues per their needs.
Signed-off-by: Sharat Masetty
---
drivers/gpu/drm/msm/msm_gpu.h | 7 +++
drivers/gpu/drm/msm/msm_submitqueue.c | 15 +--
2 files change
This patch follows Jordan's recent "drm/msm: Add A6XX device support"
patch series and adds preemption support. Preemption allows the GPU to switch
to a higher priority ringbuffer when one is ready, thereby improving user
experience. A6xx hardware supports various preemption levels, each with
diffe
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #34 from Deposite Pirate (dpir...@metalpunks.info) ---
Ok, I've had some time to apply the new patch. The tracing works and with this
patch applied on top of 4.15.6 the issue has vanished for some reason.
--
You are receiving this ma
https://bugzilla.kernel.org/show_bug.cgi?id=198123
--- Comment #33 from Deposite Pirate (dpir...@metalpunks.info) ---
Created attachment 274465
--> https://bugzilla.kernel.org/attachment.cgi?id=274465&action=edit
dmesg log 2
Applied on top of 4.15.6.
--
You are receiving this mail because:
Yo
Hi
I've not seen anything untoward with these patches with my AMD PRIME system here
Tested-by: Mike Lothian
Cheers
Mike
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=104520
Amy changed:
What|Removed |Added
Version|unspecified |17.3
Priority|high
https://bugs.freedesktop.org/show_bug.cgi?id=105244
Bug ID: 105244
Summary: NULL dereference during startup of Cape Verde with
AMDGPU and GPU passthrough
Product: DRI
Version: unspecified
Hardware: Other
OS
On Sat, Feb 24, 2018 at 06:16:46PM +, Meghana Madhyastha wrote:
> -Remove chunk splitting in tinydrm_spi_transfer in tinydrm-helpers as The spi
> core will split a buffer into max_dma_len chunks for the
> spi controller driver to handle.
> -Remove automatic byte swapping in tinydrm_spi_transf
On Sat, Feb 24, 2018 at 06:17:12PM +, Meghana Madhyastha wrote:
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -1003,7 +1003,7 @@ static int spi_map_msg(struct spi_controller *ctlr,
> struct spi_message *msg)
> * drivers which implement a transfer_one() operation. It provides
>
https://bugs.freedesktop.org/show_bug.cgi?id=100069
Gregor Münch changed:
What|Removed |Added
CC||mar...@gmail.com
--- Comment #5 from Gre
[cc += linux-rpi-ker...@lists.infradead.org]
On Sat, Feb 24, 2018 at 06:15:59PM +, Meghana Madhyastha wrote:
> I've added bcm2835_spi_transfer_one_message in spi-bcm2835. This calls
> spi_split_transfers_maxsize to split large chunks for spi dma transfers.
> I then removed chunk splitting in
https://bugs.freedesktop.org/show_bug.cgi?id=104549
--- Comment #2 from _archuser_ ---
ommit my last commit , apparently something changed and my build script
produces a 64bit radeon_dri.so that somehow works , will investigate this
further,
--
You are receiving this mail because:
You are the a
https://bugs.freedesktop.org/show_bug.cgi?id=105240
Bug ID: 105240
Summary: GPU lock-up when running QT5 based celestia
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: norma
On Thu, Feb 8, 2018 at 11:33 PM, SF Markus Elfring
wrote:
> From: Markus Elfring
> Date: Thu, 8 Feb 2018 22:23:57 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus Elfring
> --
On Thu, Feb 22, 2018 at 07:42:46PM +0200, Jyri Sarha wrote:
> Put consumer device to deferred probe list if it is unbound due to a
> dropped link to a supplier.
>
> When a device link supplier is unbound (either manually or because one
> of its own suppliers was unbound), its consumers are unbound
On Sun, 25 Feb 2018 09:59:00 +0100,
Lukas Wunner wrote:
>
> On Wed, Feb 21, 2018 at 01:39:34PM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, February 21, 2018 10:57:14 AM CET Rafael J. Wysocki wrote:
> > > So if pci_pm_runtime_suspend() is modified to call pci_save_state()
> > > before returni
On 02/23/2018 02:00 AM, Oleksandr Andrushchenko wrote:
> On 02/23/2018 01:50 AM, Boris Ostrovsky wrote:
>> On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
>>> +
>>> +static irqreturn_t evtchnl_interrupt_ctrl(int irq, void *dev_id)
>>> +{
>>> +struct xen_drm_front_evtchnl *evtchnl = dev_i
Hi Frank,
On Sunday, 25 February 2018 00:42:47 EET Frank Rowand wrote:
> On 02/22/18 14:10, Frank Rowand wrote:
> > Hi Laurent, Rob,
> >
> > Thanks for the prompt spin to address my concerns. There are some small
> > technical issues.
> >
> > I did not read the v3 patch until today. v3 through
https://bugs.freedesktop.org/show_bug.cgi?id=104549
--- Comment #1 from _archuser_ ---
Trying some stuff and stumbled on a strange side effect: when preloading 32bit
build of mesa master branch of radeon_dri.so the trace runs without glitches,
however wine can not be started this way as ts excepe
https://bugs.freedesktop.org/show_bug.cgi?id=105221
--- Comment #1 from Eric Smith ---
Replaced Radeon HD 5850 (midrange Evergreen) with Radon R7-240 (low-end GCN 1st
gen), and it boots fine without needing to remove rhgb or add nomodeset.
--
You are receiving this mail because:
You are the ass
Hi,
On 24 February 2018 at 00:43, Jason Ekstrand wrote:
> On Tue, Feb 13, 2018 at 4:31 PM, Keith Packard wrote:
>> + image->chain = chain;
>> + image->state = wsi_image_idle;
>> + image->fb_id = 0;
>> +
>> + /* XXX extract depth and bpp from image somehow */
>
> You have the format in cr
On Mon, Feb 12, 2018 at 2:53 PM, kbuild test robot
wrote:
>
>
> Fixes: 447ed3ae9ceb ("drm/amdgpu: Add KFD eviction fence")
> Signed-off-by: Fengguang Wu
> ---
> amdgpu_amdkfd_fence.c |2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_amd
On Wed, Feb 21, 2018 at 01:39:34PM +0100, Rafael J. Wysocki wrote:
> On Wednesday, February 21, 2018 10:57:14 AM CET Rafael J. Wysocki wrote:
> > So if pci_pm_runtime_suspend() is modified to call pci_save_state()
> > before returning 0 in the !dev->driver case, we can just move the
> > pci_restore
https://bugs.freedesktop.org/show_bug.cgi?id=103953
--- Comment #4 from Marc Cousin ---
Having the exact same bug, but with a RX570… DVI-D, 4.15 kernel, xorg 1.19.6,
mesa 17.3.5…
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=104274
--- Comment #8 from Luke McKee ---
I commented because the user here had the error relating to powerplay failing
that I have seen in other threads.
https://forum-en.msi.com/index.php?topic=298468.0
[46667.236028] kernel: amdgpu: [powerplay]
-Remove chunk splitting in tinydrm_spi_transfer in tinydrm-helpers as The spi
core will split a buffer into max_dma_len chunks for the
spi controller driver to handle.
-Remove automatic byte swapping in tinydrm_spi_transfer as it doesn't have
users.
-Remove the upper bound check on dma transfer
https://bugs.freedesktop.org/show_bug.cgi?id=105039
--- Comment #2 from Marc Cousin ---
I'm having a variant of this… cannot go over 1920x1080p
4.15, mesa 17.3, xorg 1.19.6, RX570. Deactivating DC makes resolutions
available again.
--
You are receiving this mail because:
You are the assignee f
/Roger-He/drm-ttm-check-if-free-mem-space-is-under-the-lower-limit/20180225-033957
base: git://people.freedesktop.org/~airlied/linux.git drm-next
config: x86_64-rhel (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the attached .config to linux build tree
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #21 from Andrey Grodzovsky (andrey.grodzov...@amd.com) ---
Yea, you right, forgot all about the cold reset part you mentioned so will
retry again on Monday. In the meanwhile you can at least try switching to LLVM
7 and see if this make
Add bcm2835_spi_transfer_one_message in spi-bcm2835.c. This function calls
the helper spi_split_transfers_maxsize before calling spi_transfer_one_message
to split the message into smaller chunks to be able to use dma.
Signed-off-by: Meghana Madhyastha
---
drivers/spi/spi-bcm2835.c | 14 +
-ci/linux/commits/Claudiu-Beznea/extend-PWM-framework-to-support-PWM-modes/20180225-024011
base:
https://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git
for-next
config: xtensa-allmodconfig (attached as .config)
compiler: xtensa-linux-gcc (GCC) 7.2.0
reproduce:
wget
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #2 from dwagner ---
Just to mention this once again: These system crashes still occur, and way too
frequently to consider the amdgpu driver stable enough for professional use.
Sample dmesg output from today:
Feb 24 18:26:55 [drm:amd
I've added bcm2835_spi_transfer_one_message in spi-bcm2835. This calls
spi_split_transfers_maxsize to split large chunks for spi dma transfers.
I then removed chunk splitting in the tinydrm spi helper (as now the core is
handling the chunk splitting). However, although the SPI HW should be able to
https://bugs.freedesktop.org/show_bug.cgi?id=105177
--- Comment #17 from Reimar Imhof ---
Created attachment 137577
--> https://bugs.freedesktop.org/attachment.cgi?id=137577&action=edit
Xorg.0.log-4.15.5-with-patch-hdmi.txt
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=105177
--- Comment #16 from Reimar Imhof ---
Created attachment 137576
--> https://bugs.freedesktop.org/attachment.cgi?id=137576&action=edit
dmesg-4-15-5-with-patch-hdmi.txt
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=105177
--- Comment #14 from Reimar Imhof ---
I've build a 4.15.5 kernel incl. your patch and booted with display connected
to hdmi.
First boot hang.
In journalctl I found
Feb 24 11:29:28 linux kernel: [drm:drm_atomic_helper_wait_for_flip_done
[drm_kms_
https://bugs.freedesktop.org/show_bug.cgi?id=105177
--- Comment #15 from Reimar Imhof ---
Created attachment 137575
--> https://bugs.freedesktop.org/attachment.cgi?id=137575&action=edit
journalctl-boot-4-15-5-with-patch-hdmi-hang.txt
--
You are receiving this mail because:
You are the assigne
https://bugs.freedesktop.org/show_bug.cgi?id=105235
Bug ID: 105235
Summary: shutdown gives a NMI and locks (nouveau?)
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Sev
Document sysfs attributes of s6e63m0 lcd panel driver by looking through
git logs and reading code.
Signed-off-by: Aishwarya Pant
---
Changes in v2:
- Convert spaces to tabs
Documentation/ABI/testing/sysfs-class-lcd-s6e63m0 | 27 +++
1 file changed, 27 insertions(+)
create
On 02/23/18 01:25, Laurent Pinchart wrote:
> Hi Frank,
>
> On Friday, 23 February 2018 05:20:43 EET Frank Rowand wrote:
>> On 02/22/18 02:25, Laurent Pinchart wrote:
>>> On Thursday, 22 February 2018 08:07:14 EET Frank Rowand wrote:
On 02/20/18 15:10, Laurent Pinchart wrote:
> Hello,
On Fri, Feb 23, 2018 at 9:10 PM, Jordan Crouse wrote:
> On Fri, Feb 23, 2018 at 04:06:39PM +0530, Vivek Gautam wrote:
>> On Fri, Feb 23, 2018 at 5:22 AM, Jordan Crouse
>> wrote:
>> > On Wed, Feb 07, 2018 at 04:01:19PM +0530, Vivek Gautam wrote:
>> >> From: Sricharan R
>> >>
>> >> The smmu devic
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
> +
> +struct drm_driver xen_drm_driver = {
> + .driver_features = DRIVER_GEM | DRIVER_MODESET |
> + DRIVER_PRIME | DRIVER_ATOMIC,
> + .lastclose = lastclose,
> + .gem_free
On 02/23/2018 02:53 AM, Oleksandr Andrushchenko wrote:
> On 02/23/2018 02:25 AM, Boris Ostrovsky wrote:
>> On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
>>> static int __init xen_drv_init(void)
>>> {
>>> +/* At the moment we only support case with XEN_PAGE_SIZE ==
>>> PAGE_SIZE *
On 02/23/18 01:00, Laurent Pinchart wrote:
> Hi Frank,
>
> On Friday, 23 February 2018 04:38:06 EET Frank Rowand wrote:
>> On 02/22/18 14:10, Frank Rowand wrote:
>>> Hi Laurent, Rob,
>>>
>>> Thanks for the prompt spin to address my concerns. There are some small
>>> technical issues.
>>>
>>> I di
On 02/23/2018 01:37 AM, Oleksandr Andrushchenko wrote:
> On 02/23/2018 12:23 AM, Boris Ostrovsky wrote:
>> On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
>>> +static struct xenbus_driver xen_driver = {
>>> +.ids = xen_drv_ids,
>>> +.probe = xen_drv_probe,
>>> +.remove = xen_drv_
On 02/23/2018 05:26 PM, Boris Ostrovsky wrote:
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
+static struct xen_gem_object *gem_create(struct drm_device *dev, size_t size)
+{
+ struct xen_drm_front_drm_info *drm_info = dev->dev_private;
+ struct xen_gem_object *xen_obj;
+
On 02/21/2018 03:03 AM, Oleksandr Andrushchenko wrote:
> +static struct xen_gem_object *gem_create(struct drm_device *dev, size_t size)
> +{
> + struct xen_drm_front_drm_info *drm_info = dev->dev_private;
> + struct xen_gem_object *xen_obj;
> + int ret;
> +
> + size = round_up(size,
On Fri, Feb 23, 2018 at 05:55:47PM +0200, Ville Syrjälä wrote:
> On Fri, Feb 02, 2018 at 05:10:54PM +0200, Ville Syrjälä wrote:
> > On Fri, Feb 02, 2018 at 04:10:39PM +0200, Ville Syrjälä wrote:
> > > On Tue, Jan 23, 2018 at 09:02:35PM +0200, Ville Syrjälä wrote:
> > > > On Tue, Jan 23, 2018 at 06:
On Fri, Feb 23, 2018 at 5:22 AM, Jordan Crouse wrote:
> On Wed, Feb 07, 2018 at 04:01:19PM +0530, Vivek Gautam wrote:
>> From: Sricharan R
>>
>> The smmu device probe/remove and add/remove master device callbacks
>> gets called when the smmu is not linked to its master, that is without
>> the con
On Tue, Feb 13, 2018 at 05:50:01PM -0800, Dongwon Kim wrote:
> Reference document for hyper_DMABUF driver
>
> Documentation/hyper-dmabuf-sharing.txt
This should likely be patch 1 in order for reviewers to have the
appropriate context.
>
> Signed-off-by: Dongwon Kim
> ---
> Documentation/hyper
54 matches
Mail list logo
