public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@the-dreams.de>
To: Gao Pan <pandy.gao@nxp.com>
Cc: u.kleine-koenig@pengutronix.de, 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: Sat, 16 Apr 2016 23:29:11 +0200	[thread overview]
Message-ID: <20160416212911.GE1522@katana> (raw)
In-Reply-To: <1458035482-14905-1-git-send-email-pandy.gao@nxp.com>

[-- Attachment #1: Type: text/plain, Size: 889 bytes --]

On Tue, Mar 15, 2016 at 05:51:22PM +0800, 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>

Since you need to resend anyhow (DT support?), just a few high-level
things.

There is a lot of dev_dbg in here. Some of them are helpful when
developing the driver, but not anymore once the driver is upstream.
Please check for that.

> +static int __init i2c_adap_imx_init(void)
> +{
> +	return platform_driver_register(&i2c_imx7ulp_driver);
> +}
> +subsys_initcall(i2c_adap_imx_init);

I usually don't accept subsys_initcall() for new drivers anymore. It
usually works around problems. Make sure your I2C clients do defer
probing properly.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-04-16 21:29 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
2016-03-16  2:21   ` Pan Gao
2016-04-16 21:29 ` Wolfram Sang [this message]
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=20160416212911.GE1522@katana \
    --to=wsa@the-dreams.de \
    --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 \
    /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