linux-kernel - Re: [PATCH 1/2] mfd: bq2415x charger 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:	Tue, 6 Dec 2011 11:14:58 +0000
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	aliaksei.katovich@...ia.com
Cc:	sameo@...ux.intel.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] mfd: bq2415x charger driver

On Wed, Mar 09, 2011 at 04:48:03PM +0200, aliaksei.katovich@...ia.com wrote:

> +	file = debugfs_create_file("regdump", 0444, root, cli, &bq2415x_ops);
> +	if (IS_ERR(file))
> +		return;

Rather than create a custom register dump interface I'd suggest
converting to the regmap API which provides standard code to do this.

> +
> +/**
> + * bq2415x_exec - execute charger specific command
> + *
> + * Returns result of command execution upon success or negative otherwise
> + */
> +int bq2415x_exec(enum bq2415x_cmd cmd)
> +{
> +	int res;

> +	if (!bq2415x_cli)
> +		return -ENODEV;

> +	switch (cmd) {
> +	case BQ2415X_ENABLE_CHARGER:
> +		res = bq2415x_enable_charger(true);
> +		break;

...

> +EXPORT_SYMBOL(bq2415x_exec);

This should clearly be going through kernel frameworks and even if
defining a custom in kernel API for this device there's no reason to
emulate ioctl().

> +static int bq2415x_list_voltage(struct regulator_dev *rdev, unsigned i)
> +{
> +	struct bq2415x_regulator *r = rdev_get_drvdata(rdev);
> +
> +	if (i >= r->desc.n_voltages)
> +		return 0;
> +
> +	return bq2415x_vmap_calc(i, r->val_summ, r->init.constraints.min_uV);
> +}

MFDs should put their subfunction drivers within the appropriate
subsystem.

> +static int
> +bq2415x_set_voltage(struct regulator_dev *rdev, int min_uV, int max_uV)
> +{

This won't compile against current kernels, always submit against the
latest development versions (though in this case it won't compile with
3.0...)


> +	/* populate my consumers table */
> +	for (i = 0, j = 0; i < init->num_consumer_supplies && j < n; i++) {

No, this is all wrong - just pass the init data (including consumers)
straight through from the machine driver like all the other regulator
drivers.
--
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/