All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laxman Dewangan <ldewangan@nvidia.com>
To: Axel Lin <axel.lin@gmail.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Graeme Gregory <gg@slimlogic.co.uk>, Liam Girdwood <lrg@ti.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	SamuelOrtiz <sameo@linux.intel.com>,
	Venu Byravarasu <vbyravarasu@nvidia.com>
Subject: Re: [PATCH RFT] regulator: tps65910: Remvoe tps65910_reg_[read|modify_bits|read_locked|write_locked] functions
Date: Thu, 12 Jul 2012 15:20:10 +0530	[thread overview]
Message-ID: <4FFE9DD2.9070404@nvidia.com> (raw)
In-Reply-To: <1342007053.4362.2.camel@phoenix>

On Wednesday 11 July 2012 05:14 PM, Axel Lin wrote:
> The tps65910 mfd driver has been converted to regmap APIs.
> This patch adds tps65910_reg_update_bits() in include/linux/mfd/tps65910.h.
> Thus we can use tps65910_reg_read/tps65910_reg_write/tps65910_reg_update_bits
> directly and remove tps65910_reg_[read|modify_bits|read_locked|write_locked]
> functions. With this change, we can also remove the mutex in struct tps65910_reg.
>
> Signed-off-by: Axel Lin<axel.lin@gmail.com>
> ---

Tested-by: Laxman Dewangan <ldewangan@nvidia.com>

Venu,
I think your RTC driver development may need some of change from here.

Thanks,
Laxman


  reply	other threads:[~2012-07-12  9:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-11 11:44 [PATCH RFT] regulator: tps65910: Remvoe tps65910_reg_[read|modify_bits|read_locked|write_locked] functions Axel Lin
2012-07-12  9:50 ` Laxman Dewangan [this message]
2012-07-12 17:07 ` Mark Brown

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=4FFE9DD2.9070404@nvidia.com \
    --to=ldewangan@nvidia.com \
    --cc=axel.lin@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=gg@slimlogic.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=sameo@linux.intel.com \
    --cc=vbyravarasu@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.