From: Frank Wang <frank.wang@rock-chips.com>
To: "Heiko Stübner" <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,
frank.wang@rock-chips.com
Subject: Re: [PATCH v4 0/2] Add a new Rockchip usb2 phy driver
Date: Sun, 12 Jun 2016 09:01:58 +0800 [thread overview]
Message-ID: <e04a4ba5-ee22-5d18-1341-ce8c7780eb15@rock-chips.com> (raw)
In-Reply-To: <7024078.xQbt7GEvIn@diego>
Hi Heiko,
On 2016/6/8 22:33, Heiko Stübner wrote:
> Hi Frank,
>
> Am Dienstag, 7. Juni 2016, 17:15:52 schrieb Frank Wang:
>> The newer SoCs (rk3366, rk3399) of Rock-chip 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.
>>
>> These series patches add phy-rockchip-inno-usb2.c and the corresponding
>> documentation.
> please see the replies on the v3 thread (regarding handling of multiple phy
> blocks) .
>
OK, I just got back from Dragon Boat Festival (one of the great
traditions of my nation's festival), I will correct it and send out
later today.
BR.
Frank
>> Changes in v4:
>> - Used 'phy-supply' instead of 'vbus_*-supply'.
>>
>> Changes in v3:
>> - Supplemented some hardware-description into the devicetree bindings.
>> - Resolved the mapping defect between fixed value in driver and the
>> property in devicetree.
>> - Code cleanup.
>>
>> Changes in v2:
>> - Specified more hardware-description into the devicetree bindings.
>> - Optimized some process of driver.
>>
>> Frank Wang (2):
>> Documentation: bindings: add DT documentation for Rockchip USB2PHY
>> phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy
>>
>> .../bindings/phy/phy-rockchip-inno-usb2.txt | 62 ++
>> drivers/phy/Kconfig | 7 +
>> drivers/phy/Makefile | 1 +
>> drivers/phy/phy-rockchip-inno-usb2.c | 614
>> ++++++++++++++++++++ 4 files changed, 684 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/phy/phy-rockchip-inno-usb2.txt create
>> mode 100644 drivers/phy/phy-rockchip-inno-usb2.c
>
>
>
prev parent reply other threads:[~2016-06-12 1:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 9:15 [PATCH v4 0/2] Add a new Rockchip usb2 phy driver Frank Wang
2016-06-07 9:15 ` [PATCH v4 1/2] Documentation: bindings: add DT documentation for Rockchip USB2PHY Frank Wang
2016-06-08 20:04 ` Rob Herring
2016-06-12 1:18 ` Frank Wang
2016-06-07 9:15 ` [PATCH v4 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy Frank Wang
2016-06-08 14:33 ` [PATCH v4 0/2] Add a new Rockchip usb2 phy driver Heiko Stübner
2016-06-12 1:01 ` Frank Wang [this message]
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=e04a4ba5-ee22-5d18-1341-ce8c7780eb15@rock-chips.com \
--to=frank.wang@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;
as well as URLs for NNTP newsgroup(s).