From: mark.yao@rock-chips.com (Mark yao)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] drm/rockchip: fixes
Date: Wed, 02 Dec 2015 10:55:29 +0800 [thread overview]
Message-ID: <565E5DA1.1070006@rock-chips.com> (raw)
Hi Dave
Here are some needed fixes for rockchip drm.
There are three patches I had sent you before, I noticed that you don't
land them, so I rebase to drm-fixes and send you again:
drm/rockchip: unset pgoff when mmap'ing gems
drm rockchip can't work without this patch, when test with
modetest, always get following error:
trying to open device 'rockchip'...success.
failed to map buffer: Unknown error -6
drm/rockchip: vop: Correct enabled clocks during setup
if build drm rockchip as module, we need this patch, system
would hang if aclk is disabled.
drm/rockchip: vop: fix window origin calculation
this patch fix window display, display shift by one pixel
on screen.
Other new two fixes:
drm/rockchip: Fix module autoload for OF platform driver
module autoloading won't work without this patch.
drm/rockchip: Use CRTC vblank event interface
Passing -1 as the pipe triggers a WARN_ON at every pageflip
on multi-screen, that make multi-screen unusable.
I'd like you can land them.
Thanks.
The following changes since commit
b50a1705b598fa4074a5e5e4f20ca46485d1cd0e:
Merge tag 'drm-intel-fixes-2015-11-30' of
git://anongit.freedesktop.org/drm-intel into drm-fixes (2015-12-01
08:00:33 +1000)
are available in the git repository at:
https://github.com/markyzq/kernel-drm-rockchip.git
drm-fixes-rockchip-2015-12-02
for you to fetch changes up to c9fbb7f7b5c56752373e4f425d5157815426e233:
drm/rockchip: Use CRTC vblank event interface (2015-12-02 10:22:21
+0800)
----------------------------------------------------------------
Daniel Stone (1):
drm/rockchip: Use CRTC vblank event interface
Dominik Behr (1):
drm/rockchip: vop: fix window origin calculation
Heiko Stuebner (1):
drm/rockchip: unset pgoff when mmap'ing gems
Luis de Bethencourt (1):
drm/rockchip: Fix module autoload for OF platform driver
Sjoerd Simons (1):
drm/rockchip: vop: Correct enabled clocks during setup
drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 1 +
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 43
+++++++++++----------------
2 files changed, 19 insertions(+), 25 deletions(-)
--
?ark Yao
WARNING: multiple messages have this Message-ID (diff)
From: Mark yao <mark.yao@rock-chips.com>
To: airlied@linux.ie
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: [GIT PULL] drm/rockchip: fixes
Date: Wed, 02 Dec 2015 10:55:29 +0800 [thread overview]
Message-ID: <565E5DA1.1070006@rock-chips.com> (raw)
Hi Dave
Here are some needed fixes for rockchip drm.
There are three patches I had sent you before, I noticed that you don't
land them, so I rebase to drm-fixes and send you again:
drm/rockchip: unset pgoff when mmap'ing gems
drm rockchip can't work without this patch, when test with
modetest, always get following error:
trying to open device 'rockchip'...success.
failed to map buffer: Unknown error -6
drm/rockchip: vop: Correct enabled clocks during setup
if build drm rockchip as module, we need this patch, system
would hang if aclk is disabled.
drm/rockchip: vop: fix window origin calculation
this patch fix window display, display shift by one pixel
on screen.
Other new two fixes:
drm/rockchip: Fix module autoload for OF platform driver
module autoloading won't work without this patch.
drm/rockchip: Use CRTC vblank event interface
Passing -1 as the pipe triggers a WARN_ON at every pageflip
on multi-screen, that make multi-screen unusable.
I'd like you can land them.
Thanks.
The following changes since commit
b50a1705b598fa4074a5e5e4f20ca46485d1cd0e:
Merge tag 'drm-intel-fixes-2015-11-30' of
git://anongit.freedesktop.org/drm-intel into drm-fixes (2015-12-01
08:00:33 +1000)
are available in the git repository at:
https://github.com/markyzq/kernel-drm-rockchip.git
drm-fixes-rockchip-2015-12-02
for you to fetch changes up to c9fbb7f7b5c56752373e4f425d5157815426e233:
drm/rockchip: Use CRTC vblank event interface (2015-12-02 10:22:21
+0800)
----------------------------------------------------------------
Daniel Stone (1):
drm/rockchip: Use CRTC vblank event interface
Dominik Behr (1):
drm/rockchip: vop: fix window origin calculation
Heiko Stuebner (1):
drm/rockchip: unset pgoff when mmap'ing gems
Luis de Bethencourt (1):
drm/rockchip: Fix module autoload for OF platform driver
Sjoerd Simons (1):
drm/rockchip: vop: Correct enabled clocks during setup
drivers/gpu/drm/rockchip/rockchip_drm_gem.c | 1 +
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 43
+++++++++++----------------
2 files changed, 19 insertions(+), 25 deletions(-)
--
Mark Yao
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-12-02 2:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 2:55 Mark yao [this message]
2015-12-02 2:55 ` [GIT PULL] drm/rockchip: fixes Mark yao
-- strict thread matches above, loose matches on Subject: below --
2016-01-22 1:37 Mark yao
2016-01-22 1:37 ` Mark yao
2015-11-11 0:56 Mark yao
2015-11-11 0:56 ` Mark yao
2015-11-21 21:50 ` Heiko Stuebner
2015-11-21 21:50 ` Heiko Stuebner
2015-04-03 6:49 Mark yao
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=565E5DA1.1070006@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.