All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Regulator enable/disable delay based on board design: How to handle?
Date: Mon, 13 Feb 2012 17:09:47 -0800	[thread overview]
Message-ID: <20120214010946.GE11931@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F394F28.70709@nvidia.com>

[-- Attachment #1: Type: text/plain, Size: 883 bytes --]

On Mon, Feb 13, 2012 at 11:28:00PM +0530, Laxman Dewangan wrote:

> Interesting, Many regulator driver is written like it just take the
> regulator_init_data as the platform data and does not leave any
> option to add any new platform parameters.
> Not sure how can we add platform data without too much tempering on
> the existing user, but if we can add parameter of delay(settling
> time) in struct regulator_init_data then almost all driver can
> support such platform specific delay.

This is part of the reason why the driver_data field is present in the
constraints - the driver can take that and use it as a pdata within
pdata structure.  It's not terribly nice to do that but it's possible.
A standard parameter might cause too much complexity as drivers try to
implement it even if they don't really need to (for example, due to
having soft control of this stuff already).

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-02-14  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13  9:18 Regulator enable/disable delay based on board design: How to handle? Laxman Dewangan
2012-02-13 16:37 ` Mark Brown
2012-02-13 17:58   ` Laxman Dewangan
2012-02-14  1:09     ` Mark Brown [this message]
2012-02-14 11:23       ` Laxman Dewangan

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=20120214010946.GE11931@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=ldewangan@nvidia.com \
    --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 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.