From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964889AbcBQAWM (ORCPT ); Tue, 16 Feb 2016 19:22:12 -0500 Received: from regular1.263xmail.com ([211.150.99.131]:42698 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964793AbcBQAWL (ORCPT ); Tue, 16 Feb 2016 19:22:11 -0500 X-Greylist: delayed 53973 seconds by postgrey-1.27 at vger.kernel.org; Tue, 16 Feb 2016 19:22:10 EST 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: jay.xu@rock-chips.com X-FST-TO: devicetree@vger.kernel.org X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: jay.xu@rock-chips.com X-UNIQUE-TAG: <2c9853037b7185507f72249c612c4d38> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [PATCH] spi/rockchip: Add dt-binding for Rockchip rk3399 spi To: Heiko Stuebner , Mark Brown References: <1455614538-4415-1-git-send-email-jay.xu@rock-chips.com> <20160216132223.GM18327@sirena.org.uk> <1730751.NYv1NxJVuB@phil> Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, jwerner@chromium.org, huangtao@rock-chips.com, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org From: Jianqun Xu Message-ID: <56C3BD26.3030704@rock-chips.com> Date: Wed, 17 Feb 2016 08:21:58 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 In-Reply-To: <1730751.NYv1NxJVuB@phil> Content-Type: text/plain; charset=gbk; 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 ÔÚ 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. >