From: Faiz Abbas <faiz.abbas@arm.com>
To: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Cc: liviu.dudau@arm.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
daniel@ffwll.ch, Faiz Abbas <faiz.abbas@arm.com>
Subject: [PATCH 0/3] Fixes for the komeda driver
Date: Mon, 19 Feb 2024 15:39:12 +0530 [thread overview]
Message-ID: <20240219100915.192475-1-faiz.abbas@arm.com> (raw)
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 does not print verbose
pipeline information unless the entire pipeline is actually up.
Patch 3 adds a 40 bit DMA mask for each pipeline.
Amjad Ouled-Ameur (1):
drm/arm/komeda: update DMA mask to 40 bits
Faiz Abbas (2):
drm/arm/komeda: Fix komeda probe failing if there are no links in the
secondary pipeline
drm/arm/komeda: Move pipeline prints to after the entire pipeline has
been enabled
.../gpu/drm/arm/display/komeda/komeda_crtc.c | 45 ++++++++++++++-----
.../gpu/drm/arm/display/komeda/komeda_drv.c | 4 ++
.../gpu/drm/arm/display/komeda/komeda_kms.h | 1 +
.../drm/arm/display/komeda/komeda_pipeline.c | 4 +-
4 files changed, 41 insertions(+), 13 deletions(-)
--
2.25.1
next reply other threads:[~2024-02-19 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 10:09 Faiz Abbas [this message]
2024-02-19 10:09 ` [PATCH 1/3] drm/arm/komeda: Fix komeda probe failing if there are no links in the secondary pipeline Faiz Abbas
2024-03-06 13:43 ` Liviu Dudau
2024-03-11 8:32 ` Faiz Abbas
2024-02-19 10:09 ` [PATCH 2/3] drm/arm/komeda: Move pipeline prints to after the entire pipeline has been enabled Faiz Abbas
2024-02-19 10:09 ` [PATCH 3/3] drm/arm/komeda: update DMA mask to 40 bits Faiz Abbas
2024-02-27 10:52 ` [PATCH 0/3] Fixes for the komeda driver Liviu Dudau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240219100915.192475-1-faiz.abbas@arm.com \
--to=faiz.abbas@arm.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®