lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120919170441.GQ28670@sortiz-mobl>
Date:	Wed, 19 Sep 2012 19:04:41 +0200
From:	Samuel Ortiz <sameo@...ux.intel.com>
To:	"Kim, Milo" <Milo.Kim@...com>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] mfd: add new lp8788 driver

Hi Kim,

On Fri, Sep 07, 2012 at 08:51:50AM +0000, Kim, Milo wrote:
>  TI LP8788 PMU provides regulators, battery charger, ADC,
>  RTC, backlight driver and current sinks.
> 
>  This MFD patch supports the I2C communication using the regmap,
>  the interrupt handling using the linear IRQ domain and
>  configurable platform data structures for each driver module.
> 
>  (Driver Architecture)
> 
>                                          < mfd devices >
>   LP8788 HW  ..........  mfd  .......... regulator drivers
>                 I2C                      power supply driver
>                 IRQs                     iio adc driver
>                                          rtc driver
>                                          backlight driver
>                                          current sink drivers
> 
>   o regulators    : LDOs and BUCKs
>   o power supply  : Battery charger
>   o iio adc       : Battery voltage/temperature
>   o rtc           : RTC and alarm
>   o backlight
>   o current sink  : LED and vibrator
> 
>  All MFD device modules are registered by LP8788 MFD core driver.
>  For sharing information such like the virtual IRQ number,
>  MFD core driver uses the resource structure.
>  Then each module can retrieve the specific IRQ number and detect it
>  in the IRQ thread.
> 
>  Configurable platform data is handled in each driver module.
> 
>  (History)
> 
>  Patch v4.
>  ADC platform data change : pointer array -> simple pointer
> 
>  Patch v3.
>  Use linear IRQ domain rather than old generic IRQ.
> 
>  Patch v2.
>  Use generic IRQ for interrupt handling.
>  Remove ADC exported functions. moved to new iio adc driver.
> 
> Signed-off-by: Milo(Woogyom) Kim <milo.kim@...com>
> ---
>  drivers/mfd/Kconfig              |   10 ++
>  drivers/mfd/Makefile             |    2 +
>  drivers/mfd/lp8788-irq.c         |  197 +++++++++++++++++++++
>  drivers/mfd/lp8788.c             |  245 +++++++++++++++++++++++++
>  include/linux/mfd/lp8788-isink.h |   52 ++++++
>  include/linux/mfd/lp8788.h       |  364 ++++++++++++++++++++++++++++++++++++++
>  6 files changed, 870 insertions(+)
>  create mode 100644 drivers/mfd/lp8788-irq.c
>  create mode 100644 drivers/mfd/lp8788.c
>  create mode 100644 include/linux/mfd/lp8788-isink.h
>  create mode 100644 include/linux/mfd/lp8788.h
This is applied to my for-next branch now, thanks.

Cheers,
Samuel.

-- 
Intel Open Source Technology Centre
http://oss.intel.com/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