From: Mark yao <mark.yao@rock-chips.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: "open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: Re: [GIT PULL] drm/rockchip: some fixes
Date: Thu, 23 Feb 2017 10:03:23 +0800 [thread overview]
Message-ID: <58AE42EB.6030604@rock-chips.com> (raw)
In-Reply-To: <CAOw6vbJFM4UcM2s-gW+iXfTPysYU3=qdTY8f=oASC5g_7CQd2A@mail.gmail.com>
On 2017年02月23日 00:09, Sean Paul wrote:
> On Tue, Feb 21, 2017 at 7:54 PM, Mark yao <mark.yao@rock-chips.com> wrote:
>> Hi Dave
>>
>> Some fixes, looks good to me.
>>
> Hi Mark,
> As we discussed, rockchip patches should now go through -misc. Since
> 4.10 is already released, I'll push these through over there.
>
> Sean
Hi Sean
Right, I had tried the -misc branch, but failed on some steps. let us
re-discussed how to use it.
and thanks for pushing these patches to -misc branch.
Best Regards.
>
>> Best regards.
>>
>> The following changes since commit 9ca70356a9260403c1bda40d942935e55d00c11c:
>>
>> Revert "drm: Resurrect atomic rmfb code, v3" (2017-02-17 12:39:04 +1000)
>>
>> are available in the git repository at:
>>
>> https://github.com/markyzq/kernel-drm-rockchip.git
>> drm-rockchip-next-2017-02-22
>>
>> for you to fetch changes up to 3690629b844b961fc9dda98b0ffc16a6010a7f21:
>>
>> drm/rockchip: vop: verify pixelclock for hdmi and displayport (2017-02-22
>> 08:44:22 +0800)
>>
>> ----------------------------------------------------------------
>> Arnd Bergmann (1):
>> drm/rockchip: add extcon dependency for DP
>>
>> Christophe Jaillet (1):
>> drm/rockchip: cdn-dp: Fix error handling
>>
>> Mark Yao (3):
>> drm/rockchip: vop: no need wait vblank on crtc enable
>> drm/rockchip: vop: verify display mode with vop max_output
>> drm/rockchip: vop: verify pixelclock for hdmi and displayport
>>
>> drivers/gpu/drm/rockchip/Kconfig | 1 +
>> drivers/gpu/drm/rockchip/cdn-dp-core.c | 4 +++-
>> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 56
>> ++++++++++++++++++--------------------------------------
>> drivers/gpu/drm/rockchip/rockchip_drm_vop.h | 7 +++++++
>> drivers/gpu/drm/rockchip/rockchip_vop_reg.c | 13 +++++++++++++
>> 5 files changed, 42 insertions(+), 39 deletions(-)
>>
>> --
>> Ｍark Yao
>>
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
>
>
--
Ｍark Yao
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-23 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 0:54 [GIT PULL] drm/rockchip: some fixes Mark yao
2017-02-22 16:09 ` Sean Paul
2017-02-23 2:03 ` Mark yao [this message]
2017-02-23 18:01 ` Sean Paul
2017-02-24 0:42 ` Mark yao
-- strict thread matches above, loose matches on Subject: below --
2016-09-10 2:57 Mark yao
2016-09-13 0:20 ` Dave Airlie
2016-09-17 5:41 ` Mark yao
2016-07-19 2:32 Mark yao
2016-05-03 6:21 Mark yao
2016-03-28 6:54 [GIT PULL]: " Mark yao
2015-07-13 6:22 [GIT PULL] " 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=58AE42EB.6030604@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=seanpaul@chromium.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.