From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752914AbcFLBCW (ORCPT ); Sat, 11 Jun 2016 21:02:22 -0400 Received: from regular1.263xmail.com ([211.150.99.141]:39774 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751849AbcFLBCU (ORCPT ); Sat, 11 Jun 2016 21:02:20 -0400 X-263anti-spam: KSV:0; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 4 X-ADDR-CHECKED: 0 X-RL-SENDER: frank.wang@rock-chips.com X-FST-TO: frank.wang@rock-chips.com X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: frank.wang@rock-chips.com X-UNIQUE-TAG: <09a2dc9ccfcbbc2b1d3ad5718a00349f> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [PATCH v4 0/2] Add a new Rockchip usb2 phy driver To: =?UTF-8?Q?Heiko_St=c3=bcbner?= References: <1465290954-15852-1-git-send-email-frank.wang@rock-chips.com> <7024078.xQbt7GEvIn@diego> 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 From: Frank Wang Message-ID: Date: Sun, 12 Jun 2016 09:01:58 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <7024078.xQbt7GEvIn@diego> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > >