From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933454AbbI1MxL (ORCPT ); Mon, 28 Sep 2015 08:53:11 -0400 Received: from regular1.263xmail.com ([211.150.99.139]:47589 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932950AbbI1MxK (ORCPT ); Mon, 28 Sep 2015 08:53:10 -0400 X-263anti-spam: KSV:0;BIG:0;ABS:1;DNS:0;ATT:0;SPF:S; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-KSVirus-check: 0 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ADDR-CHECKED: 0 X-RL-SENDER: zhengxing@rock-chips.com X-FST-TO: heiko@sntech.de X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: zhengxing@rock-chips.com X-UNIQUE-TAG: <28de42170594ff16a67c4a34c1e75e4f> X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Message-ID: <5609382F.2000203@rock-chips.com> Date: Mon, 28 Sep 2015 20:53:03 +0800 From: Xing Zheng User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120410 Thunderbird/11.0.1 MIME-Version: 1.0 To: =?UTF-8?B?SGVpa28gU3TDvGJuZXI=?= CC: linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 7/9] rockchip: make sure timer5 is enabled on rk3036 platforms References: <1442478540-15068-1-git-send-email-zhengxing@rock-chips.com> <11125723.j2J5LpAGi4@diego> <560931A3.2020403@rock-chips.com> <1726823.4nE2gJuWPe@diego> In-Reply-To: <1726823.4nE2gJuWPe@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 On 2015年09月28日 20:44, Heiko Stübner wrote: > Hi, > > Am Montag, 28. September 2015, 20:25:07 schrieb Xing Zheng: >> On 2015年09月17日 23:05, Heiko Stübner wrote: >>> Am Donnerstag, 17. September 2015, 18:37:24 schrieb Xing Zheng: >>>> The timer5 supplies the architected timer and thus as has to run when >>>> the system clocksource and clockevents drivers are registered. >>> please kindly ask the people doing uboot development to do this in uboot >>> itself in future socs :-) - for example Simon's rk3288 mainline uboot does >>> this correctly. >> OK, I will ask the engineer who is doing uboot whether needs to add >> this patch. So I will remove it from the patchset v3 of "Build and support >> rk3036 SoC platform". > No, I really only meant try to make people get this right in the future :-). > > For the rk3036 there are probably already devices on the market with uboots > sporting that issue. So it's ok to have this in here now, it's just to make > sure it gets really fixed in future socs. > > > Heiko > > OK, I got it. Thank you. :)