Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754029AbaFXXAl (ORCPT ); Tue, 24 Jun 2014 19:00:41 -0400 Received: from mail-vc0-f172.google.com ([209.85.220.172]:50823 "EHLO mail-vc0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751479AbaFXXAj (ORCPT ); Tue, 24 Jun 2014 19:00:39 -0400 MIME-Version: 1.0 In-Reply-To: <1402464739-19044-3-git-send-email-tushar.b@samsung.com> References: <1402464739-19044-1-git-send-email-tushar.b@samsung.com> <1402464739-19044-3-git-send-email-tushar.b@samsung.com> Date: Tue, 24 Jun 2014 16:00:38 -0700 Message-ID: Subject: Re: [PATCH 2/3] ARM: dts: Update the parent for Audss clocks in Exynos5420 From: Doug Anderson To: Tushar Behera , Kukjin Kim , Kukjin Kim Cc: "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , linux-samsung-soc , "linux-arm-kernel@lists.infradead.org" , Mike Turquette , Tomasz Figa , Russell King , Kumar Gala , Ian Campbell , Mark Rutland , Pawel Moll , Rob Herring , Kevin Hilman , Tushar Behera , Shaik Ameer Basha Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Tushar, On Tue, Jun 10, 2014 at 10:32 PM, Tushar Behera wrote: > Currently CLK_FOUT_EPLL was set as one of the parents of AUDSS mux. > As per the user manual, it should be CLK_MAU_EPLL. > > The problem surfaced when the bootloader in Peach-pit board set > the EPLL clock as the parent of AUDSS mux. While booting the kernel, > we used to get a system hang during late boot if CLK_MAU_EPLL was > disabled. > > Signed-off-by: Tushar Behera > Signed-off-by: Shaik Ameer Basha > Reported-by: Kevin Hilman > --- > arch/arm/boot/dts/exynos5420.dtsi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) I've tested this myself now as well. Tested-by: Doug Anderson -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/