public inbox for linux-rockchip@lists.infradead.org
 help / color / mirror / Atom feed
From: Frank Wang <frank.wang@rock-chips.com>
To: Heiko Stuebner <heiko@sntech.de>
Cc: dianders@chromium.org, linux@roeck-us.net, groeck@chromium.org,
	jwerner@chromium.org, kishon@ti.com, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-rockchip@lists.infradead.org,
	xzy.xu@rock-chips.com, kever.yang@rock-chips.com,
	huangtao@rock-chips.com, william.wu@rock-chips.com,
	daniel.meng@rock-chips.com, frank.wang@rock-chips.com
Subject: Re: [PATCH v7 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy
Date: Mon, 18 Jul 2016 18:02:28 +0800	[thread overview]
Message-ID: <901bc2d0-34ac-4c18-8fd2-491b10a43579@rock-chips.com> (raw)
In-Reply-To: <3635389.HlLpm27c0G@phil>

Hi Heiko,

On 2016/6/25 3:58, Heiko Stuebner wrote:
> Am Dienstag, 21. Juni 2016, 18:30:05 schrieb Frank Wang:
>> The newer SoCs (rk3366, rk3399) take a different usb-phy IP block
>> than rk3288 and before, and most of phy-related registers are also
>> different from the past, so a new phy driver is required necessarily.
>>
>> Signed-off-by: Frank Wang <frank.wang@rock-chips.com>
>> Suggested-by: Heiko Stuebner <heiko@sntech.de>
>> Suggested-by: Guenter Roeck <linux@roeck-us.net>
>> Suggested-by: Doug Anderson <dianders@chromium.org>
> still looks nice, so still
> Reviewed-by: Heiko Stuebner <heiko@sntech.de>
>
>

Currently, we have already prepared compatible for rk3399, however, I 
found these series of patch had not merged in, so shall I reopen it or 
commit a new one?

BR.
Frank

  reply	other threads:[~2016-07-18 10:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-21 10:30 [PATCH v7 0/2] Add a new Rockchip usb2 phy driver Frank Wang
     [not found] ` <1466505005-86122-1-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-21 10:30   ` [PATCH v7 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY Frank Wang
2016-06-21 10:30   ` [PATCH v7 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy Frank Wang
     [not found]     ` <1466505005-86122-3-git-send-email-frank.wang-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-06-24 19:58       ` Heiko Stuebner
2016-07-18 10:02         ` Frank Wang [this message]
     [not found]           ` <901bc2d0-34ac-4c18-8fd2-491b10a43579-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-07-18 11:28             ` Heiko Stübner
2016-06-24 20:44     ` Guenter Roeck

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=901bc2d0-34ac-4c18-8fd2-491b10a43579@rock-chips.com \
    --to=frank.wang@rock-chips.com \
    --cc=daniel.meng@rock-chips.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=galak@codeaurora.org \
    --cc=groeck@chromium.org \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=jwerner@chromium.org \
    --cc=kever.yang@rock-chips.com \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=william.wu@rock-chips.com \
    --cc=xzy.xu@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