Jani Nikula writes:
> On Tue, 07 Nov 2023, Sam James wrote:
>> GCC 14 introduces a new -Walloc-size included in -Wextra which errors out
>> like:
>> ```
>> drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c: In function
>> ‘eb_copy_relocations’:
>> drivers/gpu/drm/i915/gem/i915_gem_execbuffer.c:1
https://bugzilla.kernel.org/show_bug.cgi?id=218133
Michael Pollind (mpoll...@gmail.com) changed:
What|Removed |Added
Kernel Version||Linux version
https://bugzilla.kernel.org/show_bug.cgi?id=218133
Michael Pollind (mpoll...@gmail.com) changed:
What|Removed |Added
Summary|kernel panic when opening |kernel panic when o
https://bugzilla.kernel.org/show_bug.cgi?id=218133
Michael Pollind (mpoll...@gmail.com) changed:
What|Removed |Added
Summary|kernel panic when opening |kernel panic when o
https://bugzilla.kernel.org/show_bug.cgi?id=218133
Bug ID: 218133
Summary: kernel panic when opening spotify 6.5.0.10.12 ubuntu
23.10
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status:
This reverts commit 36245bd02e88e68ac5955c2958c968879d7b75a9.
Signed-off-by: Luben Tuikov
---
include/drm/drm_print.h | 14 --
1 file changed, 14 deletions(-)
diff --git a/include/drm/drm_print.h b/include/drm/drm_print.h
index e8fe60d0eb8783..a93a387f8a1a15 100644
--- a/include/drm
On Fri, 10 Nov 2023 18:27:08 -0800 Mina Almasry wrote:
> Thanks for the clear requirement. I clearly had something different in mind.
>
> Might be dumb suggestions, but instead of creating a new ndo that we
> maybe end up wanting to deprecate once the queue API is ready, how
> about we use either
On Fri, Nov 10, 2023 at 3:13 PM Jakub Kicinski wrote:
>
> My brain is slightly fried after trying to catch up on the thread
> for close to 2h. So forgive me if I'm missing something.
> This applies to all emails I'm about to send :)
>
> On Sun, 5 Nov 2023 18:44:11 -0800 Mina Almasry wrote:
> > +
On Fri, Nov 10, 2023 at 3:20 PM Jakub Kicinski wrote:
>
> On Sun, 5 Nov 2023 18:44:03 -0800 Mina Almasry wrote:
> > --- a/include/linux/netdevice.h
> > +++ b/include/linux/netdevice.h
> > @@ -52,6 +52,8 @@
> > #include
> > #include
> > #include
> > +#include
> > +#include
> >
> > struct
> -Original Message-
> From: Krzysztof Kozlowski
> ExynosAutov9 reuses several devices from older designs, thus historically we
> kept the old (block's) compatible only. This works fine and there is no bug
> here, however guidelines expressed in
> Documentation/devicetree/bindings/writ
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Exynos850 reuses several devices from older designs, thus historically we
> kept the old (block's) compatible only. This works fine and there is no bug
> here, however guidelines expressed in
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Exynos7885 reuses several devices from older designs, thus historically we
> kept the old (block's) compatible only. This works fine and there is no bug
> here, however guidelines expressed i
> -Original Message-
> From: Krzysztof Kozlowski
> Exynos7 reuses several devices from older designs, thus historically we kept
> the old (block's) compatible only. This works fine and there is no bug here,
> however guidelines expressed in
> Documentation/devicetree/bindings/writing-b
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Exynos5433 reuses several devices from older designs, thus historically we
> kept the old (block's) compatible only. This works fine and there is no bug
> here, however guidelines expressed i
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines exp
> -Original Message-
> From: Krzysztof Kozlowski
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines expressed in
> Documentation/devicetree/binding
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines exp
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines exp
> -Original Message-
> From: Krzysztof Kozlowski
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines expressed in
> Documentation/devicetree/binding
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines exp
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines exp
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines exp
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:14 PM
(...)
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelin
> -Original Message-
> From: Krzysztof Kozlowski
> Sent: Wednesday, November 8, 2023 4:13 PM
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine and
> there is no bug here, however guidelines exp
On Sun, 5 Nov 2023 18:44:03 -0800 Mina Almasry wrote:
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -52,6 +52,8 @@
> #include
> #include
> #include
> +#include
> +#include
>
> struct netpoll_info;
> struct device;
> @@ -808,6 +810,84 @@ bool rps_may_expire_fl
On Sun, 5 Nov 2023 18:44:07 -0800 Mina Almasry wrote:
> #include
> #include
> +#include
> +#include
> /**
> * DOC: skb checksums
> @@ -3402,15 +3404,38 @@ static inline void skb_frag_off_copy(skb_frag_t
> *fragto,
> fragto->bv_offset = fragfrom->bv_offset;
> }
>
> +/* Returns t
On Tue, 7 Nov 2023 11:53:22 -0800 Mina Almasry wrote:
> My bad on not including some docs about this. The next version should
> have the commit message beefed up to explain all this, or a docs
> patch.
Yes, please. Would be great to have the user facing interface well
explained under Documentation
On Sun, 5 Nov 2023 18:44:09 -0800 Mina Almasry wrote:
> + if (!skb_frags_not_readable(skb)) {
nit: maybe call the helper skb_frags_readable() and flip
the polarity, avoid double negatives.
On Sun, 5 Nov 2023 18:44:01 -0800 Mina Almasry wrote:
> diff --git a/include/net/page_pool/types.h b/include/net/page_pool/types.h
> index 6fc5134095ed..d4bea053bb7e 100644
> --- a/include/net/page_pool/types.h
> +++ b/include/net/page_pool/types.h
> @@ -60,6 +60,8 @@ struct page_pool_params {
>
On Sun, 5 Nov 2023 18:44:11 -0800 Mina Almasry wrote:
> + if (ynl_subscribe(*ys, "mgmt"))
> + goto err_close;
Why? :)
On Tue, 7 Nov 2023 14:23:20 -0800 Stanislav Fomichev wrote:
> Can we mark a socket as devmem-only? Do we have any use-case for those
> hybrid setups? Or, let me put it that way: do we expect API callers
> to handle both linear and non-linear cases correctly?
> As a consumer of the previous versions
On Sun, 5 Nov 2023 18:44:02 -0800 Mina Almasry wrote:
> + -
> +name: queues
> +doc: receive queues to bind the dma-buf to.
> +type: u32
> +multi-attr: true
I think that you should throw in the queue type.
I know you made the op imply RX:
> +-
> + nam
On Sun, 5 Nov 2023 18:44:05 -0800 Mina Almasry wrote:
> +static int mp_dmabuf_devmem_init(struct page_pool *pool)
> +{
> + struct netdev_dmabuf_binding *binding = pool->mp_priv;
> +
> + if (!binding)
> + return -EINVAL;
> +
> + if (pool->p.flags & PP_FLAG_DMA_MAP ||
> +
On Thu, 09 Nov 2023 12:05:37 +0100 Paolo Abeni wrote:
> > I suppose we just disagree on the elegance of the API.
>
> FWIW, I think sockopt +cmsg is the right API.
FWIW it's fine by me as well.
My brain is slightly fried after trying to catch up on the thread
for close to 2h. So forgive me if I'm missing something.
This applies to all emails I'm about to send :)
On Sun, 5 Nov 2023 18:44:11 -0800 Mina Almasry wrote:
> + trigger_device_reset();
The user space must not be responsible
The pull request you sent on Fri, 10 Nov 2023 23:23:48 +0100:
> http://git.kernel.org/pub/scm/linux/kernel/git/deller/linux-fbdev.git
> tags/fbdev-for-6.7-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/18553507f60f4f51f071644621a58836eb59e28c
Thank you!
--
Deet
The pull request you sent on Fri, 10 Nov 2023 21:48:42 +0100:
> git://anongit.freedesktop.org/drm/drm tags/drm-next-2023-11-10
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/c0d12d769299e1e08338988c7745009e0db2a4a0
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
Hi--
On 11/10/23 07:55, André Almeida wrote:
> Document what each amdgpu driver reset method does.
>
> Signed-off-by: André Almeida
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
>
tree: git://anongit.freedesktop.org/drm-intel drm-intel-gt-next
head: 968853033d8aa4dbb80fbafa6f5d9b6a0ea21272
commit: 968853033d8aa4dbb80fbafa6f5d9b6a0ea21272 [6/6] drm/i915: Implement
fdinfo memory stats printing
config: x86_64-randconfig-122-2023
(https://download.01.org/0day-ci/archiv
The following changes since commit be3ca57cfb777ad820c6659d52e60bbdd36bf5ff:
Merge tag 'media/v6.7-1' of
git://git.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-media (2023-11-06
15:06:06 -0800)
are available in the Git repository at:
http://git.kernel.org/pub/scm/linux/kernel/git/dell
On 2023-11-10 12:18, Hamza Mahfooz wrote:
For features that are implemented primarily in DMUB (e.g. PSR), it is
useful to be able to trace them at a DMUB level from the kernel,
especially when debugging issues. So, introduce a debugfs interface that
is able to read and set the DMUB trace mask
Hi,
On Fri, Nov 10, 2023 at 1:46 AM Cong Yang
wrote:
>
> The refresh reported by modotest is 60.46Hz, and the actual measurement
s/modotets/modetest/
> is 60.01Hz, which is outside the expected tolerance. Adjust hporch and
> pixel clock to fix it. After repair, modetest and actual measurement w
On Thu, Nov 09, 2023 at 10:00:05AM +0100, Neil Armstrong wrote:
> Now this bindings is referred from amlogic,meson-gx-hhi-sysctrl.yaml and is
> documented as a subnode of a simple-mfd, drop the invalid reg property.
Why is it invalid? It's preferred to have 'reg' in MFDs even if Linux
doesn't use
Hi Linus
Dave's vpn to the big machine died, so it's on me to do fixes pr this and
next week while everyone else is at plumbers.
drm fixes for 6.7-rc1
- big pile of amd fixes, but mostly hw support newly added in 6.7
- i915 fixes, mostly minor things
- qxl memory leak fix
- vc4 uaf fix in mock h
On Wed, 08 Nov 2023 11:43:38 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:37 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:36 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:35 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:34 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:33 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:32 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:31 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, 08 Nov 2023 11:43:30 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, Nov 08, 2023 at 11:43:29AM +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree
On Wed, 08 Nov 2023 11:43:28 +0100, Krzysztof Kozlowski wrote:
> Samsung Exynos SoC reuses several devices from older designs, thus
> historically we kept the old (block's) compatible only. This works fine
> and there is no bug here, however guidelines expressed in
> Documentation/devicetree/bin
On Wed, Nov 08, 2023 at 02:18:28PM +0100, Maarten Lankhorst wrote:
> Hi Dave, Daniel,
>
> drm-misc-next-fixes is empty, have a pull request for drm-misc-fixes.
>
> Cheers,
> ~Maarten
>
> drm-misc-fixes-2023-11-08:
> drm-misc-fixes for v6.7-rc1:
>
> - drm-misc-fixes from 2023-11-02 + a single qx
On Fri, Nov 10, 2023 at 02:07:03PM -0500, Alex Deucher wrote:
> Hi Dave, Sima,
>
> Fixes for 6.7. A bit bigger than this would normally be at this point, but
> these
> are mainly fixes for new IPs added or enabled in 6.7 so they should be mostly
> self-contained. The rest is the usual general fi
On 2023-11-09 04:20, Pekka Paalanen wrote:
On Wed, 8 Nov 2023 11:27:35 -0500
Harry Wentland wrote:
On 2023-11-08 11:19, Pekka Paalanen wrote:
On Wed, 8 Nov 2023 09:31:17 -0500
Harry Wentland wrote:
On 2023-11-08 06:40, Sebastian Wick wrote:
On Wed, Nov 8, 2023 at 11:16 AM Pekka Paal
On 09/11/23 19:05, Arthur Grillo wrote:
>
>
> On 08/11/23 13:36, Harry Wentland wrote:
>> Debugging LUT math is much easier when we can unit test
>> it. Add kunit functionality to VKMS and add tests for
>> - get_lut_index
>> - lerp_u16
>>
>> v3:
>> - Use include way of testing static functi
On Thu, Nov 09, 2023 at 10:00:03AM +0100, Neil Armstrong wrote:
> Add a thirst example covering the meson-axg-hhi-sysctrl variant and more
> importantly the phy subnode.
>
> Signed-off-by: Neil Armstrong
> ---
> .../soc/amlogic/amlogic,meson-gx-hhi-sysctrl.yaml | 41
> ++
>
In order to pass functions to kunit_add_action(), they need to be of the
kunit_action_t type. While casting the function pointer can work, it
will break control-flow integrity.
vc4_mock already defines such a wrapper for drm_dev_unregister(), but it
involves less boilerplate to use the new macro,
In order to pass functions to kunit_add_action(), they need to be of the
kunit_action_t type. While casting the function pointer can work, it
will break control-flow integrity.
drm_kunit_helpers already defines wrappers, but we now have a macro
which does this automatically. Using this greatly red
KUnit's deferred action API accepts a void(*)(void *) function pointer
which is called when the test is exited. However, we very frequently
want to use existing functions which accept a single pointer, but which
may not be of type void*. While this is probably dodgy enough to be on
the wrong side o
Introduce unit tests for the drm_mode_create_dvi_i_properties() function to
ensure
the proper creation of DVI-I specific connector properties.
Signed-off-by: Dipam Turkar
---
drivers/gpu/drm/tests/drm_connector_test.c | 38 ++
1 file changed, 38 insertions(+)
diff --git a/d
Cyernet T10C has a bad default PWM frequency causing the display to
strobe when the brightness is less than 100%. Create a new quirk to use
the value from the BIOS rather than the default register value.
Signed-off-by: Allen Ballway
---
V1 -> V2: Fix style issues.
.../gpu/drm/i915/display/intel
On Fri, 2023-11-03 at 19:25 +0100, Philipp Stanner wrote:
> Currently, tha ast-driver just maps the PCI-dev's regions with
> pcim_iomap(). It does not actually reserve the regions exclusively
> with, e.g., pci_request_regions().
>
> Replace the calls to pcim_iomap() with ones to pcim_iomap_regions
Hi Dave, Sima,
Fixes for 6.7. A bit bigger than this would normally be at this point, but
these
are mainly fixes for new IPs added or enabled in 6.7 so they should be mostly
self-contained. The rest is the usual general fixes.
The following changes since commit 9ccde17d46554dbb2757c427f2cdf6768
Making i915 use drm_gem_create_mmap_offset() instead of its custom
implementations for associating GEM object with a fake offset.
Signed-off-by: Dipam Turkar
---
drivers/gpu/drm/i915/gem/i915_gem_mman.c | 21 -
drivers/gpu/drm/i915/gem/i915_gem_mman.h | 4
drivers/gpu/d
Hi Dipam,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Dipam-Turkar/Remove-custom-dumb_map_offset-implementations-in-i915-driver/20231110-185942
base: git://anongit.freedesktop.org
On Fri, Nov 10, 2023 at 08:50:58AM +0100, Neil Armstrong wrote:
> On 09/11/2023 18:34, Conor Dooley wrote:
> > On Thu, Nov 09, 2023 at 10:00:03AM +0100, Neil Armstrong wrote:
> > > Add a thirst example covering the meson-axg-hhi-sysctrl variant and more
> >
> > What on earth is a thirst example? S
The Single Root I/O Virtualization (SR-IOV) extension to the PCI
Express (PCIe) specification suite is supported starting from 12th
generation of Intel Graphics processors.
This RFC aims to explain how do we want to add support for SR-IOV
to the new Xe driver and to propose related additions to th
Hi Dipam,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Dipam-Turkar/Remove-custom-dumb_map_offset-implementations-in-i915-driver/20231110-185942
base: git://anongit.freedesktop.org/drm
tree: git://anongit.freedesktop.org/drm-intel drm-intel-gt-next
head: 968853033d8aa4dbb80fbafa6f5d9b6a0ea21272
commit: e4ae85e364fc652ea15d85b0f3a6da304c9b5ce7 [1/6] drm/i915: Add ability
for tracking buffer objects per client
config: x86_64-buildonly-randconfig-001-20231110
(https
On Tue, Oct 31, 2023 at 8:55 AM Gurchetan Singh
wrote:
>
>
> On Sun, Oct 22, 2023 at 4:50 PM Dmitry Osipenko <
> dmitry.osipe...@collabora.com> wrote:
>
>> On 10/18/23 21:17, Gurchetan Singh wrote:
>> > There are two problems with the current method of determining the
>> > virtio-gpu debug name.
Document what each amdgpu driver reset method does.
Signed-off-by: André Almeida
---
v2: Add more details and small correction (Alex)
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 25 +
1 file changed, 25 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
b/drivers
For features that are implemented primarily in DMUB (e.g. PSR), it is
useful to be able to trace them at a DMUB level from the kernel,
especially when debugging issues. So, introduce a debugfs interface that
is able to read and set the DMUB trace mask dynamically at runtime and
document how to use
On Fri, Nov 10, 2023 at 10:56 AM André Almeida wrote:
>
> Document what each amdgpu driver reset method does.
>
> Signed-off-by: André Almeida
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu.h | 20
> 1 file changed, 20 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amd
Hi Jingfeng,
You recently added the loongson drm driver to the Linux kernel tree.
Unlike all other loongson drivers, the drm driver doesn't have any
dependency set on the platform or architecture, and is therefore
proposed on all architectures. As far as I understand, this driver is
only useful on
On 11/10/23 09:50, Christian König wrote:
Am 09.11.23 um 19:34 schrieb Danilo Krummrich:
On 11/9/23 17:03, Christian König wrote:
Am 09.11.23 um 16:50 schrieb Thomas Hellström:
[SNIP]
Did we get any resolution on this?
FWIW, my take on this is that it would be possible to get GPUVM to work
Hi Dipam,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-tip/drm-tip]
url:
https://github.com/intel-lab-lkp/linux/commits/Dipam-Turkar/Remove-custom-dumb_map_offset-implementations-in-i915-driver/20231110-185942
base: git://anongit.freedesktop.org/drm
On 11/10/23 11:52, Thomas Hellström wrote:
On 11/10/23 11:42, Christian König wrote:
Am 10.11.23 um 10:39 schrieb Thomas Hellström:
[SNIP]
I was thinking more of the general design of a base-class that needs to be
refcounted. Say a driver vm that inherits from gpu-vm, gem_object and yet
On 11/7/2023 5:35 AM, Jacek Lawrynowicz wrote:
Remove job_done thread and replace it with generic callback based
mechanism.
Signed-off-by: Jacek Lawrynowicz
---
drivers/accel/ivpu/ivpu_drv.c | 30 ++---
drivers/accel/ivpu/ivpu_drv.h | 3 +-
drivers/accel/ivpu/ivpu_hw_37xx.c | 29
On 11/10/23 10:39, Thomas Hellström wrote:
On 11/10/23 09:50, Christian König wrote:
Am 09.11.23 um 19:34 schrieb Danilo Krummrich:
On 11/9/23 17:03, Christian König wrote:
Am 09.11.23 um 16:50 schrieb Thomas Hellström:
[SNIP]
Did we get any resolution on this?
FWIW, my take on this is t
DRM atomic API should reject modesetting during an async flip, so
test if the kernel properly rejects to flip with prop changes.
Signed-off-by: André Almeida
---
tests/kms_async_flips.c | 68 +
1 file changed, 68 insertions(+)
diff --git a/tests/kms_async
From: Simon Ser
This adds a simple test for DRM_MODE_PAGE_FLIP_ASYNC with the
atomic uAPI.
Signed-off-by: Simon Ser
Signed-off-by: André Almeida
---
include/drm-uapi/drm.h | 8
tests/kms_async_flips.c | 37 +
2 files changed, 45 insertions(+)
di
This series adds tests for async page flip for DRM Atomic API. Kernel patches:
https://lore.kernel.org/dri-devel/20231025005318.293690-1-andrealm...@igalia.com/
André Almeida (1):
tests/kms_async_flips: Add test for atomic prop changes
Simon Ser (1):
tests/kms_async_flips: add atomic test
i
Document what each amdgpu driver reset method does.
Signed-off-by: André Almeida
---
drivers/gpu/drm/amd/amdgpu/amdgpu.h | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu.h
b/drivers/gpu/drm/amd/amdgpu/amdgpu.h
index a79d53bdbe13..500f86
On Wed, Nov 08, 2023 at 04:04:14PM +0200, Jani Nikula wrote:
>
> Hi Dave & Daniel -
>
> I see Dave already sent the pull request for v6.7-rc1 fixes, but here's
> some more.
>
> drm-intel-next-fixes-2023-11-08:
> drm/i915 fixes for v6.7-rc1:
> - Fix null dereference when perf interface is not ava
Hi Karolina,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-misc/drm-misc-next]
[also build test WARNING on drm/drm-next drm-exynos/exynos-drm-next
drm-intel/for-linux-next drm-intel/for-linux-next-fixes drm-tip/drm-tip
linus/master v6.6 next-20231110
On 10/11/2023 15:30, Chris Morgan wrote:
> On Fri, Nov 10, 2023 at 02:14:23PM +0100, Krzysztof Kozlowski wrote:
>>> +
>>> +/delete-node/ &adc_keys;
>>> +
>>> +&chosen {
>>> + /delete-property/ stdout-path;
>>> +};
>>
>> If you have to delete so many nodes and properties, this means your
>> commo
On 11/7/23 23:03, Mina Almasry wrote:
On Tue, Nov 7, 2023 at 2:55 PM David Ahern wrote:
On 11/7/23 3:10 PM, Mina Almasry wrote:
On Mon, Nov 6, 2023 at 3:44 PM David Ahern wrote:
On 11/5/23 7:44 PM, Mina Almasry wrote:
diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
inde
On Mon, 30 Oct 2023 02:01:58 +0300
Dmitry Osipenko wrote:
> @@ -238,6 +308,20 @@ void drm_gem_shmem_put_pages(struct drm_gem_shmem_object
> *shmem)
> if (refcount_dec_not_one(&shmem->pages_use_count))
> return;
>
> + /*
> + * Destroying the object is a special case
On 10/11/2023 15:28, Chris Morgan wrote:
> On Fri, Nov 10, 2023 at 02:11:58PM +0100, Krzysztof Kozlowski wrote:
>> On 09/11/2023 22:50, Chris Morgan wrote:
>>> From: Chris Morgan
>>>
>>> Update the NewVision NV3051D compatible strings by adding a new panel,
>>> the powkiddy,rk2023-panel, and remov
Hi,
On Thu, Nov 9, 2023 at 1:26 AM Xuxin Xiong
wrote:
>
> For "auo,b101uan08.3" this panel, it is stipulated in the panel spec that
> MIPI needs to keep the LP11 state before the lcm_reset pin is pulled high.
>
> BUG=b:309908277
> TEST=emerge-kukui chromeos-kernel-5_10
BUG= and TEST= are not som
On Wed, Nov 08, 2023 at 02:42:03PM +0100, Marco Pagani wrote:
> This patch introduces an initial KUnit test suite for GEM objects
> backed by shmem buffers.
>
> Suggested-by: Javier Martinez Canillas
> Signed-off-by: Marco Pagani
>
> v2:
> - Improved description of test cases
> - Cleaner error
On 09/11/2023 10:25, AngeloGioacchino Del Regno wrote:
> Changes in v3:
> - Fixed the order of set_opp/opp_put in patch [5/6]
> - Clearly specified MediaTek SoC models in patches [4/6], [6/6]
> - Reordered clk_disable() for suspend in patch [3/6]
> - Fixed blank line removal and alignment in pa
On Fri, Nov 10, 2023 at 02:14:23PM +0100, Krzysztof Kozlowski wrote:
> On 09/11/2023 22:50, Chris Morgan wrote:
> > From: Chris Morgan
> >
> > Add support for the Powkiddy RK2023. The Powkiddy RK2023 is a handheld
> > gaming device with a 3.5 inch screen powered by the Rockchip RK3566
> > SoC. Th
On Fri, Nov 10, 2023 at 02:11:58PM +0100, Krzysztof Kozlowski wrote:
> On 09/11/2023 22:50, Chris Morgan wrote:
> > From: Chris Morgan
> >
> > Update the NewVision NV3051D compatible strings by adding a new panel,
> > the powkiddy,rk2023-panel, and removing another entry, the
> > anbernic,rg353v-
On Friday, November 10th, 2023 at 15:01, Maxime Ripard
wrote:
> On Fri, Nov 10, 2023 at 11:21:15AM +, Simon Ser wrote:
>
> > On Thursday, November 9th, 2023 at 20:17, Maxime Ripard mrip...@kernel.org
> > wrote:
> >
> > > > Can we add another function pointer to the struct drm_driver (or
>
Hi,
On Fri, Nov 10, 2023 at 04:33:23PM +0530, Dipam Turkar wrote:
> Introduce unit tests for the drm_mode_create_dvi_i_properties() function to
> ensure
> the proper creation of DVI-I specific connector properties.
>
> Signed-off-by: Dipam Turkar
> ---
> drivers/gpu/drm/tests/drm_connector_tes
1 - 100 of 178 matches
Mail list logo
