From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Margarita Olaya <magi@slimlogic.co.uk>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lrg@slimlogic.co.uk>,
sameo@linux.intel.com
Subject: Re: [PATCH 1/4] mfd: tps65912: Add new mfd device
Date: Tue, 10 May 2011 22:34:32 +0200 [thread overview]
Message-ID: <20110510203432.GA8726@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <BANLkTimAohO2svuYGcfjfNzh4Yib2o0Y7g@mail.gmail.com>
On Tue, May 10, 2011 at 03:25:23PM -0500, Margarita Olaya wrote:
> +config MFD_TPS65912
> + bool "TPS95612 Power Management chip"
> + select MFD_CORE
> + depends on I2C && GPIOLIB
> + help
> + If you say yes here you get support for the TPS65912 series of
> + PM chips.
> +
There's a whole bunch of optional SPI code in the driver so either the
dependency is wrong or the code doesn't do anything. It's generally
better to split the buses if you've got both SPI and I2C as PMICs pretty
much have to be built in and this will force both buses to be built in,
though it's not really *too* big a deal.
> +++ b/drivers/mfd/Makefile
> @@ -31,6 +31,7 @@ wm8350-objs += wm8350-irq.o
> obj-$(CONFIG_MFD_WM8350) += wm8350.o
> obj-$(CONFIG_MFD_WM8350_I2C) += wm8350-i2c.o
> obj-$(CONFIG_MFD_WM8994) += wm8994-core.o wm8994-irq.o
> +obj-$(CONFIG_MFD_TPS65912) += tps65912.o
>
> obj-$(CONFIG_TPS6105X) += tps6105x.o
> obj-$(CONFIG_TPS65010) += tps65010.o
Seems nicer to sort this with the other tps drivers?
> + tx_buf = spi_data;
> + rx_buf = 0;
> + xfer.speed_hz = spi->max_speed_hz;
The default max_speed_hz from the driver should be used if you don't do
anything so this isn't needed.
> +#define GPIO1_R_IT_SHIFT 6
> +#define HOTDIE_IT_MASK 0x20
> +#define HOTDIE_IT_SHIFT 5
> +#define PWRHOLD_R_IT_MASK 0x10
> +#define PWRHOLD_R_IT_SHIFT 4
> +#define PWRON_LP_IT_MASK 0x08
> +#define PWRON_LP_IT_SHIFT 3
> +#define PWRON_IT_MASK 0x04
> +#define PWRON_IT_SHIFT 2
> +#define VMON_IT_MASK 0x02
> +#define VMON_IT_SHIFT 1
> +#define PWRHOLD_F_IT_MAKS 0x01
> +#define PWRHOLD_F_IT_SHIFT 0
Most of the identifiers in the header look like they ought to be
namespaced.
prev parent reply other threads:[~2011-05-10 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 20:25 [PATCH 1/4] mfd: tps65912: Add new mfd device Margarita Olaya
2011-05-10 20:34 ` 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=20110510203432.GA8726@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--cc=magi@slimlogic.co.uk \
--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