public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Samuel Ortiz <sameo@openedhand.com>
To: Balaji Rao <balajirrao@openmoko.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 0/7] PCF50633 support
Date: Mon, 22 Dec 2008 11:50:45 +0100	[thread overview]
Message-ID: <20081222105044.GC2633@sortiz.org> (raw)
In-Reply-To: <20081218055618.31696.65002.stgit@cff.thadambail>

Hi Balaji,

On Thu, Dec 18, 2008 at 11:26:18AM +0530, Balaji Rao wrote:
> Changes from V1:
> 	- Subdevice specific header files now included in its respective patch.
> 	- Introduces pcf50633_register_irq and pcf50633_free_irq for irq
> 	  management
> 	- Many changes in how subdevices are created and information is passed
> 	  to them. Thanks to Alessandro Zummo for suggestions.
> 
> The following series implements support for NXP PCF50633. It's basically
> an I2C device with 9 regulators, an ADC, a PMIC, a Battery Charger
> and a RTC.
> 
> This chip is used in Openmoko Neo Freerunner mobile phone.
> 
> Driver for a similar chip PCF50606, used in Openmoko Neo 1973 device
> will follow soon.
> 
> The specs are open and are available at 
> http://people.openmoko.org/tony_tu/GTA02/datasheet/PMU/PCF50633DS_02.pdf
> 
> Samuel, are you ok with merging this via linux-mfd tree ?
Yes, I'm fine with it. Two things though:
- Could you please resend the non-mfd parts (patch 4,5,6 and 7) to me ?
- I see from the lkml archives that patches 5 and 6 didnt get Acked yet. I'll
queue them, but I'd really like to get Anton and Dmitry approval before
sending them upstream.

Cheers,
Samuel.


> 
> ---
> Balaji Rao (7):
>       mfd: PCF50633 core driver
>       mfd: PCF50633 adc driver
>       mfd: PCF50633 gpio support
>       rtc: PCF50633 rtc driver
>       power_supply: PCF50633 battery charger driver
>       input: PCF50633 input driver
>       regulator: PCF50633 pmic driver
> 
>  drivers/input/misc/Kconfig             |    7 
>  drivers/input/misc/Makefile            |    1 
>  drivers/input/misc/pcf50633-input.c    |  132 ++++++
>  drivers/mfd/Kconfig                    |   23 +
>  drivers/mfd/Makefile                   |    6 
>  drivers/mfd/pcf50633-adc.c             |  277 +++++++++++++
>  drivers/mfd/pcf50633-core.c            |  707 ++++++++++++++++++++++++++++++++
>  drivers/mfd/pcf50633-gpio.c            |  118 +++++
>  drivers/power/Kconfig                  |    6 
>  drivers/power/Makefile                 |    2 
>  drivers/power/pcf50633-charger.c       |  358 ++++++++++++++++
>  drivers/regulator/Kconfig              |    7 
>  drivers/regulator/Makefile             |    1 
>  drivers/regulator/pcf50633-regulator.c |  330 +++++++++++++++
>  drivers/rtc/Kconfig                    |    6 
>  drivers/rtc/Makefile                   |    1 
>  drivers/rtc/rtc-pcf50633.c             |  336 +++++++++++++++
>  include/linux/mfd/pcf50633/adc.h       |   72 +++
>  include/linux/mfd/pcf50633/core.h      |  218 ++++++++++
>  include/linux/mfd/pcf50633/gpio.h      |   52 ++
>  include/linux/mfd/pcf50633/mbc.h       |  134 ++++++
>  include/linux/mfd/pcf50633/pmic.h      |   68 +++
>  22 files changed, 2861 insertions(+), 1 deletions(-)
>  create mode 100644 drivers/input/misc/pcf50633-input.c
>  create mode 100644 drivers/mfd/pcf50633-adc.c
>  create mode 100644 drivers/mfd/pcf50633-core.c
>  create mode 100644 drivers/mfd/pcf50633-gpio.c
>  create mode 100644 drivers/power/pcf50633-charger.c
>  create mode 100644 drivers/regulator/pcf50633-regulator.c
>  create mode 100644 drivers/rtc/rtc-pcf50633.c
>  create mode 100644 include/linux/mfd/pcf50633/adc.h
>  create mode 100644 include/linux/mfd/pcf50633/core.h
>  create mode 100644 include/linux/mfd/pcf50633/gpio.h
>  create mode 100644 include/linux/mfd/pcf50633/mbc.h
>  create mode 100644 include/linux/mfd/pcf50633/pmic.h
> 
> 
> -- 
> Thanks,
> Balaji Rao
> 

-- 
Intel Open Source Technology Centre
http://oss.intel.com/

      parent reply	other threads:[~2008-12-22 10:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-18  5:56 [PATCH V2 0/7] PCF50633 support Balaji Rao
2008-12-18  5:56 ` [PATCH V2 1/7] mfd: PCF50633 core driver Balaji Rao
2008-12-18  5:56 ` [PATCH V2 2/7] mfd: PCF50633 adc driver Balaji Rao
2008-12-19 11:18   ` Jonathan Cameron
2008-12-19 12:05     ` Mark Brown
2008-12-19 12:47       ` Jonathan Cameron
2008-12-19 12:15     ` Andy Green
2008-12-19 12:51       ` Jonathan Cameron
2008-12-22 16:23     ` Balaji Rao
2008-12-18  5:57 ` [PATCH V2 3/7] mfd: PCF50633 gpio support Balaji Rao
2008-12-18  5:57 ` [PATCH V2 4/7] rtc: PCF50633 rtc driver Balaji Rao
2008-12-18  9:03   ` Alessandro Zummo
2008-12-18 15:11     ` Balaji Rao
2008-12-18 16:52       ` Alessandro Zummo
2008-12-18  5:57 ` [PATCH V2 5/7] power_supply: PCF50633 battery charger driver Balaji Rao
2008-12-18 20:26   ` Balaji Rao
2008-12-25 15:45   ` Anton Vorontsov
2008-12-25 18:50     ` Balaji Rao
2008-12-18  5:58 ` [PATCH V2 6/7] input: PCF50633 input driver Balaji Rao
2008-12-18  5:58 ` [PATCH V2 7/7] regulator: PCF50633 pmic driver Balaji Rao
2008-12-18 10:08   ` Mark Brown
2008-12-18 15:14     ` Balaji Rao
2008-12-18 20:30       ` Liam Girdwood
2008-12-18 20:47         ` Balaji Rao
2008-12-18 20:54           ` Liam Girdwood
2008-12-22 10:50 ` Samuel Ortiz [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=20081222105044.GC2633@sortiz.org \
    --to=sameo@openedhand.com \
    --cc=balajirrao@openmoko.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox