mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Philipp Zabel <p.zabel@pengutronix.de>
Cc: linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>,
	kernel@pengutronix.de, support.opensource@diasemi.com
Subject: Re: [PATCH] regulator: da9063: Add set_voltage_time_sel function
Date: Thu, 6 Aug 2015 19:33:22 +0100	[thread overview]
Message-ID: <20150806183322.GF20873@sirena.org.uk> (raw)
In-Reply-To: <1438879104-13081-1-git-send-email-p.zabel@pengutronix.de>

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

On Thu, Aug 06, 2015 at 06:38:24PM +0200, Philipp Zabel wrote:
> This allows to set the regulator-ramp-delay in the device tree.

> @@ -433,6 +433,7 @@ static struct regulator_ops da9063_buck_ops = {
>  	.is_enabled		= regulator_is_enabled_regmap,
>  	.get_voltage_sel	= regulator_get_voltage_sel_regmap,
>  	.set_voltage_sel	= regulator_set_voltage_sel_regmap,
> +	.set_voltage_time_sel	= regulator_set_voltage_time_sel,
>  	.list_voltage		= regulator_list_voltage_linear,
>  	.set_current_limit	= da9063_set_current_limit,
>  	.get_current_limit	= da9063_get_current_limit,

This doesn't seem right - we shouldn't need to manually add this to
every device to get the generic property to work.  Instead we ought to
just do this by default if there's nothing defined in the driver and we
see that a value was provided by DT.

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

  reply	other threads:[~2015-08-06 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06 16:38 Philipp Zabel
2015-08-06 18:33 ` Mark Brown [this message]
2015-08-07  9:29   ` Philipp Zabel
2015-08-07 12:31     ` Mark Brown
2015-08-07 13:21       ` Philipp Zabel
2015-08-07 13:29         ` Mark Brown
2015-08-07 13:36           ` Philipp Zabel

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=20150806183322.GF20873@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=support.opensource@diasemi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®