linux-kernel - Re: [PATCH v7 2/2] phy: rockchip-inno-usb2: add a new driver for Rockchip usb2phy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <901bc2d0-34ac-4c18-8fd2-491b10a43579@rock-chips.com>
Date:	Mon, 18 Jul 2016 18:02:28 +0800
From:	Frank Wang <frank.wang@...k-chips.com>
To:	Heiko Stuebner <heiko@...ech.de>
Cc:	dianders@...omium.org, linux@...ck-us.net, groeck@...omium.org,
	jwerner@...omium.org, kishon@...com, robh+dt@...nel.org,
	pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
	linux-usb@...r.kernel.org, linux-rockchip@...ts.infradead.org,
	xzy.xu@...k-chips.com, kever.yang@...k-chips.com,
	huangtao@...k-chips.com, william.wu@...k-chips.com,
	daniel.meng@...k-chips.com, frank.wang@...k-chips.com
Subject: Re: [PATCH v7 2/2] phy: rockchip-inno-usb2: add a new driver for
 Rockchip usb2phy

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@...k-chips.com>
>> Suggested-by: Heiko Stuebner <heiko@...ech.de>
>> Suggested-by: Guenter Roeck <linux@...ck-us.net>
>> Suggested-by: Doug Anderson <dianders@...omium.org>
> still looks nice, so still
> Reviewed-by: Heiko Stuebner <heiko@...ech.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