linux-kernel - Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi

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]

Date:	Wed, 17 Feb 2016 08:21:58 +0800
From:	Jianqun Xu <jay.xu@...k-chips.com>
To:	Heiko Stuebner <heiko@...ech.de>, Mark Brown <broonie@...nel.org>
Cc:	robh+dt@...nel.org, pawel.moll@....com, mark.rutland@....com,
	ijc+devicetree@...lion.org.uk, galak@...eaurora.org,
	jwerner@...omium.org, huangtao@...k-chips.com,
	linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi

Hi Heiko

在 16/02/2016 22:37, Heiko Stuebner 写道:
> Am Dienstag, 16. Februar 2016, 13:22:23 schrieb Mark Brown:
>> On Tue, Feb 16, 2016 at 05:22:18PM +0800, jianqun.xu wrote:
>>>   Documentation/devicetree/bindings/spi/spi-rockchip.txt | 1 +
>>>   1 file changed, 1 insertion(+)
>>
>> I'd expect this to be added to both the driver and the binding document
>> not just the document.
>
> It seems the driver can still use the rk3066-variant - aka nobody has found
> specific issues in the rk3399 IP implementation.
>
> Having the more specific IP names already in the dts before actually using
> them was suggested by devicetree people to not have to exchange everything
> once specific issues were found.
>
> So right now it's using the fallback-mechanism of binding to the rk3066
> name, but if some obstacle appears it will only take adding the binding in
> the driver to make it work (even with old devicetrees).
>
>
Thank you, got it, and I will re-send this patch with the driver patch.
>