From: John Keeping <john@metanate.com>
To: Sean Paul <seanpaul@chromium.org>
Cc: Chris Zhong <zyw@rock-chips.com>,
Doug Anderson <dianders@chromium.org>,
Tomasz Figa <tfiga@chromium.org>,
Heiko Stuebner <heiko@sntech.de>, Mark Yao <yzq@rock-chips.com>,
Mark Rutland <mark.rutland@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Kumar Gala <galak@codeaurora.org>,
Pawel Moll <pawel.moll@arm.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-rockchip@lists.infradead.org,
Linux ARM Kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [RESEND PATCH v7 0/7] Rockchip dw-mipi-dsi driver
Date: Wed, 22 Feb 2017 18:55:43 +0000 [thread overview]
Message-ID: <20170222185543.71e20187.john@metanate.com> (raw)
In-Reply-To: <CAOw6vbJoS2P5m31+bgWw3Sghz=EVGj0fpLgCFnbVEhzRujNCLw@mail.gmail.com>
On Wed, 22 Feb 2017 10:57:05 -0500, Sean Paul wrote:
> On Wed, Feb 22, 2017 at 8:43 AM, John Keeping <john@metanate.com> wrote:
> > On Tue, 21 Feb 2017 10:39:18 -0500, Sean Paul wrote:
> >
> >> On Mon, Feb 20, 2017 at 04:02:16PM +0800, Chris Zhong wrote:
> >> > Hi all
> >> >
> >> > [Resend this v7 version series, since there are 5 mails have gone missing, last
> >> > week]
> >> >
> >> > This version does not change the existing v6 patches, just to add the
> >> > "bandwidth fix" patch back, since we really need it.
> >> >
> >> > This patch serial is for RK3399 MIPI DSI. The MIPI DSI controller of
> >> > RK3399 is almost the same as RK3288, except a little bit of difference
> >> > in phy clock controlling and port id selection register. These patches
> >> > add RK3399 support and the power domain support.
> >> >
> >> > And these patches base on John Keeping's v3 patches[0], it fixes many bugs,
> >> > they have been tested on rk3288 evb board.
> >>
> >> Do we have an ETA on when John is planning on respinning his patchset based on
> >> review feedback?
> >
> > I have all of the changes queued but I was hoping to find some time to
> > test the latest version before sending it out; unfortunately everything
> > else is more important at the moment. If you're happy with the caveat
> > that the latest changes are build tested only I can probably send it
> > out this afternoon.
>
> I suppose my answer depends on when the tested version will be
> available, or perhaps Chris can test the new set for you? I don't have
> any rockchip devices with mipi, so i'm not much help.
None of the changes scare me that much, so I don't expect testing to
throw up any problems but I don't like throwing out patches without at
least a basic test run.
I might have time to test on Friday, but I expect Chris has more time to
devote to this than I do, so maybe it's better if I send the patches out
tomorrow.
John
next prev parent reply other threads:[~2017-02-22 18:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 8:02 [RESEND PATCH v7 0/7] Rockchip dw-mipi-dsi driver Chris Zhong
2017-02-20 8:02 ` [RESEND PATCH v7 1/7] dt-bindings: add rk3399 support for dw-mipi-rockchip Chris Zhong
2017-02-20 8:02 ` [RESEND PATCH v7 2/7] drm/rockchip/dsi: dw-mipi: support RK3399 mipi dsi Chris Zhong
2017-02-20 8:02 ` [RESEND PATCH v7 3/7] drm/rockchip/dsi: dw-mipi: correct the coding style Chris Zhong
2017-02-20 8:02 ` [RESEND PATCH v7 4/7] drm/rockchip/dsi: remove mode_valid function Chris Zhong
2017-02-20 8:02 ` [RESEND PATCH v7 5/7] dt-bindings: add power domain node for dw-mipi-rockchip Chris Zhong
2017-02-20 8:02 ` [RESEND PATCH v7 6/7] drm/rockchip/dsi: fix insufficient bandwidth of some panel Chris Zhong
2017-02-21 15:40 ` Sean Paul
2017-02-20 8:02 ` [RESEND PATCH v7 7/7] drm/rockchip/dsi: add dw-mipi power domain support Chris Zhong
2017-02-21 15:39 ` [RESEND PATCH v7 0/7] Rockchip dw-mipi-dsi driver Sean Paul
2017-02-22 1:44 ` Chris Zhong
2017-02-22 13:43 ` John Keeping
2017-02-22 15:57 ` Sean Paul
2017-02-22 18:55 ` John Keeping [this message]
2017-02-22 22:10 ` Sean Paul
2017-02-23 0:25 ` Chris Zhong
2017-03-01 20:02 ` Sean Paul
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=20170222185543.71e20187.john@metanate.com \
--to=john@metanate.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=galak@codeaurora.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=seanpaul@chromium.org \
--cc=tfiga@chromium.org \
--cc=yzq@rock-chips.com \
--cc=zyw@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox