From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Liao Subject: Re: [PATCH] soc: mediatek: Fix random hang up issue while kernel init Date: Thu, 1 Oct 2015 14:58:52 +0800 Message-ID: <1443682732.1714.11.camel@mtksdaap41> References: <1443162717-64831-1-git-send-email-jamesjj.liao@mediatek.com> <1443169573.3135.9.camel@pengutronix.de> <5607D224.4050801@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Daniel Kurtz Cc: Matthias Brugger , Lucas Stach , Sascha Hauer , "linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , "open list:OPEN FIRMWARE AND..." , srv_heupstream , Kevin Hilman , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , linux-mediatek-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-mediatek@lists.infradead.org Hi Daniel, Thanks for your help to explain the patch. On Tue, 2015-09-29 at 18:25 +0800, Daniel Kurtz wrote: > On Sun, Sep 27, 2015 at 7:25 PM, Matthias Brugger > wrote: > >> But then we at least need a corresponding change to the binding documentation. I'll send a new patch with changing binding document. > If the existing bindings are not used anywhere yet (*), it seems like > unnecessary overhead to enforce backwards compatibility at this stage. > > (*) I don't actually know if this is true, perhaps only Mediatek can > answer this. What does the meaning of existing bindings are used anywhere? Do you mean this binding is used by other SoCs ? Currently scpsys driver can't be shared between different Mediatek SoCs because the power domains are different from each other. So I think it should no need to maintain backward compatibility on scpsys's binding. > > Apart from that, please send the dtsi part as a seperate patch. OK. Best regards, James -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html From mboxrd@z Thu Jan 1 00:00:00 1970 From: jamesjj.liao@mediatek.com (James Liao) Date: Thu, 1 Oct 2015 14:58:52 +0800 Subject: [PATCH] soc: mediatek: Fix random hang up issue while kernel init In-Reply-To: References: <1443162717-64831-1-git-send-email-jamesjj.liao@mediatek.com> <1443169573.3135.9.camel@pengutronix.de> <5607D224.4050801@gmail.com> Message-ID: <1443682732.1714.11.camel@mtksdaap41> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi Daniel, Thanks for your help to explain the patch. On Tue, 2015-09-29 at 18:25 +0800, Daniel Kurtz wrote: > On Sun, Sep 27, 2015 at 7:25 PM, Matthias Brugger > wrote: > >> But then we at least need a corresponding change to the binding documentation. I'll send a new patch with changing binding document. > If the existing bindings are not used anywhere yet (*), it seems like > unnecessary overhead to enforce backwards compatibility at this stage. > > (*) I don't actually know if this is true, perhaps only Mediatek can > answer this. What does the meaning of existing bindings are used anywhere? Do you mean this binding is used by other SoCs ? Currently scpsys driver can't be shared between different Mediatek SoCs because the power domains are different from each other. So I think it should no need to maintain backward compatibility on scpsys's binding. > > Apart from that, please send the dtsi part as a seperate patch. OK. Best regards, James From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755539AbbJAG7A (ORCPT ); Thu, 1 Oct 2015 02:59:00 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:42945 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1752758AbbJAG64 (ORCPT ); Thu, 1 Oct 2015 02:58:56 -0400 X-Listener-Flag: 11101 Message-ID: <1443682732.1714.11.camel@mtksdaap41> Subject: Re: [PATCH] soc: mediatek: Fix random hang up issue while kernel init From: James Liao To: Daniel Kurtz CC: Matthias Brugger , Lucas Stach , Sascha Hauer , "linux-arm-kernel@lists.infradead.org" , "open list:OPEN FIRMWARE AND..." , srv_heupstream , Kevin Hilman , "linux-kernel@vger.kernel.org" , Date: Thu, 1 Oct 2015 14:58:52 +0800 In-Reply-To: References: <1443162717-64831-1-git-send-email-jamesjj.liao@mediatek.com> <1443169573.3135.9.camel@pengutronix.de> <5607D224.4050801@gmail.com> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel, Thanks for your help to explain the patch. On Tue, 2015-09-29 at 18:25 +0800, Daniel Kurtz wrote: > On Sun, Sep 27, 2015 at 7:25 PM, Matthias Brugger > wrote: > >> But then we at least need a corresponding change to the binding documentation. I'll send a new patch with changing binding document. > If the existing bindings are not used anywhere yet (*), it seems like > unnecessary overhead to enforce backwards compatibility at this stage. > > (*) I don't actually know if this is true, perhaps only Mediatek can > answer this. What does the meaning of existing bindings are used anywhere? Do you mean this binding is used by other SoCs ? Currently scpsys driver can't be shared between different Mediatek SoCs because the power domains are different from each other. So I think it should no need to maintain backward compatibility on scpsys's binding. > > Apart from that, please send the dtsi part as a seperate patch. OK. Best regards, James