linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
	Kyungmin Park <kyungmin.park@samsung.com>,
	Liam Girdwood <lrg@ti.com>, Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH v3] regulator: treat regulators with constant volatage as fixed
Date: Wed, 14 Nov 2012 11:01:25 +0900	[thread overview]
Message-ID: <20121114020124.GH4415@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1352800177-16139-1-git-send-email-m.szyprowski@samsung.com>

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

On Tue, Nov 13, 2012 at 10:49:37AM +0100, Marek Szyprowski wrote:

> +	if (rdev->constraints->valid_ops_mask & REGULATOR_CHANGE_VOLTAGE) {
> +		if (rdev->desc->n_voltages)
> +			return rdev->desc->n_voltages;
> +		else
> +			return -EINVAL;
> +	} else {
> +		return 1;
> +	}

Hrm, now I can read the logic I'm not convinced this is a good idea.
This will report that we have an available voltage for devices which
don't know their voltage (things like battery supplies often do this as
the voltage is unregulated) and it will mean that we are doing something 
different for the case where there's only one voltage (reporting the
restricted count instead of the physically supported count).

I think we want a regulator_can_change_voltage() or possibly a count
function (though I can't see any use cases except this) which answers
the question directly instead of layering on top of this function.

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

  reply	other threads:[~2012-11-14  2:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13  8:48 [PATCH 0/3] Fix fixed regulators support Marek Szyprowski
2012-11-13  8:48 ` [PATCH 1/3] regulator: fix voltage check in regulator_is_supported_voltage() Marek Szyprowski
2012-11-13  9:01   ` Mark Brown
2012-11-13  8:48 ` [PATCH 2/3] regulator: threat regulators with constant volatage as fixed Marek Szyprowski
2012-11-13  9:00   ` Mark Brown
2012-11-13  9:35     ` [PATCH v2] regulator: treat " Marek Szyprowski
2012-11-13  9:42       ` Mark Brown
2012-11-13  9:49         ` [PATCH v3] " Marek Szyprowski
2012-11-14  2:01           ` Mark Brown [this message]
2012-11-20 13:20             ` Marek Szyprowski
2012-11-13  8:48 ` [PATCH 3/3] mmc: sdhci: apply voltage range check only for non-fixed regulators Marek Szyprowski
2012-11-13 12:45   ` Chris Ball
2012-11-13 13:32     ` [PATCH v2] " Marek Szyprowski
2012-11-13 13:45       ` Chris Ball
2012-11-13 14:09         ` Marek Szyprowski
2012-11-13 14:14           ` Chris Ball
2012-11-13 21:23             ` Philip Rakity
2012-11-20  8:42               ` Marek Szyprowski
2012-11-14  1:10     ` [PATCH 3/3] " 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=20121114020124.GH4415@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=cjb@laptop.org \
    --cc=kyungmin.park@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=m.szyprowski@samsung.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;
as well as URLs for NNTP newsgroup(s).