Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-14 Thread Geert Uytterhoeven
Hi Maxime, On Fri, Jun 14, 2024 at 10:35 AM Maxime Ripard wrote: > On Fri, Jun 14, 2024 at 08:58:26AM GMT, Geert Uytterhoeven wrote: > > Looks like the top commit of last drm-misc PR [1] is part of the > > drm-misc-next branch. but not of the for-linux-next branch, while > > Stephen pulls the

Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-14 Thread Maxime Ripard
Hi, On Fri, Jun 14, 2024 at 08:58:26AM GMT, Geert Uytterhoeven wrote: > Hi Stephen and Maxime, > > On Fri, Jun 14, 2024 at 12:00 AM Stephen Rothwell > wrote: > > On Thu, 13 Jun 2024 11:48:15 +0200 Geert Uytterhoeven > > wrote: > > > > > Has the drm-misc git repo moved? > > > > > > > > It

Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-14 Thread Geert Uytterhoeven
Hi Stephen and Maxime, On Fri, Jun 14, 2024 at 12:00 AM Stephen Rothwell wrote: > On Thu, 13 Jun 2024 11:48:15 +0200 Geert Uytterhoeven > wrote: > > > > Has the drm-misc git repo moved? > > > > > > It moved to gitlab recently, the new url is > > >

Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-13 Thread Stephen Rothwell
Hi Geert, On Thu, 13 Jun 2024 11:48:15 +0200 Geert Uytterhoeven wrote: > > > > Has the drm-misc git repo moved? > > > > It moved to gitlab recently, the new url is > > g...@gitlab.freedesktop.org:drm/misc/kernel.git > > Time to tell Stephen... linux-next has been using that URL for some

Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-13 Thread Jocelyn Falempe
On 13/06/2024 11:32, Geert Uytterhoeven wrote: Hi Jocelyn, On Thu, Jun 13, 2024 at 10:38 AM Jocelyn Falempe wrote: On 12/06/2024 15:54, Geert Uytterhoeven wrote: If drm/panic is enabled, a user-friendly message is shown on screen when a kernel panic occurs, together with an ASCII art

Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-13 Thread Geert Uytterhoeven
Hi Jocelyn, CC sfr On Thu, Jun 13, 2024 at 11:41 AM Jocelyn Falempe wrote: > On 13/06/2024 11:32, Geert Uytterhoeven wrote: > > On Thu, Jun 13, 2024 at 10:38 AM Jocelyn Falempe > > wrote: > >> On 12/06/2024 15:54, Geert Uytterhoeven wrote: > >>> If drm/panic is enabled, a user-friendly

Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-13 Thread Geert Uytterhoeven
Hi Jocelyn, On Thu, Jun 13, 2024 at 10:38 AM Jocelyn Falempe wrote: > On 12/06/2024 15:54, Geert Uytterhoeven wrote: > > If drm/panic is enabled, a user-friendly message is shown on screen when > > a kernel panic occurs, together with an ASCII art penguin logo. > > Of course we can do better ;-)

Re: [PATCH 0/3] drm/panic: Fixes and graphical logo

