From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from wolverine02.qualcomm.com ([199.106.114.251]:2395 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753937Ab0G1QmF (ORCPT ); Wed, 28 Jul 2010 12:42:05 -0400 Subject: Re: [PATCH 3/7] msm: update clk rate to use min/max values From: Daniel Walker In-Reply-To: <4C505952.3080100@codeaurora.org> References: <1280264672-19364-1-git-send-email-dwalker@codeaurora.org> <1280264672-19364-3-git-send-email-dwalker@codeaurora.org> <4C505952.3080100@codeaurora.org> Content-Type: text/plain; charset="UTF-8" Date: Wed, 28 Jul 2010 09:41:56 -0700 Message-ID: <1280335316.21185.4.camel@c-dwalke-linux.qualcomm.com> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-arm-msm-owner@vger.kernel.org List-ID: To: Neil Leeder Cc: linux-arm-msm@vger.kernel.org On Wed, 2010-07-28 at 12:22 -0400, Neil Leeder wrote: > On 7/27/2010 5:04 PM, Daniel Walker wrote: > > > static struct msm_mddi_platform_data mddi_pdata = { > > - .clk_rate = 122880000, > > + .min_clk_rate = 122880000, > > + .min_clk_rate = 98304000, > One of those should probably be max... Ooops, True .. What do you think of this patch in general ? How are we doing this in the staging driver? Daniel -- Sent by an consultant of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.