From: Mark Brown <broonie@kernel.org>
To: Guodong Xu <guodong.xu@linaro.org>
Cc: sameo@linux.intel.com, lgirdwood@gmail.com,
linux-kernel@vger.kernel.org, patches@linaro.org,
Haojian Zhuang <haojian.zhuang@linaro.org>
Subject: Re: [PATCH 1/3] mfd: Add hi6421 PMIC core driver
Date: Tue, 4 Jun 2013 17:44:40 +0100 [thread overview]
Message-ID: <20130604164440.GE31367@sirena.org.uk> (raw)
In-Reply-To: <1370356123-22357-2-git-send-email-guodong.xu@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 2589 bytes --]
On Tue, Jun 04, 2013 at 10:28:41PM +0800, Guodong Xu wrote:
> +static struct of_device_id of_hi6421_pmic_child_match_tbl[] = {
> + /* regulators */
> + {
> + .compatible = "hisilicon,hi6421-ldo",
> + },
> + {
> + .compatible = "hisilicon,hi6421-buck012",
> + },
> + {
> + .compatible = "hisilicon,hi6421-buck345",
> + },
> + { /* end */ }
> +};
I would expect this to be in the regulator driver.
> +/*
> + * The PMIC register is only 8-bit.
> + * Hisilicon SoC use hardware to map PMIC register into SoC mapping.
> + * At here, we are accessing SoC register with 32-bit.
> + */
> +u32 hi6421_pmic_read(struct hi6421_pmic *pmic, int reg)
> +{
> + unsigned long flags;
> + u32 ret;
> + spin_lock_irqsave(&pmic->lock, flags);
> + ret = readl_relaxed(pmic->regs + (reg << 2));
> + spin_unlock_irqrestore(&pmic->lock, flags);
> + return ret;
> +}
> +EXPORT_SYMBOL(hi6421_pmic_read);
This all looks like you want to be using regmap MMIO. This would save a
bit of code and get you access to infrastructure like tracepoints and
debugfs regiseter dumps as well as the regulator API helpers.
> + if (!devm_request_mem_region(dev, pmic->res->start,
> + resource_size(pmic->res),
> + pdev->name)) {
> + dev_err(dev, "cannot claim register memory\n");
> + return -ENOMEM;
> + }
> +
> + pmic->regs = devm_ioremap(dev, pmic->res->start,
> + resource_size(pmic->res));
devm_request_and_ioremap().
> + /* populate sub nodes */
> + of_platform_populate(np, of_hi6421_pmic_child_match_tbl, NULL, dev);
You should be using the MFD API for this.
> +static int hi6421_pmic_remove(struct platform_device *pdev)
> +{
> + struct device *dev = &pdev->dev;
> + struct hi6421_pmic *pmic = platform_get_drvdata(pdev);
> +
> + devm_iounmap(dev, pmic->regs);
> + devm_release_mem_region(dev, pmic->res->start,
> + resource_size(pmic->res));
> + devm_kfree(dev, pmic);
No point in cleaning up devm_ stuff, a major goal of the API is to save
writing that code. The only thing that's needed is to remove the MFD
children which you're not doing.
> + platform_set_drvdata(pdev, NULL);
This isn't required, it's never OK to access the driver data unless from
code that set it.
> +#define OCP_DEB_CTRL_REG (0x51)
> +#define OCP_DEB_SEL_MASK (0x0C)
> +#define OCP_DEB_SEL_8MS (0x00)
> +#define OCP_DEB_SEL_16MS (0x04)
> +#define OCP_DEB_SEL_32MS (0x08)
> +#define OCP_DEB_SEL_64MS (0x0C)
> +#define OCP_EN_DEBOUNCE_MASK (0x02)
> +#define OCP_EN_DEBOUNCE_ENABLE (0x02)
> +#define OCP_AUTO_STOP_MASK (0x01)
> +#define OCP_AUTO_STOP_ENABLE (0x01)
These should be namespaced.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-06-04 16:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 14:28 [PATCH 0/3] regulator: add driver for Hi6421 PMIC SoC Guodong Xu
2013-06-04 14:28 ` [PATCH 1/3] mfd: Add hi6421 PMIC core driver Guodong Xu
2013-06-04 16:44 ` Mark Brown [this message]
2013-06-04 14:28 ` [PATCH 2/3] regulator: add driver for hi6421 voltage regulator Guodong Xu
2013-06-04 17:15 ` Mark Brown
2013-06-04 14:28 ` [PATCH 3/3] ARM: dts: add dedicated dtsi for hi6421 Guodong Xu
2013-06-04 16:45 ` Mark Brown
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=20130604164440.GE31367@sirena.org.uk \
--to=broonie@kernel.org \
--cc=guodong.xu@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.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
all inboxes | Powered by JetHome®