From: Mark Brown <broonie@kernel.org>
To: Tomasz Figa <t.figa@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Kukjin Kim <kgene.kim@samsung.com>,
Alessandro Zummo <a.zummo@towertech.it>,
Grant Likely <grant.likely@linaro.org>,
Jiri Kosina <jkosina@suse.cz>,
Liam Girdwood <lgirdwood@gmail.com>,
Masanari Iida <standby24x7@gmail.com>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>,
rtc-linux@googlegroups.com, Russell King <linux@arm.linux.org.uk>,
Samuel Ortiz <sameo@linux.intel.com>,
Kyungmin Park <kyungmin.park@samsung.com>
Subject: Re: [PATCH v2 3/3] mfd: max8998: Add support for Device Tree
Date: Fri, 21 Jun 2013 15:37:45 +0100 [thread overview]
Message-ID: <20130621143745.GV27646@sirena.org.uk> (raw)
In-Reply-To: <1371818017-5215-4-git-send-email-t.figa@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1388 bytes --]
On Fri, Jun 21, 2013 at 02:33:37PM +0200, Tomasz Figa wrote:
> + - EN32KHz AP: 32KHz clock output for application processor
> + - EN32KHz CP: 32KHz clock output for call processor
The clocks should be supported using the clock API not the regulator
API, they shouldn't be present in the DT regulator binding.
> + if (iodev->dev->of_node) {
> + ret = max8998_pmic_dt_parse_pdata(iodev, pdata);
> + if (ret)
> + return ret;
> + }
> +
Might be neater to have the check inside the function?
> if (IS_ERR(rdev[i])) {
> ret = PTR_ERR(rdev[i]);
> - dev_err(max8998->dev, "regulator init failed\n");
> + dev_err(max8998->dev, "regulator %s init failed\n",
> + regulators[index].name);
Print the error code (the original doesn't but since you're changing
it...)?
> index 46f2301..042a873 100644
> --- a/drivers/rtc/rtc-max8998.c
> +++ b/drivers/rtc/rtc-max8998.c
> @@ -253,7 +253,7 @@ static const struct rtc_class_ops max8998_rtc_ops = {
> static int max8998_rtc_probe(struct platform_device *pdev)
> {
> struct max8998_dev *max8998 = dev_get_drvdata(pdev->dev.parent);
> - struct max8998_platform_data *pdata = dev_get_platdata(max8998->dev);
> + struct max8998_platform_data *pdata = max8998->pdata;
> struct max8998_rtc_info *info;
> int ret;
>
Probably better to split out this refactoring into a separate patch.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-06-21 14:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 12:33 [PATCH v2 0/3] regulator: " Tomasz Figa
2013-06-21 12:33 ` [PATCH v2 1/3] mfd: Add irq domain support for max8998 interrupts Tomasz Figa
2013-06-21 14:12 ` Rasmus Villemoes
2013-06-21 14:31 ` Mark Brown
2013-06-21 12:33 ` [PATCH v2 2/3] regulator: max8998: Use arrays for specifying voltages in platform data Tomasz Figa
2013-06-21 14:39 ` Mark Brown
2013-06-21 12:33 ` [PATCH v2 3/3] mfd: max8998: Add support for Device Tree Tomasz Figa
2013-06-21 14:37 ` Mark Brown [this message]
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=20130621143745.GV27646@sirena.org.uk \
--to=broonie@kernel.org \
--cc=a.zummo@towertech.it \
--cc=grant.likely@linaro.org \
--cc=jkosina@suse.cz \
--cc=kgene.kim@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rtc-linux@googlegroups.com \
--cc=sameo@linux.intel.com \
--cc=standby24x7@gmail.com \
--cc=t.figa@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
all inboxes | Powered by JetHome®