Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754694AbbLPPHY (ORCPT ); Wed, 16 Dec 2015 10:07:24 -0500 Received: from mga09.intel.com ([134.134.136.24]:45544 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752042AbbLPPHW (ORCPT ); Wed, 16 Dec 2015 10:07:22 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,437,1444719600"; d="scan'208";a="874940665" Date: Wed, 16 Dec 2015 17:04:46 +0200 From: Mika Westerberg To: Suravee Suthikulpanit Cc: wsa@the-dreams.de, lho@apm.com, Ken.Xue@amd.com, linux-i2c@vger.kernel.org, linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org, Jarkko Nikula , Andy Shevchenko Subject: Re: [PATCH] i2c: designware: Do not require clock when SSCN and FFCN are provided Message-ID: <20151216150446.GY1762@lahna.fi.intel.com> References: <1450219138-5868-1-git-send-email-Suravee.Suthikulpanit@amd.com> <20151216094202.GR1762@lahna.fi.intel.com> <56717100.3020602@amd.com> <20151216142810.GW1762@lahna.fi.intel.com> <567178D2.30002@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <567178D2.30002@amd.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 844 Lines: 19 On Wed, Dec 16, 2015 at 08:44:34AM -0600, Suravee Suthikulpanit wrote: > I am trying to avoid having to hard-coded clock frequency value in the > driver. Would it be alright to not return w/ error, and just do the > following? > > dev->clk = devm_clk_get(&pdev->dev, NULL); > if (!IS_ERR(dev->clk)) > dev->get_clk_rate_khz = i2c_dw_get_clk_rate_khz; > > This should work for the Intel case when clock is also provided. Does it also work when clk_prepare_enable()/disable() is called for the clock (in PM callbacks for example)? If yes, then I don't see problems with what you are suggesting. -- 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/