From: "Zhu, Lejun" <lejun.zhu@linux.intel.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: broonie@kernel.org, sameo@linux.intel.com,
linux-kernel@vger.kernel.org, jacob.jun.pan@linux.intel.com,
bin.yang@intel.com
Subject: Re: [PATCH v3 1/4] mfd: intel_soc_pmic: Core driver
Date: Wed, 28 May 2014 11:07:03 +0800 [thread overview]
Message-ID: <538552D7.1000408@linux.intel.com> (raw)
In-Reply-To: <20140527153541.GB4227@lee--X1>
On 5/27/2014 11:35 PM, Lee Jones wrote:
>> This patch provides the common code for the intel_soc_pmic MFD driver, such as read/write register and set up IRQ.
(...)
>> +/*
>> +* Set and clear multiple bits of a PMIC register
>> +*/
>> +int intel_soc_pmic_update(int reg, u8 val, u8 mask)
>> +{
>> + int ret;
>> +
>> + mutex_lock(&pmic_lock);
>> +
>> + if (!pmic)
>> + ret = -EIO;
>> + else
>> + ret = regmap_update_bits(pmic->regmap, reg, mask, val);
>> +
>> + mutex_unlock(&pmic_lock);
>> +
>> + return ret;
>> +}
>> +EXPORT_SYMBOL_GPL(intel_soc_pmic_update);
>
> I'm really not a fan of all these pointless agregation call-backs. I
> see them as unesersary overhead. Just use the regmap API directly.
OK. I'll remove these wrappers from the MFD driver, seems no one likes
them...
I'll fix the patch set as you suggested and resubmit. Thank you for
reviewing this.
Best Regards
Lejun
next prev parent reply other threads:[~2014-05-28 3:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 4:06 [PATCH v3 0/4] mfd: Intel SoC Power Management IC Zhu, Lejun
2014-05-27 4:06 ` [PATCH v3 1/4] mfd: intel_soc_pmic: Core driver Zhu, Lejun
2014-05-27 15:35 ` Lee Jones
2014-05-28 3:07 ` Zhu, Lejun [this message]
2014-05-27 4:06 ` [PATCH v3 2/4] mfd: intel_soc_pmic: I2C interface Zhu, Lejun
2014-05-27 16:04 ` Lee Jones
2014-05-27 4:06 ` [PATCH v3 3/4] mfd: intel_soc_pmic: Crystal Cove support Zhu, Lejun
2014-05-27 16:47 ` Lee Jones
2014-05-27 4:06 ` [PATCH v3 4/4] mfd: intel_soc_pmic: Build files Zhu, Lejun
2014-05-27 16:49 ` Lee Jones
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=538552D7.1000408@linux.intel.com \
--to=lejun.zhu@linux.intel.com \
--cc=bin.yang@intel.com \
--cc=broonie@kernel.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).