[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151216150446.GY1762@lahna.fi.intel.com>
Date: Wed, 16 Dec 2015 17:04:46 +0200
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Suravee Suthikulpanit <Suravee.Suthikulpanit@....com>
Cc: wsa@...-dreams.de, lho@....com, Ken.Xue@....com,
linux-i2c@...r.kernel.org, linux-acpi@...r.kernel.org,
linux-kernel@...r.kernel.org,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH] i2c: designware: Do not require clock when SSCN and FFCN
are provided
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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists