From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: Gao Pan <pandy.gao@nxp.com>,
wsa@the-dreams.de, u.kleine-koenig@pengutronix.de
Cc: linux-i2c@vger.kernel.org, frank.li@nxp.com, fugang.duan@nxp.com
Subject: Re: [Patch v1] i2c: imx7ulp: add i.MX7ULP i2c controller bus driver
Date: Tue, 15 Mar 2016 14:42:09 +0200 [thread overview]
Message-ID: <56E80321.6090105@mentor.com> (raw)
In-Reply-To: <1458035482-14905-1-git-send-email-pandy.gao@nxp.com>
Hello,
On 15.03.2016 11:51, Gao Pan wrote:
> Add i.MX7ULP i2c bus driver which can continue operating
> in stop modes provided an appropriate clock is available.
>
> It is also designed for low CPU overhead with DMA offloading
> of FIFO register accesses.
>
> Signed-off-by: Gao Pan <pandy.gao@nxp.com>
> ---
[snip]
> +
> +static int i2c_imx7ulp_start(struct imx7ulp_i2c_struct *i2c_imx7ulp)
> +{
> + int ret;
> + unsigned int temp;
> +
> + dev_dbg(&i2c_imx7ulp->adapter.dev, "<%s>\n", __func__);
> +
> + ret = clk_prepare_enable(i2c_imx7ulp->bus_clk);
> + if (ret) {
> + dev_err(&i2c_imx7ulp->adapter.dev,
> + "can't enable I2C bus clock, ret=%d\n", ret);
> + return ret;
> + }
> +
> + ret = clk_prepare_enable(i2c_imx7ulp->per_clk);
> + if (ret) {
> + dev_err(&i2c_imx7ulp->adapter.dev,
> + "can't enable I2C peripheral clock, ret=%d\n", ret);
> + return ret;
Leaked prepared/enabled i2c_imx7ulp->bus_clk clock on error path.
> + }
> +
--
With best wishes,
Vladimir
next prev parent reply other threads:[~2016-03-15 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 9:51 [Patch v1] i2c: imx7ulp: add i.MX7ULP i2c controller bus driver Gao Pan
2016-03-15 10:14 ` Uwe Kleine-König
2016-03-16 5:48 ` Pan Gao
2016-03-15 12:42 ` Vladimir Zapolskiy [this message]
2016-03-16 2:21 ` Pan Gao
2016-04-16 21:29 ` Wolfram Sang
2016-04-18 2:05 ` Pan Gao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56E80321.6090105@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=frank.li@nxp.com \
--cc=fugang.duan@nxp.com \
--cc=linux-i2c@vger.kernel.org \
--cc=pandy.gao@nxp.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wsa@the-dreams.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox