From: Heiko Stuebner <heiko@sntech.de>
To: Mark Yao <mark.yao@rock-chips.com>
Cc: David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers
Date: Thu, 27 Jul 2017 00:50:51 +0200 [thread overview]
Message-ID: <1646231.OqT85nW1UI@phil> (raw)
In-Reply-To: <1501049960-6006-1-git-send-email-mark.yao@rock-chips.com>
Am Mittwoch, 26. Juli 2017, 14:19:19 CEST schrieb Mark Yao:
> In the hardware design process, the design of line flags
> register is associated with the interrupt register,
> placing the line flags in the interrupt definition is
> more reasonable, and it would make multi-vop define easilier.
>
> Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
> Reviewed-by: Sean Paul <seanpaul@chromium.org>
on rk3036 and rk3288
Tested-by: Heiko Stuebner <heiko@sntech.de>
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Mark Yao <mark.yao@rock-chips.com>
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers
Date: Thu, 27 Jul 2017 00:50:51 +0200 [thread overview]
Message-ID: <1646231.OqT85nW1UI@phil> (raw)
In-Reply-To: <1501049960-6006-1-git-send-email-mark.yao@rock-chips.com>
Am Mittwoch, 26. Juli 2017, 14:19:19 CEST schrieb Mark Yao:
> In the hardware design process, the design of line flags
> register is associated with the interrupt register,
> placing the line flags in the interrupt definition is
> more reasonable, and it would make multi-vop define easilier.
>
> Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
> Reviewed-by: Sean Paul <seanpaul@chromium.org>
on rk3036 and rk3288
Tested-by: Heiko Stuebner <heiko@sntech.de>
Heiko
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stuebner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v6 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers
Date: Thu, 27 Jul 2017 00:50:51 +0200 [thread overview]
Message-ID: <1646231.OqT85nW1UI@phil> (raw)
In-Reply-To: <1501049960-6006-1-git-send-email-mark.yao@rock-chips.com>
Am Mittwoch, 26. Juli 2017, 14:19:19 CEST schrieb Mark Yao:
> In the hardware design process, the design of line flags
> register is associated with the interrupt register,
> placing the line flags in the interrupt definition is
> more reasonable, and it would make multi-vop define easilier.
>
> Signed-off-by: Mark Yao <mark.yao@rock-chips.com>
> Reviewed-by: Sean Paul <seanpaul@chromium.org>
on rk3036 and rk3288
Tested-by: Heiko Stuebner <heiko@sntech.de>
Heiko
next prev parent reply other threads:[~2017-07-26 22:50 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 6:18 [PATCH v6 0/7] drm/rockchip: add all full framework vop support Mark Yao
2017-07-26 6:18 ` Mark Yao
2017-07-26 6:18 ` Mark Yao
2017-07-26 6:19 ` [PATCH v6 1/7] drm/rockchip: vop: initialize registers directly Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 22:44 ` Heiko Stuebner
2017-07-26 22:44 ` Heiko Stuebner
2017-07-26 22:44 ` Heiko Stuebner
2017-07-27 8:31 ` [v6,1/7] " jeffy
2017-07-27 8:31 ` jeffy
2017-07-27 8:31 ` jeffy
2017-07-26 6:19 ` [PATCH v6 2/7] drm/rockchip: vop: move write_relaxed flags to vop register Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 22:46 ` Heiko Stuebner
2017-07-26 22:46 ` Heiko Stuebner
2017-07-26 22:46 ` Heiko Stuebner
2017-07-27 8:43 ` [v6,2/7] " jeffy
2017-07-27 8:43 ` [v6, 2/7] " jeffy
2017-07-27 8:43 ` jeffy
2017-07-26 6:19 ` [PATCH v6 3/7] drm/rockchip: vop: move line_flag_num to interrupt registers Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 22:50 ` Heiko Stuebner [this message]
2017-07-26 22:50 ` Heiko Stuebner
2017-07-26 22:50 ` Heiko Stuebner
2017-07-26 6:19 ` [PATCH v6 4/7] drm/rockchip: vop: group vop registers Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-27 8:49 ` [v6,4/7] " jeffy
2017-07-27 8:49 ` jeffy
2017-07-27 8:49 ` jeffy
2017-07-27 9:51 ` [PATCH v6 4/7] " Heiko Stübner
2017-07-27 9:51 ` Heiko Stübner
2017-07-27 9:51 ` Heiko Stübner
2017-07-27 10:10 ` Heiko Stübner
2017-07-27 10:10 ` Heiko Stübner
2017-07-27 10:10 ` Heiko Stübner
2017-07-28 1:02 ` Mark yao
2017-07-28 1:02 ` Mark yao
2017-07-28 1:02 ` Mark yao
2017-07-28 2:45 ` Mark yao
2017-07-28 2:45 ` Mark yao
2017-07-28 6:06 ` [PATCH v6.1 " Mark Yao
2017-07-28 6:06 ` Mark Yao
2017-07-28 6:06 ` Mark Yao
2017-07-28 9:21 ` Heiko Stuebner
2017-07-28 9:21 ` Heiko Stuebner
2017-07-28 9:21 ` Heiko Stuebner
2017-07-26 6:19 ` [PATCH v6 5/7] drm/rockchip: vop: add a series of vop support Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-27 8:59 ` [v6,5/7] " jeffy
2017-07-27 8:59 ` jeffy
2017-07-27 8:59 ` jeffy
2017-07-28 12:48 ` [PATCH v6 5/7] " Heiko Stuebner
2017-07-28 12:48 ` Heiko Stuebner
2017-07-28 12:48 ` Heiko Stuebner
2017-07-26 6:19 ` [PATCH v6 6/7] dt-bindings: display: rockchip: fill Documents for vop series Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-28 9:25 ` Heiko Stuebner
2017-07-28 9:25 ` Heiko Stuebner
2017-07-28 9:25 ` Heiko Stuebner
2017-07-26 6:19 ` [PATCH v6 7/7] drm/rockchip: vop: rk3328: fix overlay abnormal Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-26 6:19 ` Mark Yao
2017-07-27 8:42 ` [v6,7/7] " jeffy
2017-07-27 8:42 ` jeffy
2017-07-27 8:42 ` jeffy
2017-07-28 13:06 ` [PATCH v6 7/7] " Heiko Stuebner
2017-07-28 13:06 ` Heiko Stuebner
2017-07-28 13:06 ` Heiko Stuebner
2017-07-31 1:02 ` [PATCH v6 0/7] drm/rockchip: add all full framework vop support Mark yao
2017-07-31 1:02 ` Mark yao
2017-07-31 1:02 ` 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=1646231.OqT85nW1UI@phil \
--to=heiko@sntech.de \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.yao@rock-chips.com \
/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.