public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Keerthy <a0393675@ti.com>
Cc: Keerthy <j-keerthy@ti.com>,
	devicetree@vger.kernel.org, robh+dt@kernel.org,
	mark.rutland@arm.com, sameo@linux.intel.com,
	grant.likely@linaro.org, ian@slimlogic.co.uk,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	broonie@linaro.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 3/4] mfd: tps65917: Add driver for the TPS65917 PMIC
Date: Fri, 23 May 2014 11:06:34 +0100	[thread overview]
Message-ID: <20140523100634.GP19747@lee--X1> (raw)
In-Reply-To: <537EBEE4.9050309@ti.com>

> >>>>The TPS65917 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 tps65917 mfd device. At this time only
> >>>>the regulator functionality is made available.
> >>>>
> >>>>Signed-off-by: Keerthy <j-keerthy@ti.com>
> >>>>---
> >>>>v3 Changes:
> >>>>
> >>>>  * Header file formating
> >>>>  * Changed the cache_type to REGCACHE_RBTREE
> >>>>  * removed unnecessary code
> >>>>  * Corrected documentation style
> >>>>  * Added pm_power_off function
> >>>>
> >>>>  v2 Changes:
> >>>>
> >>>>  * Added volatile register check as some of the registers
> >>>>    in the set are volatile.
> >>>>drivers/mfd/Kconfig          |   12 +
> >>>>  drivers/mfd/Makefile         |    1 +
> >>>>  drivers/mfd/tps65917.c       |  594 +++++++++++++++++
> >>>>  include/linux/mfd/tps65917.h | 1485 ++++++++++++++++++++++++++++++++++++++++++
> >>>>  4 files changed, 2092 insertions(+)
> >>>>  create mode 100644 drivers/mfd/tps65917.c
> >>>>  create mode 100644 include/linux/mfd/tps65917.h

[...]

> >>>>+		ret = regmap_read(tps65917->regmap[slave], addr, &reg);
> >>>>+		if (ret)
> >>>>+			goto err_irq;
> >>>>+	}i
> >>>What does the read do?  You're not doing anything with the value.
> >>This pad1 and pad2 stuff is not needed. I will remove this.
> >Then why is it in here?
> >
> >Did you copy this code from somewhere, if so, where?
> >
> >Okay, I just answered my own question.  There is so much common code
> >in between this and palmas, there is no way I'm going to accept this
> >driver.  Please merge it in with the palmas driver!
> >
> The chip is more like a subset of palmas with lot of register offset changes
> and register bit field changes. Adding this would make it clumsy.
> There could
> be lot of checks. That is why i chose to write a new driver.
> 
> Palmas driver already supports palmas variants and tps659038. Merging
> this would mean more and more checks :-/.

Then find an elegant way of representing the variants.  I'm not
prepared to carry that much duplicated code in MFD.  It's already
overladened and in need of an overhaul.  This will exacerbate the
matter.

-- 
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2014-05-23 10:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-22  4:00 [PATCH v3 0/4] tps65917: Drivers for TPS65917 PMIC Keerthy
2014-05-22  4:00 ` [PATCH v3 1/4] MFD: DT bindings for the TPS65917 family MFD Keerthy
2014-05-22  4:00 ` [PATCH v3 2/4] Regulators: Add TPS65917 Bindings Keerthy
2014-05-22  4:00 ` [PATCH v3 3/4] mfd: tps65917: Add driver for the TPS65917 PMIC Keerthy
2014-05-22  8:37   ` Lee Jones
2014-05-22 10:57     ` Keerthy
2014-05-22 11:48       ` Lee Jones
2014-05-23  3:22         ` Keerthy
2014-05-23 10:06           ` Lee Jones [this message]
2014-05-23 10:59             ` Keerthy
2014-05-23 11:18               ` Lee Jones
2014-05-22  4:00 ` [PATCH v3 4/4] regulator: tps65917: Add Regulator driver for " 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=20140523100634.GP19747@lee--X1 \
    --to=lee.jones@linaro.org \
    --cc=a0393675@ti.com \
    --cc=broonie@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=grant.likely@linaro.org \
    --cc=ian@slimlogic.co.uk \
    --cc=j-keerthy@ti.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=robh+dt@kernel.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