From: Jonathan Cameron <jic23@kernel.org>
To: Jacob Pan <jacob.jun.pan@linux.intel.com>,
IIO <linux-iio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
DEVICE TREE <devicetree@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>
Cc: Carlo Caione <carlo@caione.org>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Aaron Lu <aaron.lu@intel.com>, Alan Cox <alan@linux.intel.com>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Grant Likely <grant.likely@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Hartmut Knaack <knaack.h@gmx.de>,
Fugang Duan <B38611@freescale.com>, Arnd Bergmann <arnd@arndb.de>,
Zubair Lutfullah <zubair.lutfullah@gmail.com>,
Sebastian Reichel <sre@debian.org>,
Johannes Thumshirn <johannes.thumshirn@men.de>,
Philippe Reynes <tremyfr@yahoo.fr>,
Angelo Compagnucci <angelo.compagnucci@gmail.com>,
Doug Anderson <dianders@chromium.org>,
Ramakrishna Pallala <ramakrishna.pallala@intel.com>,
Peter Meerwald <pmeerw@pmeerw.net>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Rafael Wysocki <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH v4 2/3] iio/adc: add support for axp288 adc
Date: Sun, 21 Sep 2014 14:14:17 +0100 [thread overview]
Message-ID: <541ECF29.8060006@kernel.org> (raw)
In-Reply-To: <1410912715-25903-3-git-send-email-jacob.jun.pan@linux.intel.com>
On 17/09/14 01:11, Jacob Pan wrote:
> Platform driver for X-Powers AXP288 ADC, which is a sub-device of the
> customized AXP288 PMIC for Intel Baytrail-CR platforms. GPADC device
> enumerates as one of the MFD cell devices. It uses IIO infrastructure
> to communicate with userspace and consumer drivers.
>
> Usages of ADC channels include battery charging and thermal sensors.
>
> Based on initial work by:
> Ramakrishna Pallala <ramakrishna.pallala@intel.com>
>
> Signed-off-by: Jacob Pan <jacob.jun.pan@linux.intel.com>
A few more bits from me...
Jonathan
> ---
> drivers/iio/adc/Kconfig | 8 ++
> drivers/iio/adc/Makefile | 1 +
> drivers/iio/adc/axp288_adc.c | 254 +++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 263 insertions(+)
> create mode 100644 drivers/iio/adc/axp288_adc.c
>
> diff --git a/drivers/iio/adc/Kconfig b/drivers/iio/adc/Kconfig
> index 11b048a..db2681b 100644
> --- a/drivers/iio/adc/Kconfig
> +++ b/drivers/iio/adc/Kconfig
> @@ -127,6 +127,14 @@ config AT91_ADC
> help
> Say yes here to build support for Atmel AT91 ADC.
>
> +config AXP288_ADC
> + tristate "X-Powers AXP288 ADC driver"
> + depends on MFD_AXP20X
> + help
> + Say yes here to have support for X-Powers power management IC (PMIC) ADC
> + device. Depending on platform configuration, this general purpose ADC can
> + be used for sampling sensors such as thermal resistors.
> +
> config EXYNOS_ADC
> tristate "Exynos ADC driver support"
> depends on ARCH_EXYNOS || (OF && COMPILE_TEST)
> diff --git a/drivers/iio/adc/Makefile b/drivers/iio/adc/Makefile
> index ad81b51..19640f9 100644
> --- a/drivers/iio/adc/Makefile
> +++ b/drivers/iio/adc/Makefile
> @@ -14,6 +14,7 @@ obj-$(CONFIG_AD7793) += ad7793.o
> obj-$(CONFIG_AD7887) += ad7887.o
> obj-$(CONFIG_AD799X) += ad799x.o
> obj-$(CONFIG_AT91_ADC) += at91_adc.o
> +obj-$(CONFIG_AXP288_ADC) += axp288_adc.o
> obj-$(CONFIG_EXYNOS_ADC) += exynos_adc.o
> obj-$(CONFIG_LP8788_ADC) += lp8788_adc.o
> obj-$(CONFIG_MAX1027) += max1027.o
> diff --git a/drivers/iio/adc/axp288_adc.c b/drivers/iio/adc/axp288_adc.c
> new file mode 100644
> index 0000000..333c624
> --- /dev/null
> +++ b/drivers/iio/adc/axp288_adc.c
> @@ -0,0 +1,254 @@
> +/*
> + * axp288_adc.c - X-Powers AXP288 PMIC ADC Driver
> + *
> + * Copyright (C) 2014 Intel Corporation
> + *
> + * ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; version 2 of the License.
> + *
> + * This program is distributed in the hope that it will be useful, but
> + * WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * General Public License for more details.
> + *
> + */
> +
> +#include <linux/module.h>
> +#include <linux/kernel.h>
> +#include <linux/device.h>
> +#include <linux/regmap.h>
> +#include <linux/mfd/axp20x.h>
> +#include <linux/platform_device.h>
> +
> +#include <linux/iio/iio.h>
> +#include <linux/iio/machine.h>
> +#include <linux/iio/driver.h>
> +
> +#define AXP288_ADC_EN_MASK 0xF1
> +#define AXP288_ADC_TS_PIN_GPADC 0xF2
> +#define AXP288_ADC_TS_PIN_ON 0xF3
> +
> +enum axp288_adc_id {
> + AXP288_ADC_TS,
> + AXP288_ADC_PMIC,
> + AXP288_ADC_GP,
> + AXP288_ADC_BATT_CHRG_I,
> + AXP288_ADC_BATT_DISCHRG_I,
> + AXP288_ADC_BATT_V,
> + AXP288_ADC_NR_CHAN,
> +};
> +
> +struct axp288_adc_info {
> + int irq;
> + struct device *dev;
Is the dev element ever used?
> + struct regmap *regmap;
> +};
> +
> +static const struct iio_chan_spec const axp288_adc_channels[] = {
> + {
> + .indexed = 1,
> + .type = IIO_TEMP,
> + .channel = 0,
> + .address = AXP288_TS_ADC_H,
> + .datasheet_name = "CH0",
> + }, {
> + .indexed = 1,
> + .type = IIO_TEMP,
> + .channel = 1,
> + .address = AXP288_PMIC_ADC_H,
> + .datasheet_name = "CH1",
> + }, {
> + .indexed = 1,
> + .type = IIO_TEMP,
> + .channel = 2,
> + .address = AXP288_GP_ADC_H,
> + .datasheet_name = "CH2",
> + }, {
> + .indexed = 1,
> + .type = IIO_CURRENT,
> + .channel = 3,
> + .address = AXP20X_BATT_CHRG_I_H,
> + .datasheet_name = "CH3",
> + .info_mask_separate = BIT(IIO_CHAN_INFO_PROCESSED),
> + }, {
> + .indexed = 1,
> + .type = IIO_CURRENT,
> + .channel = 4,
> + .address = AXP20X_BATT_DISCHRG_I_H,
> + .datasheet_name = "CH4",
> + .info_mask_separate = BIT(IIO_CHAN_INFO_PROCESSED),
> + }, {
> + .indexed = 1,
> + .type = IIO_VOLTAGE,
> + .channel = 5,
> + .address = AXP20X_BATT_V_H,
> + .datasheet_name = "CH5",
> + .info_mask_separate = BIT(IIO_CHAN_INFO_PROCESSED),
> + },
> +};
> +
> +#define AXP288_ADC_MAP(_adc_channel_label, _consumer_dev_name, \
> + _consumer_channel) \
> + { \
> + .adc_channel_label = _adc_channel_label, \
> + .consumer_dev_name = _consumer_dev_name, \
> + .consumer_channel = _consumer_channel, \
> + }
> +
> +/* for consumer drivers */
> +static struct iio_map axp288_adc_default_maps[] = {
> + AXP288_ADC_MAP("TS_PIN", "axp288-batt", "axp288-batt-temp"),
> + AXP288_ADC_MAP("PMIC_TEMP", "axp288-pmic", "axp288-pmic-temp"),
> + AXP288_ADC_MAP("GPADC", "axp288-gpadc", "axp288-system-temp"),
> + AXP288_ADC_MAP("BATT_CHG_I", "axp288-chrg", "axp288-chrg-curr"),
> + AXP288_ADC_MAP("BATT_DISCHRG_I", "axp288-chrg", "axp288-chrg-d-curr"),
> + AXP288_ADC_MAP("BATT_V", "axp288-batt", "axp288-batt-volt"),
> + {},
> +};
> +
> +static int axp288_adc_read_raw(struct iio_dev *indio_dev,
> + struct iio_chan_spec const *chan,
> + int *val, int *val2, long mask)
> +{
> + int ret;
> + struct axp288_adc_info *info = iio_priv(indio_dev);
> + u8 buf[2];
> +
> + mutex_lock(&indio_dev->mlock);
> + switch (mask) {
> + case IIO_CHAN_INFO_RAW:
> + /* special case for GPADC sample */
> + if (chan->address == AXP288_GP_ADC_H) {
> + ret = regmap_write(info->regmap, AXP288_ADC_TS_PIN_CTRL,
> + AXP288_ADC_TS_PIN_GPADC);
> + if (ret) {
> + dev_err(&indio_dev->dev, "GPADC mode\n");
> + mutex_unlock(&indio_dev->mlock);
> + return ret;
> + }
> + }
> + case IIO_CHAN_INFO_PROCESSED:
> + ret = regmap_bulk_read(info->regmap, chan->address, buf, 2);
> + if (ret) {
> + dev_err(&indio_dev->dev, "sample raw data failed\n");
> + break;
> + }
> + *val = (buf[0] << 4) + ((buf[1] >> 4) & 0x0F);
> + ret = IIO_VAL_INT;
> + break;
> + default:
> + ret = -EINVAL;
> + }
> +
Why is this statement down here rather than in the relevant case entry
above?
> + if (mask == IIO_CHAN_INFO_RAW && chan->address == AXP288_GP_ADC_H)
> + ret = regmap_write(info->regmap, AXP288_ADC_TS_PIN_CTRL,
> + AXP288_ADC_TS_PIN_ON);
> +
> + mutex_unlock(&indio_dev->mlock);
> +
> + return ret;
> +}
> +
> +static int axp288_adc_enable(struct regmap *regmap, bool enable)
It's fussy, but axp288_adc_set_state or similar would be slightly
less confusing as enable with a parameter of false, just means
don't enable, not disable as i would imagine you intend...
> +{
> + unsigned int pin_on, adc_en;
> +
> + if (enable) {
> + pin_on = AXP288_ADC_TS_PIN_ON;
> + adc_en = AXP288_ADC_EN_MASK;
> + } else {
> + pin_on = ~AXP288_ADC_TS_PIN_ON;
> + adc_en = ~AXP288_ADC_EN_MASK;
> + }
> + if (regmap_write(regmap, AXP288_ADC_TS_PIN_CTRL, pin_on))
> + return -EIO;
> +
> + return regmap_write(regmap, AXP20X_ADC_EN1, ~AXP288_ADC_EN_MASK);
> +}
> +
> +static const struct iio_info axp288_adc_iio_info = {
> + .read_raw = &axp288_adc_read_raw,
> + .driver_module = THIS_MODULE,
> +};
> +
> +static int axp288_adc_probe(struct platform_device *pdev)
> +{
> + int ret;
> + struct axp288_adc_info *info;
> + struct iio_dev *indio_dev;
> + struct axp20x_dev *axp20x = dev_get_drvdata(pdev->dev.parent);
> +
> + indio_dev = devm_iio_device_alloc(&pdev->dev, sizeof(*info));
> + if (!indio_dev)
> + return -ENOMEM;
> +
> + info = iio_priv(indio_dev);
> + info->irq = platform_get_irq(pdev, 0);
> + if (info->irq < 0) {
> + dev_err(&pdev->dev, "no irq resource?\n");
> + return info->irq;
> + }
> + platform_set_drvdata(pdev, indio_dev);
> + info->regmap = axp20x->regmap;
> + ret = axp288_adc_enable(axp20x->regmap, true);
> + if (ret) {
> + dev_err(&pdev->dev, "Unable to enable ADC device\n");
> + return ret;
> + }
> +
> + indio_dev->dev.parent = &pdev->dev;
> + indio_dev->name = pdev->name;
> + indio_dev->channels = axp288_adc_channels;
> + indio_dev->num_channels = ARRAY_SIZE(axp288_adc_channels);
> + indio_dev->info = &axp288_adc_iio_info;
> + indio_dev->modes = INDIO_DIRECT_MODE;
> + ret = iio_map_array_register(indio_dev, axp288_adc_default_maps);
> + if (ret < 0)
> + goto err_disable_dev;
> +
> + ret = iio_device_register(indio_dev);
> + if (ret < 0) {
> + dev_err(&pdev->dev, "unable to register iio device\n");
> + goto err_array_unregister;
> + }
> +
> + return 0;
> +
> +err_array_unregister:
> + iio_map_array_unregister(indio_dev);
> +err_disable_dev:
> + ret = axp288_adc_enable(axp20x->regmap, false);
> +
> + return ret;
> +}
> +
> +static int axp288_adc_remove(struct platform_device *pdev)
> +{
> + struct iio_dev *indio_dev = platform_get_drvdata(pdev);
> + struct axp20x_dev *axp20x = dev_get_drvdata(pdev->dev.parent);
Would feel a little more consistent to get the regmap from info->regmap,
but doesn't really matter I suppose...
> +
> + if (axp288_adc_enable(axp20x->regmap, false))
> + dev_err(&pdev->dev, "Unable to disable ADC device\n");
> + iio_device_unregister(indio_dev);
> + iio_map_array_unregister(indio_dev);
> +
> + return 0;
> +}
> +
> +static struct platform_driver axp288_adc_driver = {
> + .probe = axp288_adc_probe,
> + .remove = axp288_adc_remove,
> + .driver = {
> + .name = "axp288_adc",
> + .owner = THIS_MODULE,
> + },
> +};
> +
> +module_platform_driver(axp288_adc_driver);
> +
> +MODULE_AUTHOR("Jacob Pan <jacob.jun.pan@linux.intel.com>");
> +MODULE_DESCRIPTION("X-Powers AXP288 ADC Driver");
> +MODULE_LICENSE("GPL");
>
next prev parent reply other threads:[~2014-09-21 13:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 0:11 [PATCH v4 0/3] Initial support for XPowers AXP288 PMIC Jacob Pan
2014-09-17 0:11 ` [PATCH v4 1/3] mfd/axp20x: extend axp20x to support axp288 pmic Jacob Pan
2014-09-18 5:39 ` Lee Jones
2014-09-18 12:32 ` Jacob Pan
2014-09-24 11:02 ` Lee Jones
2014-09-24 13:46 ` Jacob Pan
2014-09-21 13:01 ` Jonathan Cameron
2014-09-17 0:11 ` [PATCH v4 2/3] iio/adc: add support for axp288 adc Jacob Pan
2014-09-17 22:20 ` Hartmut Knaack
2014-09-17 22:30 ` Hartmut Knaack
2014-09-17 23:13 ` Jacob Pan
2014-09-18 21:52 ` Hartmut Knaack
2014-09-18 22:35 ` Jacob Pan
2014-09-21 13:14 ` Jonathan Cameron [this message]
2014-09-22 17:46 ` Jacob Pan
2014-09-17 0:11 ` [PATCH v4 3/3] iio: add documentation for current attribute Jacob Pan
2014-09-21 13:03 ` Jonathan Cameron
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=541ECF29.8060006@kernel.org \
--to=jic23@kernel.org \
--cc=B38611@freescale.com \
--cc=aaron.lu@intel.com \
--cc=alan@linux.intel.com \
--cc=angelo.compagnucci@gmail.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=carlo@caione.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=johannes.thumshirn@men.de \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=pmeerw@pmeerw.net \
--cc=rafael.j.wysocki@intel.com \
--cc=ramakrishna.pallala@intel.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.com \
--cc=sre@debian.org \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=tremyfr@yahoo.fr \
--cc=zubair.lutfullah@gmail.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).