linux-kernel - Re: [PATCH V1 2/6] regulator: da9062: DA9062 regulator 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150418114828.GG26185@sirena.org.uk>
Date:	Sat, 18 Apr 2015 12:48:28 +0100
From:	Mark Brown <broonie@...nel.org>
To:	S Twiss <stwiss.opensource@...semi.com>
Cc:	LINUXKERNEL <linux-kernel@...r.kernel.org>,
	Liam Girdwood <lgirdwood@...il.com>,
	Alessandro Zummo <a.zummo@...ertech.it>,
	DEVICETREE <devicetree@...r.kernel.org>,
	David Dajun Chen <david.chen@...semi.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Ian Campbell <ijc+devicetree@...lion.org.uk>,
	Kumar Gala <galak@...eaurora.org>,
	LINUXINPUT <linux-input@...r.kernel.org>,
	LINUXWATCHDOG <linux-watchdog@...r.kernel.org>,
	Lee Jones <lee.jones@...aro.org>,
	Mark Rutland <mark.rutland@....com>,
	Pawel Moll <pawel.moll@....com>,
	RTCLINUX <rtc-linux@...glegroups.com>,
	Rob Herring <robh+dt@...nel.org>,
	Samuel Ortiz <sameo@...ux.intel.com>,
	Support Opensource <support.opensource@...semi.com>,
	Wim Van Sebroeck <wim@...ana.be>
Subject: Re: [PATCH V1 2/6] regulator: da9062: DA9062 regulator driver

On Fri, Apr 17, 2015 at 03:23:32PM +0100, S Twiss wrote:

> +/* Regulator interrupt handlers */
> +static irqreturn_t da9062_ldo_lim_event(int irq, void *data)
> +{
> +	struct da9062_regulators *regulators = data;
> +	struct da9062 *hw = regulators->regulator[0].hw;
> +	struct da9062_regulator *regl;
> +	int bits, i, ret;
> +
> +	ret = regmap_read(hw->regmap, DA9062AA_STATUS_D, &bits);
> +	if (ret < 0)
> +		return IRQ_NONE;

Please log an error for this, if we're having trouble talking to the
device that seems like a serious issue.

> +	for (i = regulators->n_regulators - 1; i >= 0; i--) {
> +		regl = &regulators->regulator[i];
> +		if (regl->info->oc_event.reg != DA9062AA_STATUS_D)
> +			continue;
> +
> +		if (BIT(regl->info->oc_event.lsb) & bits)
> +			regulator_notifier_call_chain(regl->rdev,
> +					REGULATOR_EVENT_OVER_CURRENT, NULL);
> +	}
> +
> +	return IRQ_HANDLED;

This will return IRQ_HANDLED even if none of the regulators were
flagginng an event.

> +static irqreturn_t da9062_vdd_warn_event(int irq, void *data)
> +{
> +	return IRQ_HANDLED;
> +}

Ignoring an interrupt is not usefully handling it - at the *least* this
should be generating a log message.

> +static struct da9062_regulators_pdata *da9062_parse_regulators_dt(
> +		struct platform_device *pdev,
> +		struct of_regulator_match **reg_matches)
> +{
> +	struct da9062_regulators_pdata *pdata;
> +	struct da9062_regulator_data *rdata;
> +	struct device_node *node;
> +	int i, n, num;
> +
> +	node = of_get_child_by_name(pdev->dev.parent->of_node, "regulators");
> +	if (!node) {
> +		dev_err(&pdev->dev, "Regulators device node not found\n");
> +		return ERR_PTR(-ENODEV);
> +	}
> +
> +	num = of_regulator_match(&pdev->dev, node, da9062_matches,
> +				 ARRAY_SIZE(da9062_matches));

Don't open code this, describe the DT names in the regualtor_desc and
let the core register.

> +	if (IS_ERR(pdata) || pdata->n_regulators == 0) {
> +		dev_err(&pdev->dev,
> +			"No regulators defined for the platform\n");
> +		return PTR_ERR(pdata);
> +	}
> +
> +	n_regulators = ARRAY_SIZE(local_regulator_info),

This is broken, the set of regulators in the silicon is not a property
of the platform.  The driver should just register all the regualtors
that are present in the silicon.  I'm fairly sure I've been through this
before...

> +	ret = request_threaded_irq(irq,
> +				   NULL, da9062_vdd_warn_event,
> +				   IRQF_TRIGGER_LOW | IRQF_ONESHOT,
> +				   "VDD_WARN", regulators);

devm_request_threaded_irq().

Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)