From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Boyd Subject: Re: [PATCH] drm/msm/hdmi: set hdp clock rate before prepare_enable call Date: Mon, 09 Jun 2014 10:56:28 -0700 Message-ID: <5395F54C.3080806@codeaurora.org> References: <1402063412-10407-1-git-send-email-sviau@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from smtp.codeaurora.org ([198.145.11.231]:50945 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753901AbaFIR4a (ORCPT ); Mon, 9 Jun 2014 13:56:30 -0400 In-Reply-To: <1402063412-10407-1-git-send-email-sviau@codeaurora.org> Sender: linux-arm-msm-owner@vger.kernel.org List-Id: linux-arm-msm@vger.kernel.org To: Stephane Viau Cc: robdclark@gmail.com, dri-devel@lists.freedesktop.org, linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org On 06/06/14 07:03, Stephane Viau wrote: > The clock driver usually complains when a clock is being prepared > before setting its rate. It is the case here for "core_clk" which > needs to be set at 19.2 MHz before we attempt a prepare_enable(). That's only true in the downstream vendor kernel. Upstream we detect all rates when clocks are registered. Given that 19.2Mhz is the default rate out of reset for this clock this patch is fairly useless. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation