From: Graeme Gregory <gg@slimlogic.co.uk>
To: Kyle Manna <kyle.manna@fuel7.com>
Cc: linux-kernel@vger.kernel.org,
Samuel Ortiz <sameo@linux.intel.com>, Liam Girdwood <lrg@ti.com>,
Jorge Eduardo Candelaria <jedu@slimlogic.co.uk>
Subject: Re: [PATCH 0/6] mfd: TPS65910 bug fixes and enhancements
Date: Tue, 18 Oct 2011 19:42:23 +0100 [thread overview]
Message-ID: <4E9DC88F.4070803@slimlogic.co.uk> (raw)
In-Reply-To: <1318962388-26151-1-git-send-email-kyle.manna@fuel7.com>
On 18/10/11 19:26, Kyle Manna wrote:
> This series of patches fixes a number of small problems with the TPS65910 that
> were discovered on a custom board.
>
> Additionally, the last patch enhances the platform to driver interface using the
> TWL4030 series of regulators as an example.
>
> Kyle Manna (6):
> mfd: TPS65910: Handle non-existent devices
> mfd: TPS65910: Add I2C slave address macros
> mfd: TPS65910: Fix typo that clobbers genirq
> mfd: TPS65910: Move linux/gpio.h include to header
> mfd: TPS65910: Fix tps65910_set_voltage
> mfd: TPS65910: Improve regulator init data
>
> drivers/mfd/tps65910.c | 23 ++-
> drivers/regulator/tps65910-regulator.c | 246 +++++++++++++++++++++++++-------
> include/linux/mfd/tps65910.h | 36 +++++-
> 3 files changed, 247 insertions(+), 58 deletions(-)
>
In my opinion patches 5 and 6 are regressions.
set_voltage_sel was added to core api to allow the voltage selection
code that a lot of drivers implemented identically to be abstracted to
the regulator core.
The twl4030 driver method of defining platform data has left us with a
very inflexible way of adding functionality when a new variant of the
chip is released. This was remarked on by a number of kernel developers
when I upstreamed the twl6025 support. I feel copying the twl driver is
the wrong direction to go in in this regard.
Graeme
prev parent reply other threads:[~2011-10-18 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 18:26 Kyle Manna
2011-10-18 18:26 ` [PATCH 1/6] mfd: TPS65910: Handle non-existent devices Kyle Manna
2011-10-18 18:26 ` [PATCH 2/6] mfd: TPS65910: Add I2C slave address macros Kyle Manna
2011-10-18 18:26 ` [PATCH 3/6] mfd: TPS65910: Fix typo that clobbers genirq Kyle Manna
2011-10-18 18:26 ` [PATCH 4/6] mfd: TPS65910: Move linux/gpio.h include to header Kyle Manna
2011-10-18 18:26 ` [PATCH 5/6] mfd: TPS65910: Fix tps65910_set_voltage Kyle Manna
2011-10-19 13:32 ` Mark Brown
2011-10-20 15:21 ` Kyle Manna
2011-10-18 18:26 ` [PATCH 6/6] mfd: TPS65910: Improve regulator init data Kyle Manna
2011-10-19 14:00 ` Mark Brown
2011-10-24 16:13 ` Kyle Manna
2011-10-18 18:42 ` Graeme Gregory [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=4E9DC88F.4070803@slimlogic.co.uk \
--to=gg@slimlogic.co.uk \
--cc=jedu@slimlogic.co.uk \
--cc=kyle.manna@fuel7.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--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
Powered by JetHome