From: Lee Jones <lee.jones@linaro.org>
To: Keerthy <j-keerthy@ti.com>
Cc: rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ijc+devicetree@hellion.org.uk, rob@landley.net,
sameo@linux.intel.com, grant.likely@linaro.org,
lgirdwood@gmail.com, broonie@kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/4] MFD: TPS65218: Add driver for the TPS65218 PMIC
Date: Tue, 3 Dec 2013 09:24:10 +0000 [thread overview]
Message-ID: <20131203092410.GD11828@lee--X1> (raw)
In-Reply-To: <1386053006-6480-3-git-send-email-j-keerthy@ti.com>
> The TPS65218 chip is a power management IC for Portable Navigation Systems
> and Tablet Computing devices. It contains the following components:
>
> - Regulators.
> - Over Temperature warning and Shut down.
>
> This patch adds support for tps65218 mfd device. At this time only
> the regulator functionality is made available.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
> drivers/mfd/Kconfig | 14 ++
> drivers/mfd/Makefile | 1 +
> drivers/mfd/tps65218.c | 281 +++++++++++++++++++++++++++++++++++++++++
> include/linux/mfd/tps65218.h | 288 ++++++++++++++++++++++++++++++++++++++++++
<snip>
> +config MFD_TPS65218
> + tristate "TI TPS65218 Power Management chips"
> + depends on I2C
> + select MFD_CORE
> + select REGMAP_I2C
> + help
> + If you say yes here you get support for the TPS65218 series of
> + Power Management chips.
> + These include voltage regulators, gpio and other features
> + that are often used in portable devices.
Perhaps you should add a note that only the regulator component is
currently supported.
<snip>
> new file mode 100644
> index 0000000..8c61640
> --- /dev/null
> +++ b/drivers/mfd/tps65218.c
> @@ -0,0 +1,281 @@
> +/*
> + * TPS65218 chip family multi-function driver
Instead of calling it an MFD driver (is there such a thing?) I think
you should mention its true purpose, as per the datasheet.
<snip>
> +static const struct of_device_id of_tps65218_match_table[] = {
> + { .compatible = "ti,tps65218", },
> + { /* end */ }
I think the end comment is superfluous.
However, if you _really_ want to put something in there, I dislike
"/* Sentinel */" the least.
> +static int tps65218_probe(struct i2c_client *client,
> + const struct i2c_device_id *ids)
> +{
<snip>
> + ret = of_platform_populate(client->dev.of_node, NULL, NULL,
> + &client->dev);
What are you trying to do here?
Register each regulator as a platform device?
<snip>
> +static const struct i2c_device_id tps65218_id_table[] = {
> + {"tps65218", TPS65218},
> +};
This has a different structure to of_tps65218_match_table, please
ensure they're the same. I prefer spaces after '{' and before '}'.
<snip>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: Keerthy <j-keerthy@ti.com>
Cc: rob.herring@calxeda.com, pawel.moll@arm.com,
mark.rutland@arm.com, swarren@wwwdotorg.org,
ijc+devicetree@hellion.org.uk, rob@landley.net,
sameo@linux.intel.com, grant.likely@linaro.org,
lgirdwood@gmail.com, broonie@kernel.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 2/4] MFD: TPS65218: Add driver for the TPS65218 PMIC
Date: Tue, 3 Dec 2013 09:24:10 +0000 [thread overview]
Message-ID: <20131203092410.GD11828@lee--X1> (raw)
In-Reply-To: <1386053006-6480-3-git-send-email-j-keerthy@ti.com>
> The TPS65218 chip is a power management IC for Portable Navigation Systems
> and Tablet Computing devices. It contains the following components:
>
> - Regulators.
> - Over Temperature warning and Shut down.
>
> This patch adds support for tps65218 mfd device. At this time only
> the regulator functionality is made available.
>
> Signed-off-by: Keerthy <j-keerthy@ti.com>
> ---
> drivers/mfd/Kconfig | 14 ++
> drivers/mfd/Makefile | 1 +
> drivers/mfd/tps65218.c | 281 +++++++++++++++++++++++++++++++++++++++++
> include/linux/mfd/tps65218.h | 288 ++++++++++++++++++++++++++++++++++++++++++
<snip>
> +config MFD_TPS65218
> + tristate "TI TPS65218 Power Management chips"
> + depends on I2C
> + select MFD_CORE
> + select REGMAP_I2C
> + help
> + If you say yes here you get support for the TPS65218 series of
> + Power Management chips.
> + These include voltage regulators, gpio and other features
> + that are often used in portable devices.
Perhaps you should add a note that only the regulator component is
currently supported.
<snip>
> new file mode 100644
> index 0000000..8c61640
> --- /dev/null
> +++ b/drivers/mfd/tps65218.c
> @@ -0,0 +1,281 @@
> +/*
> + * TPS65218 chip family multi-function driver
Instead of calling it an MFD driver (is there such a thing?) I think
you should mention its true purpose, as per the datasheet.
<snip>
> +static const struct of_device_id of_tps65218_match_table[] = {
> + { .compatible = "ti,tps65218", },
> + { /* end */ }
I think the end comment is superfluous.
However, if you _really_ want to put something in there, I dislike
"/* Sentinel */" the least.
> +static int tps65218_probe(struct i2c_client *client,
> + const struct i2c_device_id *ids)
> +{
<snip>
> + ret = of_platform_populate(client->dev.of_node, NULL, NULL,
> + &client->dev);
What are you trying to do here?
Register each regulator as a platform device?
<snip>
> +static const struct i2c_device_id tps65218_id_table[] = {
> + {"tps65218", TPS65218},
> +};
This has a different structure to of_tps65218_match_table, please
ensure they're the same. I prefer spaces after '{' and before '}'.
<snip>
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2013-12-03 9:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 6:43 [PATCH 0/4] mfd: TPS65218: Add support for TPS65218 PMIC Keerthy
2013-12-03 6:43 ` Keerthy
2013-12-03 6:43 ` [PATCH 1/4] mfd: DT bindings " Keerthy
2013-12-03 6:43 ` Keerthy
2013-12-03 9:36 ` Lee Jones
2013-12-03 10:52 ` Keerthy
2013-12-03 10:52 ` Keerthy
2013-12-03 11:04 ` Lee Jones
2013-12-03 11:04 ` Lee Jones
2013-12-03 6:43 ` [PATCH 2/4] MFD: TPS65218: Add driver for the " Keerthy
2013-12-03 6:43 ` Keerthy
2013-12-03 9:24 ` Lee Jones [this message]
2013-12-03 9:24 ` Lee Jones
2013-12-03 10:06 ` Keerthy
2013-12-03 10:06 ` Keerthy
2013-12-03 11:21 ` Lee Jones
2013-12-03 11:21 ` Lee Jones
2013-12-03 13:28 ` Mark Brown
2013-12-03 15:19 ` Mark Brown
2013-12-03 6:43 ` [PATCH 3/4] Regulators: TPS65218: Add Regulator driver for " Keerthy
2013-12-03 6:43 ` Keerthy
2013-12-03 15:16 ` Mark Brown
[not found] ` <20131203151654.GB27568-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2013-12-04 5:59 ` Keerthy
2013-12-04 5:59 ` Keerthy
2013-12-04 7:39 ` Manish Badarkhe
2013-12-03 6:43 ` [PATCH 4/4] ARM: dts: AM437x: Add TPS65218 device tree nodes Keerthy
2013-12-03 6:43 ` Keerthy
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=20131203092410.GD11828@lee--X1 \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=j-keerthy@ti.com \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.