2024-06-13 Thread Jocelyn Falempe
On 12/06/2024 15:54, Geert Uytterhoeven wrote: Hi all, If drm/panic is enabled, a user-friendly message is shown on screen when a kernel panic occurs, together with an ASCII art penguin logo. Of course we can do better ;-) Hence this patch series extends drm/panic to draw the

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-05-21 Thread Jarkko Sakkinen
On Thu Feb 29, 2024 at 12:55 AM EET, Helen Koike wrote: > Dear Kernel Community, > > This patch introduces a `.gitlab-ci` file along with a `ci/` folder, defining > a > basic test pipeline triggered by code pushes to a GitLab-CI instance. This > initial version includes static checks (checkpatch

Re: [PATCH 0/3] HW layer refactor

2024-05-17 Thread Jacek Lawrynowicz
Applied to drm-misc-next On 15.05.2024 13:30, Jacek Lawrynowicz wrote: > The NPU device consists of two parts: NPU buttress and NPU IP. > Buttress is a platform specific part that integrates the NPU IP with > the CPU. > NPU IP is the platform agnostic part that does the inference. > > This

Re: [PATCH 0/3] dt-bindings: display: panel: constrain 'reg'

2024-05-15 Thread neil . armstrong
On 14/05/2024 11:07, Krzysztof Kozlowski wrote: On 14/05/2024 10:44, Neil Armstrong wrote: On 13/05/2024 18:41, Dmitry Baryshkov wrote: On Mon, 13 May 2024 at 16:17, Rob Herring wrote: On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: Hi, Cleanups for display panel

Re: [PATCH 0/3] dt-bindings: display: panel: constrain 'reg'

2024-05-14 Thread Krzysztof Kozlowski
On 14/05/2024 10:44, Neil Armstrong wrote: > On 13/05/2024 18:41, Dmitry Baryshkov wrote: >> On Mon, 13 May 2024 at 16:17, Rob Herring wrote: >>> >>> On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: Hi, Cleanups for display panel bindings. Rob, maybe

Re: [PATCH 0/3] dt-bindings: display: panel: constrain 'reg'

2024-05-14 Thread Neil Armstrong
On 13/05/2024 18:41, Dmitry Baryshkov wrote: On Mon, 13 May 2024 at 16:17, Rob Herring wrote: On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: Hi, Cleanups for display panel bindings. Rob, maybe you could take entire set if it applies? I based it on linux-next, so letl

Re: [PATCH 0/3] dt-bindings: display: panel: constrain 'reg'

2024-05-13 Thread Dmitry Baryshkov
On Mon, 13 May 2024 at 16:17, Rob Herring wrote: > > On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: > > Hi, > > > > Cleanups for display panel bindings. > > > > Rob, maybe you could take entire set if it applies? I based it on > > linux-next, so letl me know if I need to

Re: [PATCH 0/3] dt-bindings: display: panel: constrain 'reg'

2024-05-13 Thread Rob Herring
On Thu, May 09, 2024 at 11:42:50AM +0200, Krzysztof Kozlowski wrote: > Hi, > > Cleanups for display panel bindings. > > Rob, maybe you could take entire set if it applies? I based it on > linux-next, so letl me know if I need to rebase on your for-next. Applied. These 2 don't exist in my tree:

Re: [PATCH 0/3] drm: Multiple documentation update

2024-04-09 Thread Louis Chauvet
Le 09/04/24 - 13:18, Jani Nikula a écrit : > On Tue, 09 Apr 2024, Louis Chauvet wrote: > > PATCH 1 and PATCH 2 focus on the rotation property. The rotation property > > can be challenging to understand, especially when it is combined with > > reflections. These patches aim to provide clearer

Re: [PATCH 0/3] drm: Multiple documentation update

2024-04-09 Thread Jani Nikula
On Tue, 09 Apr 2024, Louis Chauvet wrote: > PATCH 1 and PATCH 2 focus on the rotation property. The rotation property > can be challenging to understand, especially when it is combined with > reflections. These patches aim to provide clearer explanations and > examples to aid in comprehension.

Re: [PATCH 0/3] drm/edid & drm/display header spring cleaning

2024-04-08 Thread Jani Nikula
On Thu, 21 Mar 2024, Jani Nikula wrote: > Jani Nikula (3): > drm/displayid: move drm_displayid.h to drm_displayd_internal.h > drm/edid: move all internal declarations to drm_crtc_internal.h > drm/edid: group struct drm_edid based declarations together Resent as part of

Re: [PATCH 0/3] drm/mediatek: Fixes for DDP component search/destroy

2024-03-21 Thread AngeloGioacchino Del Regno
Il 01/02/24 13:53, AngeloGioacchino Del Regno ha scritto: This series performs some cleanups for DDP component CRTC search and correctly iounmaps the previously of_iomap() calls from drm_ddp_comp. Tested on MT8195 Cherry Tomato Hello CK, gentle ping for this series. Cheers, Angelo

Re: [PATCH 0/3] drm/panthor: Fix 3 issues reported by the kernel test bot

2024-03-11 Thread Boris Brezillon
On Mon, 4 Mar 2024 10:08:09 +0100 Boris Brezillon wrote: > Hello, > > Here are three trivial fixes for bugs reported by the intel kernel test > bot. > > Regards, > > Boris > > Boris Brezillon (3): > drm/panthor: Fix panthor_devfreq kerneldoc > drm/panthor: Explicitly include page.h for

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-03-04 Thread Guillaume Tucker
On 02/03/2024 10:48 pm, Gustavo Padovan wrote: On Friday, March 01, 2024 18:56 -03, Guillaume Tucker wrote: On 29/02/2024 17:28, Nicolas Dufresne wrote: Hi, Le jeudi 29 février 2024 à 16:16 +0200, Nikolai Kondrashov a écrit : On 2/29/24 2:20 PM, Guillaume Tucker wrote: Hello, On

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-03-03 Thread Guillaume Tucker
On 29/02/2024 17:28, Nicolas Dufresne wrote: > Hi, > > Le jeudi 29 février 2024 à 16:16 +0200, Nikolai Kondrashov a écrit : >> On 2/29/24 2:20 PM, Guillaume Tucker wrote: >>> Hello, >>> >>> On 28/02/2024 23:55, Helen Koike wrote: Dear Kernel Community, This patch introduces a

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-03-02 Thread Gustavo Padovan
On Friday, March 01, 2024 18:56 -03, Guillaume Tucker wrote: > On 29/02/2024 17:28, Nicolas Dufresne wrote: > > Hi, > > > > Le jeudi 29 février 2024 à 16:16 +0200, Nikolai Kondrashov a écrit : > >> On 2/29/24 2:20 PM, Guillaume Tucker wrote: > >>> Hello, > >>> > >>> On 28/02/2024 23:55, Helen

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Nicolas Dufresne
Hi, Le jeudi 29 février 2024 à 16:16 +0200, Nikolai Kondrashov a écrit : > On 2/29/24 2:20 PM, Guillaume Tucker wrote: > > Hello, > > > > On 28/02/2024 23:55, Helen Koike wrote: > > > Dear Kernel Community, > > > > > > This patch introduces a `.gitlab-ci` file along with a `ci/` folder, > > >

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Nikolai Kondrashov
On 2/29/24 01:07, Laurent Pinchart wrote: On Wed, Feb 28, 2024 at 07:55:24PM -0300, Helen Koike wrote: **Join Our Slack Channel:** We have a Slack channel, #gitlab-ci, on the KernelCI Slack instance https://kernelci.slack.com/ . Feel free to join and contribute to the conversation. The

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Sakari Ailus
Hi Laurent, Helen, On Thu, Feb 29, 2024 at 01:07:25AM +0200, Laurent Pinchart wrote: > > **Join Our Slack Channel:** > > We have a Slack channel, #gitlab-ci, on the KernelCI Slack instance > > https://kernelci.slack.com/ . > > Feel free to join and contribute to the conversation. The KernelCI

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Nikolai Kondrashov
On 2/29/24 2:25 PM, Laurent Pinchart wrote: On Thu, Feb 29, 2024 at 02:20:41PM +0200, Laurent Pinchart wrote: On Thu, Feb 29, 2024 at 12:53:38PM +0100, Guillaume Tucker wrote: On 29/02/2024 12:41, Mark Brown wrote: On Thu, Feb 29, 2024 at 01:19:19PM +0200, Laurent Pinchart wrote: On Thu, Feb

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Guillaume Tucker
Hello, On 28/02/2024 23:55, Helen Koike wrote: > Dear Kernel Community, > > This patch introduces a `.gitlab-ci` file along with a `ci/` folder, defining > a > basic test pipeline triggered by code pushes to a GitLab-CI instance. This > initial version includes static checks (checkpatch and

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Nikolai Kondrashov
On 2/29/24 1:19 PM, Laurent Pinchart wrote: On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote: On 2/29/24 11:34 AM, Laurent Pinchart wrote: On Thu, Feb 29, 2024 at 11:26:51AM +0200, Nikolai Kondrashov wrote: On 2/29/24 01:07, Laurent Pinchart wrote: On Wed, Feb 28, 2024 at

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Nikolai Kondrashov
On 2/29/24 11:34 AM, Laurent Pinchart wrote: On Thu, Feb 29, 2024 at 11:26:51AM +0200, Nikolai Kondrashov wrote: On 2/29/24 01:07, Laurent Pinchart wrote: On Wed, Feb 28, 2024 at 07:55:24PM -0300, Helen Koike wrote: **Join Our Slack Channel:** We have a Slack channel, #gitlab-ci, on the

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Nikolai Kondrashov
On 2/29/24 2:20 PM, Guillaume Tucker wrote: Hello, On 28/02/2024 23:55, Helen Koike wrote: Dear Kernel Community, This patch introduces a `.gitlab-ci` file along with a `ci/` folder, defining a basic test pipeline triggered by code pushes to a GitLab-CI instance. This initial version includes

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Guillaume Tucker
On 29/02/2024 12:41, Mark Brown wrote: > On Thu, Feb 29, 2024 at 01:19:19PM +0200, Laurent Pinchart wrote: >> On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote: > >>> Of course. You're also welcome to join the #kernelci channel on libera.chat. > >> Isn't that a bit pointless if

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Laurent Pinchart
On Thu, Feb 29, 2024 at 02:20:41PM +0200, Laurent Pinchart wrote: > On Thu, Feb 29, 2024 at 12:53:38PM +0100, Guillaume Tucker wrote: > > On 29/02/2024 12:41, Mark Brown wrote: > > > On Thu, Feb 29, 2024 at 01:19:19PM +0200, Laurent Pinchart wrote: > > >> On Thu, Feb 29, 2024 at 01:10:16PM +0200,

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Laurent Pinchart
On Thu, Feb 29, 2024 at 12:53:38PM +0100, Guillaume Tucker wrote: > On 29/02/2024 12:41, Mark Brown wrote: > > On Thu, Feb 29, 2024 at 01:19:19PM +0200, Laurent Pinchart wrote: > >> On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote: > > > >>> Of course. You're also welcome to

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Mark Brown
On Thu, Feb 29, 2024 at 01:19:19PM +0200, Laurent Pinchart wrote: > On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote: > > Of course. You're also welcome to join the #kernelci channel on libera.chat. > Isn't that a bit pointless if it's no the main IM channel ? It *was* the

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Laurent Pinchart
On Thu, Feb 29, 2024 at 01:10:16PM +0200, Nikolai Kondrashov wrote: > On 2/29/24 11:34 AM, Laurent Pinchart wrote: > > On Thu, Feb 29, 2024 at 11:26:51AM +0200, Nikolai Kondrashov wrote: > >> On 2/29/24 01:07, Laurent Pinchart wrote: > >>> On Wed, Feb 28, 2024 at 07:55:24PM -0300, Helen Koike

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Mark Brown
On Thu, Feb 29, 2024 at 09:39:01AM +, Sakari Ailus wrote: > On Thu, Feb 29, 2024 at 01:07:25AM +0200, Laurent Pinchart wrote: > > > We have a Slack channel, #gitlab-ci, on the KernelCI Slack instance > > > https://kernelci.slack.com/ . > > > Feel free to join and contribute to the

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Laurent Pinchart
On Thu, Feb 29, 2024 at 11:26:51AM +0200, Nikolai Kondrashov wrote: > On 2/29/24 01:07, Laurent Pinchart wrote: > > On Wed, Feb 28, 2024 at 07:55:24PM -0300, Helen Koike wrote: > >> **Join Our Slack Channel:** > >> We have a Slack channel, #gitlab-ci, on the KernelCI Slack instance > >>

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-29 Thread Maxime Ripard
On Thu, Feb 29, 2024 at 01:07:25AM +0200, Laurent Pinchart wrote: > > Chat Discussions > > > > > > For those interested in further discussions: > > > > **Join Our Slack Channel:** > > We have a Slack channel, #gitlab-ci, on the KernelCI Slack instance > >

Re: [PATCH 0/3] kci-gitlab: Introducing GitLab-CI Pipeline for Kernel Testing

2024-02-28 Thread Laurent Pinchart
Hi Helen, I appreciate the amount of work you've put into this, to improve testing of the kernel as a whole. I'll need more time to answer, but please see below for a quick comment already. On Wed, Feb 28, 2024 at 07:55:24PM -0300, Helen Koike wrote: > Dear Kernel Community, > > This patch

Re: [PATCH 0/3] Fixes for the komeda driver

2024-02-27 Thread Liviu Dudau
Hi Faiz, On Mon, Feb 19, 2024 at 03:39:12PM +0530, Faiz Abbas wrote: > The following patches add fixes to the komeda DPU driver. > > Patch 1 fixes an issue where the crtc always expects both pipelines to > always have remote nodes populated. > > Patch 2 is a cosmetic fix that ensures komeda

Re: [PATCH 0/3] drm/amdgpu: Use KMEM_CACHE instead of kmem_cache_create

2024-02-21 Thread Alex Deucher
Applied. Thanks! On Wed, Feb 21, 2024 at 6:08 AM Christian König wrote: > > Am 21.02.24 um 10:59 schrieb Kunwu Chan: > > For where the cache name and the structure name match. > > Use the new KMEM_CACHE() macro instead of direct kmem_cache_create > > to simplify the creation of SLAB caches. > >

Re: [PATCH 0/3] drm/amdgpu: Use KMEM_CACHE instead of kmem_cache_create

2024-02-21 Thread Christian König
Am 21.02.24 um 10:59 schrieb Kunwu Chan: For where the cache name and the structure name match. Use the new KMEM_CACHE() macro instead of direct kmem_cache_create to simplify the creation of SLAB caches. Reviewed-by: Christian König for the entire series. Kunwu Chan (3): drm/amdgpu:

Re: [PATCH 0/3] drm/panel: add one more Leadtek panel, the ltk101b4029w

2024-02-16 Thread Heiko Stuebner
On Thu, 15 Feb 2024 10:05:12 +0100, Heiko Stuebner wrote: > Similar in setup to the ltk500hd1829, group it with this driver. > > Heiko Stuebner (3): > drm/panel: ltk500hd1829: make room for more similar panels > dt-bindings: display: ltk500hd1829: add variant compatible for > ltk101b4029w

Re: [PATCH 0/3] drm/panel: add one more Leadtek panel, the ltk101b4029w

2024-02-15 Thread Quentin Schulz
Hi Heiko, On 2/15/24 10:05, Heiko Stuebner wrote: Similar in setup to the ltk500hd1829, group it with this driver. > Heiko Stuebner (3): drm/panel: ltk500hd1829: make room for more similar panels dt-bindings: display: ltk500hd1829: add variant compatible for ltk101b4029w

Re: [PATCH 0/3] accel/ivpu fixes for 6.8-rc1

2024-01-25 Thread Jacek Lawrynowicz
Applied to drm-misc-fixes On 22.01.2024 13:09, Jacek Lawrynowicz wrote: > Stability fixes for reset, recovery and unbind. > > Jacek Lawrynowicz (3): > accel/ivpu: Fix dev open/close races with unbind > accel/ivpu: Improve stability of ivpu_submit_ioctl() > accel/ivpu: Improve recovery and

Re: [PATCH 0/3] Update LLVM Phabricator and Bugzilla links

2024-01-12 Thread Alex Deucher
On Tue, Jan 9, 2024 at 5:26 PM Nathan Chancellor wrote: > > This series updates all instances of LLVM Phabricator and Bugzilla links > to point to GitHub commits directly and LLVM's Bugzilla to GitHub issue > shortlinks respectively. > > I split up the Phabricator patch into BPF selftests and the

Re: [PATCH 0/3] Update LLVM Phabricator and Bugzilla links

2024-01-11 Thread Fangrui Song
On Wed, Jan 10, 2024 at 4:46 PM Kees Cook wrote: > > On Tue, Jan 09, 2024 at 03:16:28PM -0700, Nathan Chancellor wrote: > > This series updates all instances of LLVM Phabricator and Bugzilla links > > to point to GitHub commits directly and LLVM's Bugzilla to GitHub issue > > shortlinks

Re: [PATCH 0/3] Update LLVM Phabricator and Bugzilla links

2024-01-10 Thread Kees Cook
On Tue, Jan 09, 2024 at 03:16:28PM -0700, Nathan Chancellor wrote: > This series updates all instances of LLVM Phabricator and Bugzilla links > to point to GitHub commits directly and LLVM's Bugzilla to GitHub issue > shortlinks respectively. > > I split up the Phabricator patch into BPF

Re: [PATCH 0/3] Add Support for RG-ARC Panel

2023-12-11 Thread Neil Armstrong
Hi, On Fri, 08 Dec 2023 09:48:44 -0600, Chris Morgan wrote: > From: Chris Morgan > > Add support for the Anbernic RG-ARC display panel as used in the > RG-ARC S and RG-ARC D handheld gaming devices from Anbernic. > > Chris Morgan (3): > drm/panel: st7701: Fix AVCL calculation >

Re: [PATCH 0/3] A few fixes for transparent bridge support

2023-12-07 Thread Dmitry Baryshkov
On Tue, 05 Dec 2023 13:13:33 -0700, Nathan Chancellor wrote: > This series fixes two Kconfig issues that I noticed with the selection > of CONFIG_DRM_AUX{,_HPD}_BRIDGE along with a fix for a sparse report > that I noticed while seeing if these had already been resolved. > Applied to

Re: [PATCH 0/3] drm/panel: ilitek-ili9881c: Support Ampire AM8001280G LCD panel

2023-12-05 Thread Neil Armstrong
Hi, On Thu, 23 Nov 2023 18:08:04 +0100, Philipp Zabel wrote: > Add support for Ampire AM8001280G LCD panels to the Ilitek ILI9881C > driver. > > Also set prepare_prev_first, to make sure that the DSI host controller > is initialized to LP-11 before the panel is powered up. Tested to work > with

Re: [PATCH 0/3] drm/bridge: ti-sn65dsi86: Some updates

2023-11-29 Thread Uwe Kleine-König
Hello Laurent, On Wed, Nov 29, 2023 at 02:45:33AM +0200, Laurent Pinchart wrote: > On Fri, Nov 24, 2023 at 09:56:55AM +0100, Neil Armstrong wrote: > > On 23/11/2023 18:54, Uwe Kleine-König wrote: > > > Hello, > > > > > > this is a series I created while starring at the ti-sn65dsi86 driver in > >

Re: [PATCH 0/3] drm/bridge: ti-sn65dsi86: Some updates

2023-11-28 Thread Laurent Pinchart
Hello, On Fri, Nov 24, 2023 at 09:56:55AM +0100, Neil Armstrong wrote: > On 23/11/2023 18:54, Uwe Kleine-König wrote: > > Hello, > > > > this is a series I created while starring at the ti-sn65dsi86 driver in > > the context of my pwm-lifetime series. > > > > The first patch should be fine. The

Re: [PATCH 0/3] Revert panel fixes and original buggy patch

2023-11-28 Thread neil . armstrong
On 28/11/2023 10:34, Linus Walleij wrote: On Tue, Nov 28, 2023 at 9:30 AM Neil Armstrong wrote: You can apply them now, or tell me if you want me to apply them. Please apply them Neil (to drm-misc-fixes) order 2, 1, 3 for bisectability. Sure, doing it right now. Neil Yours, Linus

Re: [PATCH 0/3] Revert panel fixes and original buggy patch

2023-11-28 Thread Linus Walleij
On Tue, Nov 28, 2023 at 9:30 AM Neil Armstrong wrote: > You can apply them now, or tell me if you want me to apply them. Please apply them Neil (to drm-misc-fixes) order 2, 1, 3 for bisectability. Yours, Linus Walleij

Re: [PATCH 0/3] Revert panel fixes and original buggy patch

2023-11-28 Thread Neil Armstrong
Hi Linus, On 28/11/2023 00:36, Linus Walleij wrote: On Tue, Nov 28, 2023 at 12:25 AM Laurent Pinchart wrote: On Tue, Nov 28, 2023 at 12:10:18AM +0100, Linus Walleij wrote: This series reverts the attempts to fix the bug that went into v6.7-rc1 in commit 199cf07ebd2b "drm/bridge: panel: Add a

Re: [PATCH 0/3] Revert panel fixes and original buggy patch

2023-11-28 Thread Greg Kroah-Hartman
On Tue, Nov 28, 2023 at 01:52:44AM +0200, Laurent Pinchart wrote: > On Tue, Nov 28, 2023 at 12:36:15AM +0100, Linus Walleij wrote: > > On Tue, Nov 28, 2023 at 12:25 AM Laurent Pinchart wrote: > > > On Tue, Nov 28, 2023 at 12:10:18AM +0100, Linus Walleij wrote: > > > > This series reverts the

Re: [PATCH 0/3] Revert panel fixes and original buggy patch

2023-11-27 Thread Laurent Pinchart
On Tue, Nov 28, 2023 at 12:36:15AM +0100, Linus Walleij wrote: > On Tue, Nov 28, 2023 at 12:25 AM Laurent Pinchart wrote: > > On Tue, Nov 28, 2023 at 12:10:18AM +0100, Linus Walleij wrote: > > > This series reverts the attempts to fix the bug that went > > > into v6.7-rc1 in commit 199cf07ebd2b >

Re: [PATCH 0/3] Revert panel fixes and original buggy patch

2023-11-27 Thread Linus Walleij
On Tue, Nov 28, 2023 at 12:25 AM Laurent Pinchart wrote: > On Tue, Nov 28, 2023 at 12:10:18AM +0100, Linus Walleij wrote: > > This series reverts the attempts to fix the bug that went > > into v6.7-rc1 in commit 199cf07ebd2b > > "drm/bridge: panel: Add a device link between drm device and panel

Re: [PATCH 0/3] Revert panel fixes and original buggy patch

2023-11-27 Thread Laurent Pinchart
Hi Linus, On Tue, Nov 28, 2023 at 12:10:18AM +0100, Linus Walleij wrote: > This series reverts the attempts to fix the bug that went > into v6.7-rc1 in commit 199cf07ebd2b > "drm/bridge: panel: Add a device link between drm device and panel device" > and then it reverts that patch as well. > >

Re: [PATCH 0/3] drm/bridge: ti-sn65dsi86: Some updates

2023-11-24 Thread Neil Armstrong
Hi, On 23/11/2023 18:54, Uwe Kleine-König wrote: Hello, this is a series I created while starring at the ti-sn65dsi86 driver in the context of my pwm-lifetime series. The first patch should be fine. The last one has a few rough edges, but maybe you like the direction this is going to? The 2nd

Re: [PATCH 0/3] pwm: Drop useless member "pwm" from struct pwm_device

2023-11-13 Thread Uwe Kleine-König
Hello, On Fri, Jul 28, 2023 at 04:58:21PM +0200, Uwe Kleine-König wrote: > there are only two users of struct pwm_device::pwm in the tree; both use > it for some dev_dbg output. While this number allows to identify the > PWM, it's not trivial, for example the data currently available in >

Re: [PATCH 0/3] drm/ci: Add support for SM8250 Gitlab Runner

2023-11-09 Thread Helen Koike
On 07/11/2023 21:10, Jessica Zhang wrote: On 11/6/2023 9:35 AM, Jessica Zhang wrote: On 11/4/2023 6:02 AM, Helen Koike wrote: Hi Jessica, On 10/10/2023 19:25, Jessica Zhang wrote: Recently, we've registered a Gitlab runner for a Qualcomm RB5 device that will be hosted and maintained

Re: [PATCH 0/3] drm/ci: Add support for SM8250 Gitlab Runner

2023-11-07 Thread Jessica Zhang
On 11/6/2023 9:35 AM, Jessica Zhang wrote: On 11/4/2023 6:02 AM, Helen Koike wrote: Hi Jessica, On 10/10/2023 19:25, Jessica Zhang wrote: Recently, we've registered a Gitlab runner for a Qualcomm RB5 device that will be hosted and maintained in Qualcomm labs. This series will add a

Re: [PATCH 0/3] drm/ci: Add support for SM8250 Gitlab Runner

2023-11-06 Thread Jessica Zhang
On 11/4/2023 6:02 AM, Helen Koike wrote: Hi Jessica, On 10/10/2023 19:25, Jessica Zhang wrote: Recently, we've registered a Gitlab runner for a Qualcomm RB5 device that will be hosted and maintained in Qualcomm labs. This series will add a corresponding CI job for testing SM8250 devices

Re: [PATCH 0/3] drm/ci: Add support for SM8250 Gitlab Runner

2023-11-04 Thread Helen Koike
Hi Jessica, On 10/10/2023 19:25, Jessica Zhang wrote: Recently, we've registered a Gitlab runner for a Qualcomm RB5 device that will be hosted and maintained in Qualcomm labs. This series will add a corresponding CI job for testing SM8250 devices and add the skip/fails/flakes list. We were

Re: [PATCH 0/3] Make Allwinner A64's pll-mipi keep its rate when parent rate changes

2023-08-28 Thread Frank Oltmanns
On 2023-08-28 at 10:04:51 +0200, Maxime Ripard wrote: > On Fri, Aug 25, 2023 at 05:07:58PM +0200, Frank Oltmanns wrote: >> Thank you for your feedback, Maxime! >> >> On 2023-08-25 at 10:13:53 +0200, Maxime Ripard wrote: >> > [[PGP Signed Part:Undecided]] >> > Hi, >> > >> > On Fri, Aug 25, 2023

Re: [PATCH 0/3] Make Allwinner A64's pll-mipi keep its rate when parent rate changes

2023-08-28 Thread Frank Oltmanns
On 2023-08-28 at 10:25:01 +0200, Maxime Ripard wrote: > On Sat, Aug 26, 2023 at 11:12:16AM +0200, Frank Oltmanns wrote: >> >> On 2023-08-25 at 17:07:58 +0200, Frank Oltmanns wrote: >> > Thank you for your feedback, Maxime! >> > >> > On 2023-08-25 at 10:13:53 +0200, Maxime Ripard wrote: >> >>

Re: [PATCH 0/3] Make Allwinner A64's pll-mipi keep its rate when parent rate changes

2023-08-28 Thread Maxime Ripard
On Sat, Aug 26, 2023 at 11:12:16AM +0200, Frank Oltmanns wrote: > > On 2023-08-25 at 17:07:58 +0200, Frank Oltmanns wrote: > > Thank you for your feedback, Maxime! > > > > On 2023-08-25 at 10:13:53 +0200, Maxime Ripard wrote: > >> [[PGP Signed Part:Undecided]] > >> Hi, > >> > >> On Fri, Aug 25,

Re: [PATCH 0/3] Make Allwinner A64's pll-mipi keep its rate when parent rate changes

2023-08-28 Thread Maxime Ripard
On Fri, Aug 25, 2023 at 05:07:58PM +0200, Frank Oltmanns wrote: > Thank you for your feedback, Maxime! > > On 2023-08-25 at 10:13:53 +0200, Maxime Ripard wrote: > > [[PGP Signed Part:Undecided]] > > Hi, > > > > On Fri, Aug 25, 2023 at 07:36:36AM +0200, Frank Oltmanns wrote: > >> I would like to

Re: [PATCH 0/3] Make Allwinner A64's pll-mipi keep its rate when parent rate changes

2023-08-26 Thread Frank Oltmanns
On 2023-08-25 at 17:07:58 +0200, Frank Oltmanns wrote: > Thank you for your feedback, Maxime! > > On 2023-08-25 at 10:13:53 +0200, Maxime Ripard wrote: >> [[PGP Signed Part:Undecided]] >> Hi, >> >> On Fri, Aug 25, 2023 at 07:36:36AM +0200, Frank Oltmanns wrote: >>> I would like to make the

Re: [PATCH 0/3] Make Allwinner A64's pll-mipi keep its rate when parent rate changes

2023-08-25 Thread Frank Oltmanns
Thank you for your feedback, Maxime! On 2023-08-25 at 10:13:53 +0200, Maxime Ripard wrote: > [[PGP Signed Part:Undecided]] > Hi, > > On Fri, Aug 25, 2023 at 07:36:36AM +0200, Frank Oltmanns wrote: >> I would like to make the Allwinner A64's pll-mipi to keep its rate when >> its parent's

Re: [PATCH 0/3] Make Allwinner A64's pll-mipi keep its rate when parent rate changes

2023-08-25 Thread Maxime Ripard
Hi, On Fri, Aug 25, 2023 at 07:36:36AM +0200, Frank Oltmanns wrote: > I would like to make the Allwinner A64's pll-mipi to keep its rate when > its parent's (pll-video0) rate changes. Keeping pll-mipi's rate is > required, to let the A64 drive both an LCD and HDMI display at the same > time,

Re: [PATCH 0/3] pll-video0 notifier for v6.5+

2023-08-12 Thread Frank Oltmanns
On 2023-08-10 at 21:18:12 +0800, Chen-Yu Tsai wrote: > On Mon, Aug 7, 2023 at 5:36 PM Frank Oltmanns wrote: >> >> Hi Icenowy, >> >> it is my understanding that you are the original author of the following >> patches are in Ondřej's 6.4 branch [1] [2] [3] but not in his 6.5 >> branch. I assume

Re: [PATCH 0/3] pll-video0 notifier for v6.5+

2023-08-10 Thread Chen-Yu Tsai
On Mon, Aug 7, 2023 at 5:36 PM Frank Oltmanns wrote: > > Hi Icenowy, > > it is my understanding that you are the original author of the following > patches are in Ondřej's 6.4 branch [1] [2] [3] but not in his 6.5 > branch. I assume it is because of merge conflicts as the part about > setting the

Re: [PATCH 0/3] MediaTek DRM: Clean up CMDQ support and ifdefs

2023-07-21 Thread Alexandre Mergnat
On 19/07/2023 09:41, AngeloGioacchino Del Regno wrote: Il 23/06/23 14:49, Alexandre Mergnat ha scritto: On 23/06/2023 11:49, AngeloGioacchino Del Regno wrote: This series changes MediaTek CMDQ support to use the mtk-cmdq-helper functions, removing duplicated cmdq setup code in mtk-drm and

Re: [PATCH 0/3] MediaTek DRM: Clean up CMDQ support and ifdefs

2023-07-19 Thread AngeloGioacchino Del Regno
Il 23/06/23 14:49, Alexandre Mergnat ha scritto: On 23/06/2023 11:49, AngeloGioacchino Del Regno wrote: This series changes MediaTek CMDQ support to use the mtk-cmdq-helper functions, removing duplicated cmdq setup code in mtk-drm and also removing all instances of `#if

Re: [PATCH 0/3] MediaTek MIPI-DSI PHY: Cleanups

2023-07-11 Thread Vinod Koul
On Thu, 25 May 2023 13:52:55 +0200, AngeloGioacchino Del Regno wrote: > This series performs some cleanups to the MediaTek mipi-dsi PHY, used in > various MediaTek SoCs; in particular, it's migrating this driver to > register its clock as clk_hw provider instead and makes use of the devm >

Re: [PATCH 0/3] MediaTek DRM: Clean up CMDQ support and ifdefs

2023-06-23 Thread Alexandre Mergnat
On 23/06/2023 11:49, AngeloGioacchino Del Regno wrote: This series changes MediaTek CMDQ support to use the mtk-cmdq-helper functions, removing duplicated cmdq setup code in mtk-drm and also removing all instances of `#if IS_REACHABLE(CONFIG_MTK_CMDQ)` while keeping compatibility with both

Re: [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers

2023-06-19 Thread Thomas Zimmermann
Hi Am 16.06.23 um 19:00 schrieb Jeffrey Hugo: On 6/15/2023 3:31 AM, Thomas Zimmermann wrote: Set drm_gem_prime_handle_to_fd() and drm_gem_prime_fd_to_handle() for all DRM drivers. Even drivers that do not support PRIME import or export of dma-bufs can now import their own buffer objects. This

Re: [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers

2023-06-16 Thread Alex Deucher
Series looks good to me: Acked-by: Alex Deucher On Thu, Jun 15, 2023 at 5:42 AM Thomas Zimmermann wrote: > > Set drm_gem_prime_handle_to_fd() and drm_gem_prime_fd_to_handle() > for all DRM drivers. Even drivers that do not support PRIME import > or export of dma-bufs can now import their own

Re: [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers

2023-06-16 Thread Jeffrey Hugo
On 6/15/2023 3:31 AM, Thomas Zimmermann wrote: Set drm_gem_prime_handle_to_fd() and drm_gem_prime_fd_to_handle() for all DRM drivers. Even drivers that do not support PRIME import or export of dma-bufs can now import their own buffer objects. This is required by some userspace, such as

Re: [PATCH 0/3] Add support for databus widen mode

2023-06-16 Thread Dmitry Baryshkov
On 14/06/2023 04:57, Jessica Zhang wrote: DPU 5.x+ and DSI 6G 2.5.x+ support a databus-widen mode that allows for more compressed data to be transferred per pclk. This series adds support for enabling this feature for both DPU and DSI by doing the following: 1. Add a DPU_INTF_DATABUS_WIDEN

Re: [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers

2023-06-16 Thread Thomas Zimmermann
Hi Am 16.06.23 um 05:59 schrieb Zack Rusin: On Thu, 2023-06-15 at 11:31 +0200, Thomas Zimmermann wrote: Set drm_gem_prime_handle_to_fd() and drm_gem_prime_fd_to_handle() for all DRM drivers. Even drivers that do not support PRIME import or export of dma-bufs can now import their own buffer

Re: [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers

2023-06-15 Thread Zack Rusin
On Thu, 2023-06-15 at 11:31 +0200, Thomas Zimmermann wrote: > Set drm_gem_prime_handle_to_fd() and drm_gem_prime_fd_to_handle() > for all DRM drivers. Even drivers that do not support PRIME import > or export of dma-bufs can now import their own buffer objects. This > is required by some

Re: [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers

2023-06-15 Thread Thomas Zimmermann
Hi Am 15.06.23 um 16:50 schrieb Simon Ser: On Thursday, June 15th, 2023 at 11:31, Thomas Zimmermann wrote: Set drm_gem_prime_handle_to_fd() and drm_gem_prime_fd_to_handle() for all DRM drivers. Even drivers that do not support PRIME import or export of dma-bufs can now import their own

Re: [PATCH 0/3] drm: Allow PRIME 'self-import' for all drivers

2023-06-15 Thread Simon Ser
On Thursday, June 15th, 2023 at 11:31, Thomas Zimmermann wrote: > Set drm_gem_prime_handle_to_fd() and drm_gem_prime_fd_to_handle() > for all DRM drivers. Even drivers that do not support PRIME import > or export of dma-bufs can now import their own buffer objects. This > is required by some

Re: [PATCH 0/3] drm/msm/adreno: GPU support on SC8280XP

2023-06-14 Thread Bjorn Andersson
On Tue, 7 Feb 2023 19:40:49 -0800, Bjorn Andersson wrote: > This series introduces support for A690 in the DRM/MSM driver and > enables it for the two SC8280XP laptops. > > Bjorn Andersson (3): > drm/msm/adreno: Add Adreno A690 support > arm64: dts: qcom: sc8280xp: Add GPU related nodes >

Re: [PATCH 0/3] Add support for databus widen mode

2023-06-14 Thread Marijn Suijten
On 2023-06-13 18:57:10, Jessica Zhang wrote: > DPU 5.x+ and DSI 6G 2.5.x+ support a databus-widen mode that allows for > more compressed data to be transferred per pclk. > > This series adds support for enabling this feature for both DPU and DSI > by doing the following: > > 1. Add a

Re: [PATCH 0/3] fbdev/hitfb: Various fixes

2023-06-12 Thread Thomas Zimmermann
Helge, do you take these patches? Am 06.06.23 um 12:40 schrieb Thomas Zimmermann: Fix a number of minor warnings in the hitfb driver. I discovered them while working on bb47f218fd01 ("fbdev/hitfb: Cast I/O offset to address"). Thomas Zimmermann (3): fbdev/hitfb: Declare hitfb_blank() as

RE: [PATCH 0/3] fbdev/hitfb: Various fixes

2023-06-06 Thread Ruhl, Michael J
>-Original Message- >From: dri-devel On Behalf Of >Thomas Zimmermann >Sent: Tuesday, June 6, 2023 6:41 AM >To: del...@gmx.de; david.lai...@aculab.com >Cc: linux-fb...@vger.kernel.org; Thomas Zimmermann >; dri-devel@lists.freedesktop.org; linux- >s...@vger.kernel.org >Subject: [PATCH 0/3]

Re: [PATCH 0/3] STM32 warning cleanup

2023-05-17 Thread Marek Vasut
On 5/17/23 16:38, Raphael Gallais-Pou wrote: On 5/17/23 16:06, Marek Vasut wrote: On 5/17/23 15:22, Raphael Gallais-Pou wrote: This serie aims to reduce the number of device-tree warnings of following boards :    - STM32F429-DISCO    - STM32MP15* Those warnings were appearing either

Re: [PATCH 0/3] STM32 warning cleanup

2023-05-17 Thread Raphael Gallais-Pou
On 5/17/23 16:06, Marek Vasut wrote: > On 5/17/23 15:22, Raphael Gallais-Pou wrote: >> This serie aims to reduce the number of device-tree warnings of >> following boards : >> >>    - STM32F429-DISCO >>    - STM32MP15* >> >> Those warnings were appearing either during build or when checking >>

Re: [PATCH 0/3] STM32 warning cleanup

2023-05-17 Thread Marek Vasut
On 5/17/23 15:22, Raphael Gallais-Pou wrote: This serie aims to reduce the number of device-tree warnings of following boards : - STM32F429-DISCO - STM32MP15* Those warnings were appearing either during build or when checking dt-bindings and concern mostly LTDC and DSI IPs and were due

Re: [PATCH 0/3] drm/vkms: Minor Improvements

2023-05-16 Thread Arthur Grillo Queiroz Cabral
On 15/05/23 10:52, Maíra Canal wrote: > This series addresses some minor improvements to the writeback > functionality. The first patch intends to reduce the critical section > of a spinlock by removing assignments that don't need to be protected > by a lock. The second patch enables the

Re: [PATCH 0/3] fbdev: Set missing owner fields in fb_ops

2023-04-24 Thread Helge Deller
On 4/24/23 10:58, Thomas Zimmermann wrote: Set the owner field of various drivers' fb_ops instance. The setting is required by fbcon, which acquires a reference on the fbdev driver's module. Otherwise, users could attempt to unload the module while it's still in use. Thomas Zimmermann (3):

Re: [PATCH 0/3] Revert lima fdinfo patchset

2023-04-05 Thread Daniel Vetter
On Wed, Apr 05, 2023 at 08:50:06AM +0800, Qiang Yu wrote: > Applied to drm-misc-next, sorry for the trouble. No worries, I already complained to Lucas/etnaviv people that the sched revert should have been at least posted/discussed on dri-devel. Imo this isn't on you. -Daniel > > Regards, >

Re: [PATCH 0/3] Revert lima fdinfo patchset

2023-04-04 Thread Qiang Yu
Applied to drm-misc-next, sorry for the trouble. Regards, Qiang On Wed, Apr 5, 2023 at 3:28 AM Daniel Vetter wrote: > > On Tue, Apr 04, 2023 at 04:17:33PM +0100, Emil Velikov wrote: > > On Tue, 4 Apr 2023 at 08:13, wrote: > > > > > > From: Qiang Yu > > > > > > Upstream has reverted the

Re: [PATCH 0/3] Revert lima fdinfo patchset

2023-04-04 Thread Daniel Vetter
On Tue, Apr 04, 2023 at 04:17:33PM +0100, Emil Velikov wrote: > On Tue, 4 Apr 2023 at 08:13, wrote: > > > > From: Qiang Yu > > > > Upstream has reverted the dependant commit > > df622729ddbf ("drm/scheduler: track GPU active time per entity""), > > but this patchset has been pushed to

  1   2   3   4   5   6   7   8   >