Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: a0393675@ti.com (Keerthy)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v7 0/5] mfd: tps65218: Clean ups
Date: Fri, 16 Sep 2016 17:12:38 +0530	[thread overview]
Message-ID: <ab94aff0-8470-57e5-2039-12f09bb0ca33@ti.com> (raw)
In-Reply-To: <1470833641-29546-1-git-send-email-j-keerthy@ti.com>



On Wednesday 10 August 2016 06:24 PM, Keerthy wrote:
> The series cleans up mainly the regulator driver and implements
> the device tree parsing using the regulator framework. Removes
> all the redundant compatibles for the individual regulators.
> Adds platform_device_id table for the gpio and power button modules.
>
> One of the patch removes redundant read wrapper and makes
> use of regmap_read wherever necessary.

Mark,

Should i repost this series? I do not see this series in linux-next yet.

Regards,
Keerthy
>
> The series is checked for all the regulator registrations on
> am437x-gp-evm.
>
> Boot log: http://pastebin.ubuntu.com/22905402/
>
> The series is based on linux-next on top of series titled:
> [PATCH v3 0/2] regulator: Enable suspend configuration
>
> Do not have the link of the above series available at the moment.
>
> Changes in v7:
>
> Rebasing to latest next branch. GPIO patch of this series
> pushed to linux-next by Linus. Hence posting the remaining
> patches with respective Acks from the domain Maintainers.
>
> Changes in v6:
>
> Rebased regulator/mfd clean up patches against linux-next +
> https://lkml.org/lkml/2016/6/24/122 series.
>
> Changes in v5:
>
> Rebased regulator clean up patch against linux-next.
>
> Changes in v4:
>
> For gpio-tps65218 reatined the compatible table.
> Fixed missing ';' in the power button patch.
> Fixed comments on the Documentation patch.
> Split the Device Tree patches to a separate series.
>
> Changes in v3:
>
> Missed making corresponding changes in the power button and gpio
> drivers. Added couple of patches to fix them to use mfd_cell way
> of parsing.
>
> Keerthy (5):
>   mfd: tps65218: Remove redundant read wrapper
>   Documentation: regulator: tps65218: Update examples
>   input: tps65218-pwrbutton: Add platform_device_id table
>   mfd: tps65218: Use mfd_add_devices instead of of_platform_populate
>   regulator: tps65218: Remove all the compatibles
>
>  .../devicetree/bindings/regulator/tps65218.txt     |  87 +++++++++---
>  drivers/gpio/gpio-tps65218.c                       |   3 +-
>  drivers/input/misc/tps65218-pwrbutton.c            |  10 +-
>  drivers/mfd/tps65218.c                             |  34 ++---
>  drivers/regulator/tps65218-regulator.c             | 153 ++++++++-------------
>  include/linux/mfd/tps65218.h                       |   3 +-
>  6 files changed, 158 insertions(+), 132 deletions(-)
>

  reply	other threads:[~2016-09-16 11:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 12:54 [PATCH v7 0/5] mfd: tps65218: Clean ups Keerthy
2016-09-16 11:42 ` Keerthy [this message]
2016-09-16 13:31   ` Mark Brown
2016-09-16 16:21     ` Keerthy
2016-09-16 17:36       ` Mark Brown
2016-09-17  3:53         ` 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=ab94aff0-8470-57e5-2039-12f09bb0ca33@ti.com \
    --to=a0393675@ti.com \
    --cc=linux-arm-kernel@lists.infradead.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