linux-kernel - starting up i2c regulator?

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>] [day] [month] [year] [list]

Date:	Fri, 21 Dec 2012 14:12:16 +0100
From:	"Piotr Sawuk" <a9702387@...t.univie.ac.at>
To:	linux-kernel@...r.kernel.org
Subject: starting up i2c regulator?

I have a gpl driver for lsm202dlh which worked with 2.6 kernels. now in 3.5
I can modprobe it (after some include-changes), but after the echo command
to new_device dmesg tells me

[ 1147.549042] lsm303dlh_a 6-0019: failed to get regulator
[ 1147.549055] lsm303dlh_a 6-0019: probe function fails fffffdfb
[ 1147.549067] i2c 6-0019: Driver lsm303dlh_a requests probe deferral
[ 1147.549078] i2c i2c-6: new_device: Instantiated device lsm303dlh_a at 0x19

and some kind of generic files in sysfs are created but not the ones that
driver should create. the driver does obviously do

	ddata->regulator = regulator_get(&client->dev, "vdd");
	if (IS_ERR(ddata->regulator)) {
		dev_err(&client->dev, "failed to get regulator\n");
		ret = PTR_ERR(ddata->regulator);
		ddata->regulator = NULL;
		goto err_op_failed;
	}
...
err_op_failed:
	kfree(ddata);
err_alloc:
	dev_err(&client->dev, "probe function fails %x", ret);
	return ret;

so my question is, what is the meaning of fffffdfb being returned from
regulator_get(dev,"vdd")? is there anything that needs to be done to let the
driver run on newer kernel? in applesmc.c I see nothing about "regulator"
being mentioned, is that whole thing gone?

P

--
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/