From: Samuel Ortiz <sameo@linux.intel.com>
To: Chanwoo Choi <cw00.choi@samsung.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"myungjoo.ham@samsung.com" <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [RESEND PATCH v2 1/2] MFD: MAX77693: add MAX77693 MFD driver
Date: Fri, 11 May 2012 16:15:08 +0200 [thread overview]
Message-ID: <20120511141508.GQ1214@sortiz-mobl> (raw)
In-Reply-To: <4F67D86E.30509@samsung.com>
Hi Choi,
On Tue, Mar 20, 2012 at 10:07:58AM +0900, Chanwoo Choi wrote:
> @@ -0,0 +1,224 @@
> +/*
> + * max77693.c - mfd core driver for the MAX 77693
> + *
> + * Copyright (C) 2011 Samsung Electronics
2012 ?
> +int max77693_read_reg(struct i2c_client *i2c, u8 reg, u8 *dest)
> +{
> + struct max77693_dev *max77693 = i2c_get_clientdata(i2c);
> + int ret;
> +
> + mutex_lock(&max77693->iolock);
> + ret = i2c_smbus_read_byte_data(i2c, reg);
> + mutex_unlock(&max77693->iolock);
You don't need this locking as the i2c layer will do it for you.
Also, this definitely look like a good candidate for a regmap API conversion,
I'd appreciate if you could work on that.
> +static struct i2c_driver max77693_i2c_driver = {
> + .driver = {
> + .name = "max77693",
> + .owner = THIS_MODULE,
> + },
> + .probe = max77693_i2c_probe,
> + .remove = max77693_i2c_remove,
> + .id_table = max77693_i2c_id,
> +};
> +
> +static int __init max77693_i2c_init(void)
> +{
> + return i2c_add_driver(&max77693_i2c_driver);
> +}
> +/* init early so consumer devices can complete system boot */
> +subsys_initcall(max77693_i2c_init);
> +
> +static void __exit max77693_i2c_exit(void)
> +{
> + i2c_del_driver(&max77693_i2c_driver);
> +}
> +module_exit(max77693_i2c_exit);
You could use module_i2c_driver() here.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-05-11 14:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 5:28 [RESEND PATCH 1/2] MFD: MAX77693: add MAX77693 MFD driver Chanwoo Choi
2012-03-13 5:35 ` Venu Byravarasu
2012-03-13 5:39 ` Kyungmin Park
2012-03-13 5:52 ` Venu Byravarasu
2012-03-13 7:12 ` Chanwoo Choi
2012-03-13 7:19 ` Venu Byravarasu
2012-03-14 17:21 ` Mark Brown
2012-03-15 10:13 ` Chanwoo Choi
2012-03-20 1:07 ` [RESEND PATCH v2 " Chanwoo Choi
2012-05-11 14:15 ` Samuel Ortiz [this message]
2012-05-11 14:25 ` Kyungmin Park
2012-05-11 14:28 ` Kyungmin Park
2012-05-13 10:07 ` Mark Brown
2012-05-14 5:04 ` Chanwoo Choi
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=20120511141508.GQ1214@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=cw00.choi@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
/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