linux-kernel - Re: [PATCHv1 5/11] REGULATOR: Regulator module of DA9052 PMIC driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 15 Apr 2011 11:36:07 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Ashish Jangam <Ashish.Jangam@...tcummins.com>
Cc:	"lrg@...mlogic.co.uk" <lrg@...mlogic.co.uk>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	David Dajun Chen <Dajun.Chen@...semi.com>
Subject: Re: [PATCHv1 5/11] REGULATOR: Regulator module of DA9052 PMIC driver

On Wed, Apr 13, 2011 at 05:42:08PM +0530, Ashish Jangam wrote:

> Changes made since last submission:
> . Change the regulator registration method
> . Ported the driver to Linux kernel 2.6.38.2 

> Linux Kernel Version: 2.6.38.2

As I've repeatedly told you you should submit patches against -next.
Please stop doing this, it's getting repetitive.  A few comments from a
breif scan through:

> +static struct regulator_consumer_supply da9052_vddarm_consumers[] = {
> +	{
> +		.supply = "vcc",
> +	}
> +};

Supplies are connected to regulators using the machine driver not
drivers for specific regulators.

> +	if (offset == DA9052_BUCK_PERI) {
> +		if (regval >= DA9052_BUCK_PERI_REG_MAP_UPTO_3uV) {
> +			regval_uV = ((DA9052_BUCK_PERI_REG_MAP_UPTO_3uV *
> +				da9052_regulator_info[offset].step_uV)
> +				+ constraints->min_uV);
> +			regval_uV += (regval -
> +				DA9052_BUCK_PERI_REG_MAP_UPTO_3uV)
> +				*(DA9052_BUCK_PERI_3uV_STEP);
> +		} else {
> +			regval_uV =
> +				(regval * da9052_regulator_info[offset].step_uV)
> +				+ constraints->min_uV;
> +		}

Given this and the number of other differences it seems like you should
just define separate ops for BUCK_PERI.

> +static int da9052_regulator_set_voltage(struct regulator_dev *rdev, int min_uV,
> +				 int max_uV, unsigned *selector)
> +{
> +	struct da9052 *da9052 = to_da9052(rdev);
> +	int offset = rdev_get_id(rdev);
> +	int ret;
> +	int reg_val = 0;
> +
> +	reg_val = da9052_regulator_uvolts_to_regVal(rdev, min_uV);

You're completely ignoring the max_uV constraint here.

> +static int da9052_list_voltage(struct regulator_dev *rdev, unsigned selector)
> +{
> +	struct regulation_constraints *constraints = rdev->constraints;
> +	struct da9052_regulator_info *info = rdev_get_drvdata(rdev);
> +	int ret;
> +
> +	ret = constraints->min_uV + info->step_uV * selector;
> +	if (ret > constraints->max_uV)
> +		return -EINVAL;

This looks *very* broken.  Why are you looking at the constraints to
determine what the selector means?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/