From: Val Packett <val@packett.cool>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/rockchip: vop: clear DMA stop bit on flush on RK3066
Date: Sun, 19 May 2024 05:38:24 -0300 [thread overview]
Message-ID: <0C5QDS.UDESKUXHKPET1@packett.cool> (raw)
In-Reply-To: <2024051936-cosmetics-seismic-9fea@gregkh>
On Sun, May 19 2024 at 09:59:47 +02:00:00, Greg KH
<gregkh@linuxfoundation.org> wrote:
> On Sun, May 19, 2024 at 04:31:31AM -0300, Val Packett wrote:
>> On the RK3066, there is a bit that must be cleared on flush,
>> otherwise
>> we do not get display output (at least for RGB).
>
> What commit id does this fix?
I guess: f4a6de855e "drm: rockchip: vop: add rk3066 vop definitions" ?
But similar changes like:
742203cd "drm: rockchip: add missing registers for RK3066"
8d544233 "drm/rockchip: vop: Add directly output rgb feature for px30"
did not have any "Fixes" reference.
~val
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
WARNING: multiple messages have this Message-ID (diff)
From: Val Packett <val@packett.cool>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/rockchip: vop: clear DMA stop bit on flush on RK3066
Date: Sun, 19 May 2024 05:38:24 -0300 [thread overview]
Message-ID: <0C5QDS.UDESKUXHKPET1@packett.cool> (raw)
In-Reply-To: <2024051936-cosmetics-seismic-9fea@gregkh>
On Sun, May 19 2024 at 09:59:47 +02:00:00, Greg KH
<gregkh@linuxfoundation.org> wrote:
> On Sun, May 19, 2024 at 04:31:31AM -0300, Val Packett wrote:
>> On the RK3066, there is a bit that must be cleared on flush,
>> otherwise
>> we do not get display output (at least for RGB).
>
> What commit id does this fix?
I guess: f4a6de855e "drm: rockchip: vop: add rk3066 vop definitions" ?
But similar changes like:
742203cd "drm: rockchip: add missing registers for RK3066"
8d544233 "drm/rockchip: vop: Add directly output rgb feature for px30"
did not have any "Fixes" reference.
~val
WARNING: multiple messages have this Message-ID (diff)
From: Val Packett <val@packett.cool>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, "Sandy Huang" <hjc@rock-chips.com>,
"Heiko Stübner" <heiko@sntech.de>,
"Andy Yan" <andy.yan@rock-chips.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"David Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/rockchip: vop: clear DMA stop bit on flush on RK3066
Date: Sun, 19 May 2024 05:38:24 -0300 [thread overview]
Message-ID: <0C5QDS.UDESKUXHKPET1@packett.cool> (raw)
In-Reply-To: <2024051936-cosmetics-seismic-9fea@gregkh>
On Sun, May 19 2024 at 09:59:47 +02:00:00, Greg KH
<gregkh@linuxfoundation.org> wrote:
> On Sun, May 19, 2024 at 04:31:31AM -0300, Val Packett wrote:
>> On the RK3066, there is a bit that must be cleared on flush,
>> otherwise
>> we do not get display output (at least for RGB).
>
> What commit id does this fix?
I guess: f4a6de855e "drm: rockchip: vop: add rk3066 vop definitions" ?
But similar changes like:
742203cd "drm: rockchip: add missing registers for RK3066"
8d544233 "drm/rockchip: vop: Add directly output rgb feature for px30"
did not have any "Fixes" reference.
~val
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-19 8:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 7:31 [PATCH 1/2] drm/rockchip: vop: clear DMA stop bit on flush on RK3066 Val Packett
2024-05-19 7:31 ` Val Packett
2024-05-19 7:31 ` Val Packett
2024-05-19 7:31 ` [PATCH 2/2] drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB " Val Packett
2024-05-19 7:31 ` Val Packett
2024-05-19 7:31 ` Val Packett
2024-05-19 7:59 ` Greg KH
2024-05-19 7:59 ` Greg KH
2024-05-19 7:59 ` Greg KH
2024-05-19 7:59 ` [PATCH 1/2] drm/rockchip: vop: clear DMA stop bit on flush " Greg KH
2024-05-19 7:59 ` Greg KH
2024-05-19 7:59 ` Greg KH
2024-05-19 8:38 ` Val Packett [this message]
2024-05-19 8:38 ` Val Packett
2024-05-19 8:38 ` Val Packett
2024-05-19 8:54 ` Greg KH
2024-05-19 8:54 ` Greg KH
2024-05-19 8:54 ` Greg KH
2024-05-27 7:16 ` [PATCH v2 1/2] drm/rockchip: vop: clear DMA stop bit upon vblank " Val Packett
2024-05-27 7:16 ` Val Packett
2024-05-27 7:16 ` Val Packett
2024-05-27 7:16 ` [PATCH v2 2/2] drm/rockchip: vop: enable VOP_FEATURE_INTERNAL_RGB " Val Packett
2024-05-27 7:16 ` Val Packett
2024-05-27 7:16 ` Val Packett
2024-05-27 20:43 ` [PATCH v2 1/2] drm/rockchip: vop: clear DMA stop bit upon vblank " Heiko Stübner
2024-05-27 20:43 ` Heiko Stübner
2024-05-27 20:43 ` Heiko Stübner
2024-05-27 22:13 ` Val Packett
2024-05-27 22:13 ` Val Packett
2024-05-27 22:13 ` Val Packett
2024-05-27 22:51 ` Heiko Stübner
2024-05-27 22:51 ` Heiko Stübner
2024-05-27 22:51 ` Heiko Stübner
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=0C5QDS.UDESKUXHKPET1@packett.cool \
--to=val@packett.cool \
--cc=airlied@gmail.com \
--cc=andy.yan@rock-chips.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=heiko@sntech.de \
--cc=hjc@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.