Skip to contentSkip to conversation

pda_power: add support for writeable properties

PATCH In review Daniel Mack 4 participants 33 messages May 11, 2010 – May 19, 2010

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/3 pda_power: add support for writeable properties

This patch adds support for writeable power supply properties and exposes them as writeable to sysfs.

A power supply implementation must implement two new function calls in order to use that feature:

int set_property(struct power_supply *psy,
enum power_supply_property psp, const union power_supply_propval *val);

int property_is_writeable(struct power_supply *psy,

                            enum power_supply_property psp);
Cc Anton Vorontsov <[email protected]>
Cc David Woodhouse <[email protected]>
Cc Andres Salomon <[email protected]>
Cc Alexey Starikovskiy <[email protected]>
Cc Len Brown <[email protected]>
Cc Mark Brown <[email protected]>
Cc Matt Reimer <[email protected]>
Cc Evgeniy Polyakov <[email protected]>
Cc Tejun Heo <[email protected]>
---
 drivers/power/power_supply_sysfs.c |   31 +++++++++++++++++++++++++++++--
 include/linux/power_supply.h       |    5 +++++
 2 files changed, 34 insertions(+), 2 deletions(-)
drivers/power/power_supply_sysfs.c +29 -2
index 5b6e352..5cfb410 100644
@@ -31,9 +31,9 @@
 
 #define POWER_SUPPLY_ATTR(_name)					\
 {									\
-	.attr = { .name = #_name, .mode = 0444 },	\
+	.attr = { .name = #_name },					\
 	.show = power_supply_show_property,				\
-	.store = NULL,							\
+	.store = power_supply_store_property,				\
 }
 
 static struct device_attribute power_supply_attrs[];
@@ -91,6 +91,25 @@ static ssize_t power_supply_show_property(struct device *dev,
 	return sprintf(buf, "%d\n", value.intval);
 }
 
+static ssize_t power_supply_store_property(struct device *dev,
+					   struct device_attribute *attr,
+					   const char *buf, size_t count) {
+	ssize_t ret;
+	struct power_supply *psy = dev_get_drvdata(dev);
+	const ptrdiff_t off = attr - power_supply_attrs;
+	union power_supply_propval value;
+	long long_val;
+
+	/* TODO: support other types than int */
+	ret = strict_strtol(buf, 10, &long_val);
+	if (ret < 0)
+		return ret;
+
+	value.intval = long_val;
+
+	return psy->set_property(psy, off, &value);
+}
+
 /* Must be in the same order as POWER_SUPPLY_PROP_* */
 static struct device_attribute power_supply_attrs[] = {
 	/* Properties of type `int' */
@@ -164,6 +183,14 @@ int power_supply_create_attrs(struct power_supply *psy)
 	}
 
 	for (j = 0; j < psy->num_properties; j++) {
+		mode_t mode = S_IRUSR | S_IRGRP | S_IROTH;
+
+		if (psy->property_is_writeable &&
+		    psy->property_is_writeable(psy, psy->properties[j]) > 0)
+			mode |= S_IWUSR;
+
+		power_supply_attrs[psy->properties[j]].attr.mode = mode;
+
 		rc = device_create_file(psy->dev,
 			    &power_supply_attrs[psy->properties[j]]);
 		if (rc)
include/linux/power_supply.h +5 -0
index ebd2b8f..f02f7fd 100644
@@ -144,6 +144,11 @@ struct power_supply {
 	int (*get_property)(struct power_supply *psy,
 			    enum power_supply_property psp,
 			    union power_supply_propval *val);
+	int (*set_property)(struct power_supply *psy,
+			    enum power_supply_property psp,
+			    const union power_supply_propval *val);
+	int (*property_is_writeable)(struct power_supply *psy,
+				     enum power_supply_property psp);
 	void (*external_power_changed)(struct power_supply *psy);
 	void (*set_charged)(struct power_supply *psy);
 
Signature · 1 line
1.7.1
#1 lore raw

PATCH 2/3 power/ds2760_battery: make charge_now and charge_full writeable

For userspace tools and daemons, it might be necessary to adjust the charge_now and charge_full properties of the ds2760 battery monitor, for example for unavoidable corrections due to aging batteries.

For better readbility and to avoid magic numbers in conversion calculations, RATED_CAPACITY_FACTOR is introduced.

Cc Anton Vorontsov <[email protected]>
Cc Matt Reimer <[email protected]>
Cc Evgeniy Polyakov <[email protected]>
Cc Tejun Heo <[email protected]>
Cc David Woodhouse <[email protected]>
Cc Andres Salomon <[email protected]>
Cc Alexey Starikovskiy <[email protected]>
Cc Len Brown <[email protected]>
Cc Mark Brown <[email protected]>
---
 drivers/power/ds2760_battery.c |   60 ++++++++++++++++++++++++++++++++++++++--
 1 files changed, 57 insertions(+), 3 deletions(-)
drivers/power/ds2760_battery.c +57 -3
index 3bf8d1f..b82bf92 100644
@@ -78,6 +78,7 @@ MODULE_PARM_DESC(current_accum, "current accumulator value");
 
 /* Some batteries have their rated capacity stored a N * 10 mAh, while
  * others use an index into this table. */
+#define RATED_CAPACITY_FACTOR 10
 static int rated_capacities[] = {
 	0,
 	920,	/* Samsung */
@@ -170,7 +171,8 @@ static int ds2760_battery_read_status(struct ds2760_device_info *di)
 		di->rated_capacity = rated_capacities[
 			(unsigned int)di->raw[DS2760_RATED_CAPACITY]];
 	else
-		di->rated_capacity = di->raw[DS2760_RATED_CAPACITY] * 10;
+		di->rated_capacity = di->raw[DS2760_RATED_CAPACITY] *
+						RATED_CAPACITY_FACTOR;
 
 	di->rated_capacity *= 1000; /* convert to µAh */
 
@@ -426,6 +428,54 @@ static int ds2760_battery_get_property(struct power_supply *psy,
 	return 0;
 }
 
+static int ds2760_battery_set_property(struct power_supply *psy,
+				       enum power_supply_property psp,
+				       const union power_supply_propval *val)
+{
+	int ret = -EPERM;
+	unsigned char tmp;
+	struct ds2760_device_info *di = to_ds2760_device_info(psy);
+
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
+		/* the interface counts in uAh, convert the value */
+		ds2760_battery_write_rated_capacity(di, (val->intval / 1000L) /
+							RATED_CAPACITY_FACTOR);
+		break;
+
+	case POWER_SUPPLY_PROP_CHARGE_NOW:
+		tmp = val->intval & 0xff;
+		ret = w1_ds2760_write(di->w1_dev, &tmp, DS2760_CURRENT_ACCUM_LSB, 1);
+		if (ret)
+			break;
+
+		tmp = val->intval >> 8;
+		ret = w1_ds2760_write(di->w1_dev, &tmp, DS2760_CURRENT_ACCUM_MSB, 1);
+
+		break;
+
+	default:
+		break;
+	}
+
+	return ret;
+}
+
+static int ds2760_battery_property_is_writeable(struct power_supply *psy,
+						enum power_supply_property psp)
+{
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
+	case POWER_SUPPLY_PROP_CHARGE_NOW:
+		return 1;
+
+	default:
+		break;
+	}
+
+	return 0;
+}
+
 static enum power_supply_property ds2760_battery_props[] = {
 	POWER_SUPPLY_PROP_STATUS,
 	POWER_SUPPLY_PROP_VOLTAGE_NOW,
@@ -460,6 +510,9 @@ static int ds2760_battery_probe(struct platform_device *pdev)
 	di->bat.properties	= ds2760_battery_props;
 	di->bat.num_properties	= ARRAY_SIZE(ds2760_battery_props);
 	di->bat.get_property	= ds2760_battery_get_property;
+	di->bat.set_property	= ds2760_battery_set_property;
+	di->bat.property_is_writeable =
+				  ds2760_battery_property_is_writeable;
 	di->bat.set_charged	= ds2760_battery_set_charged;
 	di->bat.external_power_changed =
 				  ds2760_battery_external_power_changed;
@@ -476,9 +529,10 @@ static int ds2760_battery_probe(struct platform_device *pdev)
 
 	ds2760_battery_write_status(di, status);
 
-	/* set rated capacity from module param */
+	/* set rated capacity from module param (given in 10 * mAh) */
 	if (rated_capacity)
-		ds2760_battery_write_rated_capacity(di, rated_capacity);
+		ds2760_battery_write_rated_capacity(di,
+			(rated_capacity * 10) / RATED_CAPACITY_FACTOR);
 
 	/* set current accumulator if given as parameter.
 	 * this should only be done for bootstrapping the value */
Signature · 1 line
1.7.1
#2 lore raw

Re: [PATCH 2/3] power/ds2760_battery: make charge_now and charge_full writeable

Quoted 6 lines · Daniel Mack

For userspace tools and daemons, it might be necessary to adjust the charge_now and charge_full properties of the ds2760 battery monitor, for example for unavoidable corrections due to aging batteries.

For better readbility and to avoid magic numbers in conversion calculations, RATED_CAPACITY_FACTOR is introduced.

Forgot to squash one hunk on this one. Take the version below, please.

Daniel

Quoted 1 line

From d1a2c4e5ff53742e7db04bdf5f0009dc013ccbfb Mon Sep 17 00:00:00 2001

From: Daniel Mack <[email protected]>
Date: Tue, 23 Mar 2010 09:00:51 +0100
Subject: [PATCH 2/3] power/ds2760_battery: make charge_now and charge_full writeable

For userspace tools and daemons, it might be necessary to adjust the charge_now and charge_full properties of the ds2760 battery monitor, for example for unavoidable corrections due to aging batteries.

For better readbility and to avoid magic numbers in conversion calculations, RATED_CAPACITY_FACTOR is introduced.

Cc Anton Vorontsov <[email protected]>
Cc Matt Reimer <[email protected]>
Cc Evgeniy Polyakov <[email protected]>
Cc Tejun Heo <[email protected]>
Cc David Woodhouse <[email protected]>
Cc Alexey Starikovskiy <[email protected]>
Cc Len Brown <[email protected]>
Cc Mark Brown <[email protected]>
---
 drivers/power/ds2760_battery.c |   60 ++++++++++++++++++++++++++++++++++++++--
 1 files changed, 57 insertions(+), 3 deletions(-)
drivers/power/ds2760_battery.c +57 -3
index 3bf8d1f..4edd253 100644
@@ -78,6 +78,7 @@ MODULE_PARM_DESC(current_accum, "current accumulator value");
 
 /* Some batteries have their rated capacity stored a N * 10 mAh, while
  * others use an index into this table. */
+#define RATED_CAPACITY_FACTOR 10
 static int rated_capacities[] = {
 	0,
 	920,	/* Samsung */
@@ -170,7 +171,8 @@ static int ds2760_battery_read_status(struct ds2760_device_info *di)
 		di->rated_capacity = rated_capacities[
 			(unsigned int)di->raw[DS2760_RATED_CAPACITY]];
 	else
-		di->rated_capacity = di->raw[DS2760_RATED_CAPACITY] * 10;
+		di->rated_capacity = di->raw[DS2760_RATED_CAPACITY] *
+						RATED_CAPACITY_FACTOR;
 
 	di->rated_capacity *= 1000; /* convert to µAh */
 
@@ -426,6 +428,54 @@ static int ds2760_battery_get_property(struct power_supply *psy,
 	return 0;
 }
 
+static int ds2760_battery_set_property(struct power_supply *psy,
+				       enum power_supply_property psp,
+				       const union power_supply_propval *val)
+{
+	int ret = 0;
+	unsigned char tmp;
+	struct ds2760_device_info *di = to_ds2760_device_info(psy);
+
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
+		/* the interface counts in uAh, convert the value */
+		ds2760_battery_write_rated_capacity(di, (val->intval / 1000L) /
+								RATED_CAPACITY_FACTOR);
+		break;
+
+	case POWER_SUPPLY_PROP_CHARGE_NOW:
+		tmp = val->intval & 0xff;
+		ret = w1_ds2760_write(di->w1_dev, &tmp, DS2760_CURRENT_ACCUM_LSB, 1);
+		if (ret)
+			break;
+
+		tmp = val->intval >> 8;
+		ret = w1_ds2760_write(di->w1_dev, &tmp, DS2760_CURRENT_ACCUM_MSB, 1);
+		break;
+
+	default:
+		ret = -EPERM;
+		break;
+	}
+
+	return ret;
+}
+
+static int ds2760_battery_property_is_writeable(struct power_supply *psy,
+						enum power_supply_property psp)
+{
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
+	case POWER_SUPPLY_PROP_CHARGE_NOW:
+		return 1;
+
+	default:
+		break;
+	}
+
+	return 0;
+}
+
 static enum power_supply_property ds2760_battery_props[] = {
 	POWER_SUPPLY_PROP_STATUS,
 	POWER_SUPPLY_PROP_VOLTAGE_NOW,
@@ -460,6 +510,9 @@ static int ds2760_battery_probe(struct platform_device *pdev)
 	di->bat.properties	= ds2760_battery_props;
 	di->bat.num_properties	= ARRAY_SIZE(ds2760_battery_props);
 	di->bat.get_property	= ds2760_battery_get_property;
+	di->bat.set_property	= ds2760_battery_set_property;
+	di->bat.property_is_writeable =
+				  ds2760_battery_property_is_writeable;
 	di->bat.set_charged	= ds2760_battery_set_charged;
 	di->bat.external_power_changed =
 				  ds2760_battery_external_power_changed;
@@ -476,9 +529,10 @@ static int ds2760_battery_probe(struct platform_device *pdev)
 
 	ds2760_battery_write_status(di, status);
 
-	/* set rated capacity from module param */
+	/* set rated capacity from module param (given in 10 * mAh) */
 	if (rated_capacity)
-		ds2760_battery_write_rated_capacity(di, rated_capacity);
+		ds2760_battery_write_rated_capacity(di,
+			(rated_capacity * 10) / RATED_CAPACITY_FACTOR);
 
 	/* set current accumulator if given as parameter.
 	 * this should only be done for bootstrapping the value */
Signature · 1 line
1.7.1
#3 lore raw

Re: [PATCH 2/3] power/ds2760_battery: make charge_now and charge_full writeable

In reply to Daniel Mack

On Tue, May 11, 2010 at 06:38:45PM +0200, Daniel Mack wrote:
[...]

drivers/power/ds2760_battery.c static int ds2760_battery_get_property(struct power_supply *psy, · line 443

Quoted 13 lines
drivers/power/ds2760_battery.c +13 -0
+static int ds2760_battery_set_property(struct power_supply *psy,
+				       enum power_supply_property psp,
+				       const union power_supply_propval *val)
+{
+	int ret = -EPERM;
+	unsigned char tmp;
+	struct ds2760_device_info *di = to_ds2760_device_info(psy);
+
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
+		/* the interface counts in uAh, convert the value */
+		ds2760_battery_write_rated_capacity(di, (val->intval / 1000L) /
+							RATED_CAPACITY_FACTOR);

OK, Mark hinted that you should not change rated (design) capacity, ever. You've made CHARGE_FULL writable, which now actually changes CHARGE_FULL_DESIGN (which reports rated_capacity). Obviously, this isn't acceptable.

I understand that you might want to change rated capacity for your custom battery setups, and that's fine. After all, it's your hardware, and you have a right to break it. :-)

But to do so,

1. Could you at least change this back to POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN, so it'll be clear what exactly this prop is actually changing, and

2. Can we introduce Kconfig symbol BATTERY_DS2760_UNSAFE_OPS, and put an #ifdefs for this property? It should be 'default n', of course. Plus we can #ifdef the rated_capacity module param as well.

Thanks!

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#4 lore raw

Re: [PATCH 2/3] power/ds2760_battery: make charge_now and charge_full writeable

Quoted 13 lines · Anton Vorontsov

On Tue, May 11, 2010 at 06:38:45PM +0200, Daniel Mack wrote:
[...]

Quoted 10 lines
drivers/power/ds2760_battery.c +10 -0
+static int ds2760_battery_set_property(struct power_supply *psy,
+				       enum power_supply_property psp,
+				       const union power_supply_propval *val)
+{
+	int ret = -EPERM;
+	unsigned char tmp;
+	struct ds2760_device_info *di = to_ds2760_device_info(psy);
+
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
Quoted 8 lines

drivers/power/ds2760_battery.c static int ds2760_battery_get_property(struct power_supply *psy, · line 443

Quoted 3 lines
drivers/power/ds2760_battery.c +3 -0
+		/* the interface counts in uAh, convert the value */
+		ds2760_battery_write_rated_capacity(di, (val->intval / 1000L) /
+							RATED_CAPACITY_FACTOR);

OK, Mark hinted that you should not change rated (design) capacity, ever. You've made CHARGE_FULL writable, which now actually changes CHARGE_FULL_DESIGN (which reports rated_capacity). Obviously, this isn't acceptable.

Of course, sorry.

Quoted 3 lines

I understand that you might want to change rated capacity for your custom battery setups, and that's fine. After all, it's your hardware, and you have a right to break it. :-)

Well, if it was a hack purely for my hardware, I wouldn't share it beat it upstream ;) I believe that this feature is something all users of battery-driven devices need, as all batteries age.

Quoted 5 lines

But to do so,

1. Could you at least change this back to POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN, so it'll be clear what exactly this prop is actually changing, and

Do you see any other way to store the actual rated capacity (not the one the battery had in its good days) inside the chip?

Quoted 4 lines

2. Can we introduce Kconfig symbol BATTERY_DS2760_UNSAFE_OPS, and put an #ifdefs for this property? It should be 'default n', of course. Plus we can #ifdef the rated_capacity module param as well.

Hmm, I see that this is one way. I can do this, but I'm hessitant and would rather go a cleaer way ...

Thanks,
Daniel

#5 lore raw

Re: [PATCH 2/3] power/ds2760_battery: make charge_now and charge_full writeable

On Tue, May 11, 2010 at 07:28:59PM +0200, Daniel Mack wrote:
[...]

Quoted 6 lines
Quoted 3 lines

1. Could you at least change this back to POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN, so it'll be clear what exactly this prop is actually changing, and

Do you see any other way to store the actual rated capacity (not the one the battery had in its good days) inside the chip?

In that case it should be indeed POWER_SUPPLY_PROP_CHARGE_FULL, which is full_active_uAh, which we get from di->raw[DS2760_ACTIVE_FULL] and di->raw[DS2760_ACTIVE_FULL + 1].

We fall back to deriving it from rated_capacity if full_active is 0 (your case?):

        /* If the full_active_uAh value is not given, fall back to the rated
         * capacity. This is likely to happen when chips are not part of the
         * battery pack and is therefore not bootstrapped. */
        if (di->full_active_uAh == 0)
                di->full_active_uAh = di->rated_capacity / 1000L;

So, you probably want to make DS2760_ACTIVE_FULL writable, not DS2760_RATED_CAPACITY.

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#6 lore raw

Re: [PATCH 2/3] power/ds2760_battery: make charge_now and charge_full writeable

(sorry for the late follow-up)

Quoted 16 lines · Anton Vorontsov

On Tue, May 11, 2010 at 07:28:59PM +0200, Daniel Mack wrote:
[...]

Quoted 6 lines
Quoted 3 lines

1. Could you at least change this back to POWER_SUPPLY_PROP_CHARGE_FULL_DESIGN, so it'll be clear what exactly this prop is actually changing, and

Do you see any other way to store the actual rated capacity (not the one the battery had in its good days) inside the chip?

In that case it should be indeed POWER_SUPPLY_PROP_CHARGE_FULL, which is full_active_uAh, which we get from di->raw[DS2760_ACTIVE_FULL] and di->raw[DS2760_ACTIVE_FULL + 1].

We fall back to deriving it from rated_capacity if full_active is 0 (your case?):

Quoted 8 lines
        /* If the full_active_uAh value is not given, fall back to the rated
         * capacity. This is likely to happen when chips are not part of the
         * battery pack and is therefore not bootstrapped. */
        if (di->full_active_uAh == 0)
                di->full_active_uAh = di->rated_capacity / 1000L;

So, you probably want to make DS2760_ACTIVE_FULL writable, not DS2760_RATED_CAPACITY.

Ah of course. And DS2760_ACTIVE_FULL is 16bit wide, so we also get rid of the range problem.

Thanks,
Daniel

#7 lore raw

PATCH 3/3 power/ds2760_battery: use factor of 20 for rated_capacity

In reply to Daniel Mack

In the ds2760 driver, the currently used factor of 10 to store the rated battery capacity internally is not sufficient for batteries > 2.55 Ah, as the 8-bit register will overflow for bigger values.

Change the factor to 20 to broaden that range. Note that due to RATED_CAPACITY_FACTOR, the external interface won't change, neither for the writeable sysfs entires nor for the kernel rated_capacity module parameter.

Cc Anton Vorontsov <[email protected]>
Cc Matt Reimer <[email protected]>
Cc Evgeniy Polyakov <[email protected]>
Cc Tejun Heo <[email protected]>
Cc David Woodhouse <[email protected]>
Cc Len Brown <[email protected]>
Cc Mark Brown <[email protected]>
---
 drivers/power/ds2760_battery.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
drivers/power/ds2760_battery.c +1 -1
index b82bf92..7b3043f 100644
@@ -78,7 +78,7 @@ MODULE_PARM_DESC(current_accum, "current accumulator value");
 
 /* Some batteries have their rated capacity stored a N * 10 mAh, while
  * others use an index into this table. */
-#define RATED_CAPACITY_FACTOR 10
+#define RATED_CAPACITY_FACTOR 20
 static int rated_capacities[] = {
 	0,
 	920,	/* Samsung */
Signature · 1 line
1.7.1
#8 lore raw

Re: [PATCH 3/3] power/ds2760_battery: use factor of 20 for rated_capacity

Quoted 17 lines · Daniel Mack

In the ds2760 driver, the currently used factor of 10 to store the rated battery capacity internally is not sufficient for batteries > 2.55 Ah, as the 8-bit register will overflow for bigger values.

Change the factor to 20 to broaden that range. Note that due to RATED_CAPACITY_FACTOR, the external interface won't change, neither for the writeable sysfs entires nor for the kernel rated_capacity module parameter.

Cc Anton Vorontsov <[email protected]>
Cc Matt Reimer <[email protected]>
Cc Evgeniy Polyakov <[email protected]>
Cc Tejun Heo <[email protected]>
Cc David Woodhouse <[email protected]>
Cc Len Brown <[email protected]>
Cc Mark Brown <[email protected]>
Quoted 1 line

---

Hi Daniel,

Sorry, it took quite a bit to get to your patches.

They look good (as usual), but I have a few concerns.

drivers/power/ds2760_battery.c MODULE_PARM_DESC(current_accum, "current accumulator value"); · line 81

Quoted 13 lines
 drivers/power/ds2760_battery.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
drivers/power/ds2760_battery.c +1 -1
index b82bf92..7b3043f 100644
@@ -78,7 +78,7 @@ MODULE_PARM_DESC(current_accum, "current accumulator value");
 
 /* Some batteries have their rated capacity stored a N * 10 mAh, while
  * others use an index into this table. */
-#define RATED_CAPACITY_FACTOR 10
+#define RATED_CAPACITY_FACTOR 20

I'm a bit worried about this one.

Shouldn't this confuse batteries that already store rated capacity with factor of ten? If so, please introduce a module option.

Also, you don't update comments and module params description, e.g.

MODULE_PARM_DESC(rated_capacity, "rated battery capacity, 10*mAh or index");
....
/* set rated capacity from module param (given in 10 * mAh) */

Is that intentionally?

Thanks!

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#9 lore raw

Re: [PATCH 3/3] power/ds2760_battery: use factor of 20 for rated_capacity

Quoted 21 lines · Anton Vorontsov

drivers/power/ds2760_battery.c MODULE_PARM_DESC(current_accum, "current accumulator value"); · line 81

Quoted 13 lines · Daniel Mack
 drivers/power/ds2760_battery.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
drivers/power/ds2760_battery.c +1 -1
index b82bf92..7b3043f 100644
@@ -78,7 +78,7 @@ MODULE_PARM_DESC(current_accum, "current accumulator value");
 
 /* Some batteries have their rated capacity stored a N * 10 mAh, while
  * others use an index into this table. */
-#define RATED_CAPACITY_FACTOR 10
+#define RATED_CAPACITY_FACTOR 20

I'm a bit worried about this one.

Shouldn't this confuse batteries that already store rated capacity with factor of ten? If so, please introduce a module option.

Quoted 8 lines

Also, you don't update comments and module params description, e.g.

MODULE_PARM_DESC(rated_capacity, "rated battery capacity, 10*mAh or index");
....
/* set rated capacity from module param (given in 10 * mAh) */

Is that intentionally?

Well, this parameter doesn't change, and hence the comment is left untouched. If it is passed as module option, it is interpreted as 10*mAh and converted to the internal value.

You're right though about your concern about batteries that already stored a value given in mAh (and not as index) - this will break unless the module is loaded with a proper module parameter. Don't know whether this is acceptable.

Daniel

#10 lore raw

Re: [PATCH 3/3] power/ds2760_battery: use factor of 20 for rated_capacity

On Tue, May 11, 2010 at 07:25:29PM +0200, Daniel Mack wrote:
[...]

Quoted 20 lines
Quoted 11 lines

drivers/power/ds2760_battery.c MODULE_PARM_DESC(current_accum, "current accumulator value"); · line 81

Quoted 4 lines

/* Some batteries have their rated capacity stored a N * 10 mAh, while
* others use an index into this table. */

drivers/power/ds2760_battery.c +1 -1
-#define RATED_CAPACITY_FACTOR 10
+#define RATED_CAPACITY_FACTOR 20

I'm a bit worried about this one.

Shouldn't this confuse batteries that already store rated capacity with factor of ten? If so, please introduce a module option.

Quoted 8 lines

Also, you don't update comments and module params description, e.g.

MODULE_PARM_DESC(rated_capacity, "rated battery capacity, 10*mAh or index");
....
/* set rated capacity from module param (given in 10 * mAh) */

Is that intentionally?

Quoted 8 lines

Well, this parameter doesn't change, and hence the comment is left untouched. If it is passed as module option, it is interpreted as 10*mAh and converted to the internal value.

You're right though about your concern about batteries that already stored a value given in mAh (and not as index) - this will break unless the module is loaded with a proper module parameter. Don't know whether this is acceptable.

Unfortunately, it is not. You have to do a run-time option, i.e. module parameter (you can set up default value for this module parameter via Kconfig symbol).

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#11 lore raw
In reply to Daniel Mack
Quoted 2 lines · Daniel Mack

This patch adds support for writeable power supply properties and exposes them as writeable to sysfs.

A long-awaited feature! Thanks!

Quoted 9 lines

A power supply implementation must implement two new function calls in order to use that feature:

int set_property(struct power_supply *psy,
enum power_supply_property psp, const union power_supply_propval *val);

int property_is_writeable(struct power_supply *psy,

I'm not a native English speaker, but I think this should be 'writable'.

Quoted 1 line
                            enum power_supply_property psp);

[...]

Quoted 37 lines

#define POWER_SUPPLY_ATTR(_name) \
{ \

drivers/power/power_supply_sysfs.c +21 -2
-	.attr = { .name = #_name, .mode = 0444 },	\
+	.attr = { .name = #_name },					\
 	.show = power_supply_show_property,				\
-	.store = NULL,							\
+	.store = power_supply_store_property,				\
 }
 
 static struct device_attribute power_supply_attrs[];
@@ -91,6 +91,25 @@ static ssize_t power_supply_show_property(struct device *dev,
 	return sprintf(buf, "%d\n", value.intval);
 }
 
+static ssize_t power_supply_store_property(struct device *dev,
+					   struct device_attribute *attr,
+					   const char *buf, size_t count) {
+	ssize_t ret;
+	struct power_supply *psy = dev_get_drvdata(dev);
+	const ptrdiff_t off = attr - power_supply_attrs;
+	union power_supply_propval value;
+	long long_val;
+
+	/* TODO: support other types than int */
+	ret = strict_strtol(buf, 10, &long_val);
+	if (ret < 0)
+		return ret;
+
+	value.intval = long_val;
+
+	return psy->set_property(psy, off, &value);
+}
+
 /* Must be in the same order as POWER_SUPPLY_PROP_* */
 static struct device_attribute power_supply_attrs[] = {
 	/* Properties of type `int' */

drivers/power/power_supply_sysfs.c int power_supply_create_attrs(struct power_supply *psy) · line 192

Quoted 10 lines
drivers/power/power_supply_sysfs.c +7 -0
@@ -164,6 +183,14 @@ int power_supply_create_attrs(struct power_supply *psy)
 	}
 
 	for (j = 0; j < psy->num_properties; j++) {
+		mode_t mode = S_IRUSR | S_IRGRP | S_IROTH;
+
+		if (psy->property_is_writeable &&
+		    psy->property_is_writeable(psy, psy->properties[j]) > 0)
+			mode |= S_IWUSR;
+
+		power_supply_attrs[psy->properties[j]].attr.mode = mode;

This is dangerous. You're changing the attr mode for all power supplies, including already registered. I have no idea how attr handling core will cope with that, but we'd better not check this. :-)

Instead, change the mode to '0644' unconditionally, and in power_supply_store_property() do something like this:

{
	if (!psy->set_property)
		return -EINVAL; (or EPERM, not sure which is better).
	....
	return psy->set_property(psy, off, &value);
	/* ^^^here set_property() should -EPERM if some property
	 * is read-only.
	 */
}

Plus, that way you don't need is_writable().

Thanks,

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#12 lore raw
Quoted 4 lines · Anton Vorontsov
Quoted 3 lines · Daniel Mack

A power supply implementation must implement two new function calls in order to use that feature:

Quoted 8 lines
Quoted 5 lines

int set_property(struct power_supply *psy,
enum power_supply_property psp, const union power_supply_propval *val);

int property_is_writeable(struct power_supply *psy,

I'm not a native English speaker, but I think this should be 'writable'.

Me neither, but I looked it up, and it's in fact both allowed ;)

Quoted 25 lines
Quoted 25 lines
drivers/power/power_supply_sysfs.c +19 -0
+static ssize_t power_supply_store_property(struct device *dev,
+					   struct device_attribute *attr,
+					   const char *buf, size_t count) {
+	ssize_t ret;
+	struct power_supply *psy = dev_get_drvdata(dev);
+	const ptrdiff_t off = attr - power_supply_attrs;
+	union power_supply_propval value;
+	long long_val;
+
+	/* TODO: support other types than int */
+	ret = strict_strtol(buf, 10, &long_val);
+	if (ret < 0)
+		return ret;
+
+	value.intval = long_val;
+
+	return psy->set_property(psy, off, &value);
+}
+
 /* Must be in the same order as POWER_SUPPLY_PROP_* */
 static struct device_attribute power_supply_attrs[] = {
 	/* Properties of type `int' */
@@ -164,6 +183,14 @@ int power_supply_create_attrs(struct power_supply *psy)
 	}
 
Quoted 13 lines

drivers/power/power_supply_sysfs.c int power_supply_create_attrs(struct power_supply *psy) · line 192

Quoted 8 lines
drivers/power/power_supply_sysfs.c +7 -0
 	for (j = 0; j < psy->num_properties; j++) {
+		mode_t mode = S_IRUSR | S_IRGRP | S_IROTH;
+
+		if (psy->property_is_writeable &&
+		    psy->property_is_writeable(psy, psy->properties[j]) > 0)
+			mode |= S_IWUSR;
+
+		power_supply_attrs[psy->properties[j]].attr.mode = mode;

This is dangerous. You're changing the attr mode for all power supplies, including already registered. I have no idea how attr handling core will cope with that, but we'd better not check this. :-)

Hmm, no. The code defaults to (S_IRUSR | S_IRGRP | S_IROTH) which is 0444, just like it was before. So there shouldn't be any regression. The mode is only changed if the psy defines a property_is_writeable() callback which returns 1. Or do I miss your point?

Quoted 12 lines

Instead, change the mode to '0644' unconditionally, and in power_supply_store_property() do something like this:

{
	if (!psy->set_property)
		return -EINVAL; (or EPERM, not sure which is better).
	....
	return psy->set_property(psy, off, &value);
	/* ^^^here set_property() should -EPERM if some property
	 * is read-only.
	 */
}
Quoted 1 line

Plus, that way you don't need is_writable().

Ugh, really? I would _much_ prefer to actually _see_ which property is writeable, just from looking at the file attributes in sysfs.

Thanks,
Daniel

#13 lore raw

On Tue, May 11, 2010 at 07:58:12PM +0200, Daniel Mack wrote:
[...]

Quoted 4 lines

Hmm, no. The code defaults to (S_IRUSR | S_IRGRP | S_IROTH) which is 0444, just like it was before. So there shouldn't be any regression. The mode is only changed if the psy defines a property_is_writeable() callback which returns 1. Or do I miss your point?

Yes, power_supply_attrs is a global array, and you shouldn't change it between power_supply_register() calls.

If you don't see why it's a bad idea in general, think about it other way, a race:

...someone registers psy0 with attr X marked as read-only... ...code flow stops before device_create_file(psy0, global->mode).. [preempt]
...someone registers psy1 with attr X marked as writable... ...you set up global->mode to 0644...
[preempt again]
...we end up calling device_create_file(psy0, 0644)...

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#14 lore raw
Quoted 13 lines · Anton Vorontsov

On Tue, May 11, 2010 at 07:58:12PM +0200, Daniel Mack wrote:
[...]

Quoted 4 lines

Hmm, no. The code defaults to (S_IRUSR | S_IRGRP | S_IROTH) which is 0444, just like it was before. So there shouldn't be any regression. The mode is only changed if the psy defines a property_is_writeable() callback which returns 1. Or do I miss your point?

Yes, power_supply_attrs is a global array, and you shouldn't change it between power_supply_register() calls.

If you don't see why it's a bad idea in general, think about it other way, a race:

Quoted 7 lines

...someone registers psy0 with attr X marked as read-only... ...code flow stops before device_create_file(psy0, global->mode).. [preempt]
...someone registers psy1 with attr X marked as writable... ...you set up global->mode to 0644...
[preempt again]
...we end up calling device_create_file(psy0, 0644)...

Ah, I see. But the struct passed in is just used as template, right? So for the particular case you outlined, a simple lock should do the trick, right? I would prefer this over always-writeable file entries.

Daniel

#15 lore raw

PATCH 1/1 Introduce {sysfs,device}_create_file_mode

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

Now that we need it, introduce sysfs_create_file_mode() and device_create_file_mode() functions. With these, creating attributes with different modes is a joy.

---

Quoted 15 lines · Daniel Mack
Quoted 6 lines · Anton Vorontsov

Yes, power_supply_attrs is a global array, and you shouldn't change it between power_supply_register() calls.

If you don't see why it's a bad idea in general, think about it other way, a race:

Quoted 7 lines

...someone registers psy0 with attr X marked as read-only... ...code flow stops before device_create_file(psy0, global->mode).. [preempt]
...someone registers psy1 with attr X marked as writable... ...you set up global->mode to 0644...
[preempt again]
...we end up calling device_create_file(psy0, 0644)...

Quoted 1 line

Ah, I see. But the struct passed in is just used as template, right?

In general, you can't assume that it's just a template, otherwise 'const ptrdiff_t off = attr - power_supply_attrs;' wouldn't work.

I.e. 'attr' points to exact attribute you specified during registration. Weather its fields are used as a template or not, we don't know (well, we know how the sysfs core uses them *today*, but we don't know how sysfs will use them tomorrow).

Quoted 3 lines

So
for the particular case you outlined, a simple lock should do the trick, right?

Yes, for the particular case.

Still, I don't think that playing with attr->mode is a good idea.

If we don't want to use attr->mode for mode specifier (and I think we don't), we must implement a clean API for such a case.

Luckily, there's sysfs_add_file_mode, so if anyone will want to change attr->mode behaviour, one will have to deal with that function, and so we'll be safe.

And we must use that function, not just silently play attr->mode games during registration. That also avoids any need for locking.

Greg, does the patch look OK? If so, I'd like it to go via battery-2.6.git tree, along with patches that need that one.

You can see the original thread here:
http://lkml.org/lkml/2010/5/11/71

See power_supply_create_attrs(), there we'll use
device_create_file_mode() instead of messing with
power_supply_attrs[psy->properties[j]].attr.mode.

 drivers/base/core.c    |   21 +++++++++++++++++++++
 fs/sysfs/file.c        |   16 ++++++++++++++++
 include/linux/device.h |    3 +++
 include/linux/sysfs.h  |   10 ++++++++++
 4 files changed, 50 insertions(+), 0 deletions(-)
drivers/base/core.c +21 -0
index b56a0ba..1bc6134 100644
@@ -440,6 +440,27 @@ struct kset *devices_kset;
  * device_create_file - create sysfs attribute file for device.
  * @dev: device.
  * @attr: device attribute descriptor.
+ * @mode: file mode.
+ *
+ * This function is similar to device_create_file(), except that it
+ * doesn't use attr->mode for mode specifier.
+ */
+int device_create_file_mode(struct device *dev,
+			    const struct device_attribute *attr,
+			    mode_t mode)
+{
+	int error = 0;
+
+	if (dev)
+		error = sysfs_create_file_mode(&dev->kobj, &attr->attr, mode);
+	return error;
+}
+EXPORT_SYMBOL_GPL(device_create_file_mode);
+
+/**
+ * device_create_file - create sysfs attribute file for device.
+ * @dev: device.
+ * @attr: device attribute descriptor.
  */
 int device_create_file(struct device *dev,
 		       const struct device_attribute *attr)
fs/sysfs/file.c +16 -0
index e222b25..7bebb60 100644
@@ -528,6 +528,22 @@ int sysfs_add_file(struct sysfs_dirent *dir_sd, const struct attribute *attr,
 	return sysfs_add_file_mode(dir_sd, attr, type, attr->mode);
 }
 
+/**
+ *	sysfs_create_file_mode - create an attribute file for an object.
+ *	@kobj:	object we're creating for.
+ *	@attr:	attribute descriptor.
+ *	@mode:	file mode.
+ *
+ *	This function is similar to sysfs_create_file(), except that it
+ *	doesn't use attr->mode for mode specifier.
+ */
+int sysfs_create_file_mode(struct kobject *kobj, const struct attribute *attr,
+			   mode_t mode)
+{
+	BUG_ON(!kobj || !kobj->sd || !attr);
+
+	return sysfs_add_file_mode(kobj->sd, attr, SYSFS_KOBJ_ATTR, mode);
+}
 
 /**
  *	sysfs_create_file - create an attribute file for an object.
include/linux/device.h +3 -0
index 1821928..8277364 100644
@@ -337,6 +337,9 @@ struct device_attribute {
 #define DEVICE_ATTR(_name, _mode, _show, _store) \
 struct device_attribute dev_attr_##_name = __ATTR(_name, _mode, _show, _store)
 
+extern int __must_check device_create_file_mode(struct device *device,
+					const struct device_attribute *entry,
+					mode_t mode);
 extern int __must_check device_create_file(struct device *device,
 					const struct device_attribute *entry);
 extern void device_remove_file(struct device *dev,
include/linux/sysfs.h +10 -0
index f0496b3..222774f 100644
@@ -130,6 +130,9 @@ int __must_check sysfs_rename_dir(struct kobject *kobj, const char *new_name);
 int __must_check sysfs_move_dir(struct kobject *kobj,
 				struct kobject *new_parent_kobj);
 
+int __must_check sysfs_create_file_mode(struct kobject *kobj,
+					const struct attribute *attr,
+					mode_t mode);
 int __must_check sysfs_create_file(struct kobject *kobj,
 				   const struct attribute *attr);
 int __must_check sysfs_create_files(struct kobject *kobj,
@@ -202,6 +205,13 @@ static inline int sysfs_move_dir(struct kobject *kobj,
 	return 0;
 }
 
+static inline int sysfs_create_file_mode(struct kobject *kobj,
+					 const struct attribute *attr,
+					 mode_t mode)
+{
+	return 0;
+}
+
 static inline int sysfs_create_file(struct kobject *kobj,
 				    const struct attribute *attr)
 {
Signature · 1 line
1.7.0.5
#16 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

Quoted 4 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Quoted 8 lines

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

Now that we need it, introduce sysfs_create_file_mode() and device_create_file_mode() functions. With these, creating attributes with different modes is a joy.

Ah, nice. Thanks for caring! If this is accepted, I'll respin my patches and make them use it.

Thanks,
Daniel

Quoted 173 lines

---

Quoted 15 lines · Daniel Mack
Quoted 6 lines · Anton Vorontsov

Yes, power_supply_attrs is a global array, and you shouldn't change it between power_supply_register() calls.

If you don't see why it's a bad idea in general, think about it other way, a race:

Quoted 7 lines

...someone registers psy0 with attr X marked as read-only... ...code flow stops before device_create_file(psy0, global->mode).. [preempt]
...someone registers psy1 with attr X marked as writable... ...you set up global->mode to 0644...
[preempt again]
...we end up calling device_create_file(psy0, 0644)...

Quoted 1 line

Ah, I see. But the struct passed in is just used as template, right?

In general, you can't assume that it's just a template, otherwise 'const ptrdiff_t off = attr - power_supply_attrs;' wouldn't work.

I.e. 'attr' points to exact attribute you specified during registration. Weather its fields are used as a template or not, we don't know (well, we know how the sysfs core uses them *today*, but we don't know how sysfs will use them tomorrow).

Quoted 3 lines

So
for the particular case you outlined, a simple lock should do the trick, right?

Yes, for the particular case.

Still, I don't think that playing with attr->mode is a good idea.

If we don't want to use attr->mode for mode specifier (and I think we don't), we must implement a clean API for such a case.

Luckily, there's sysfs_add_file_mode, so if anyone will want to change attr->mode behaviour, one will have to deal with that function, and so we'll be safe.

And we must use that function, not just silently play attr->mode games during registration. That also avoids any need for locking.

Greg, does the patch look OK? If so, I'd like it to go via battery-2.6.git tree, along with patches that need that one.

You can see the original thread here:
http://lkml.org/lkml/2010/5/11/71

See power_supply_create_attrs(), there we'll use
device_create_file_mode() instead of messing with
power_supply_attrs[psy->properties[j]].attr.mode.

 drivers/base/core.c    |   21 +++++++++++++++++++++
 fs/sysfs/file.c        |   16 ++++++++++++++++
 include/linux/device.h |    3 +++
 include/linux/sysfs.h  |   10 ++++++++++
 4 files changed, 50 insertions(+), 0 deletions(-)
drivers/base/core.c +21 -0
index b56a0ba..1bc6134 100644
@@ -440,6 +440,27 @@ struct kset *devices_kset;
  * device_create_file - create sysfs attribute file for device.
  * @dev: device.
  * @attr: device attribute descriptor.
+ * @mode: file mode.
+ *
+ * This function is similar to device_create_file(), except that it
+ * doesn't use attr->mode for mode specifier.
+ */
+int device_create_file_mode(struct device *dev,
+			    const struct device_attribute *attr,
+			    mode_t mode)
+{
+	int error = 0;
+
+	if (dev)
+		error = sysfs_create_file_mode(&dev->kobj, &attr->attr, mode);
+	return error;
+}
+EXPORT_SYMBOL_GPL(device_create_file_mode);
+
+/**
+ * device_create_file - create sysfs attribute file for device.
+ * @dev: device.
+ * @attr: device attribute descriptor.
  */
 int device_create_file(struct device *dev,
 		       const struct device_attribute *attr)
fs/sysfs/file.c +16 -0
index e222b25..7bebb60 100644
@@ -528,6 +528,22 @@ int sysfs_add_file(struct sysfs_dirent *dir_sd, const struct attribute *attr,
 	return sysfs_add_file_mode(dir_sd, attr, type, attr->mode);
 }
 
+/**
+ *	sysfs_create_file_mode - create an attribute file for an object.
+ *	@kobj:	object we're creating for.
+ *	@attr:	attribute descriptor.
+ *	@mode:	file mode.
+ *
+ *	This function is similar to sysfs_create_file(), except that it
+ *	doesn't use attr->mode for mode specifier.
+ */
+int sysfs_create_file_mode(struct kobject *kobj, const struct attribute *attr,
+			   mode_t mode)
+{
+	BUG_ON(!kobj || !kobj->sd || !attr);
+
+	return sysfs_add_file_mode(kobj->sd, attr, SYSFS_KOBJ_ATTR, mode);
+}
 
 /**
  *	sysfs_create_file - create an attribute file for an object.
include/linux/device.h +3 -0
index 1821928..8277364 100644
@@ -337,6 +337,9 @@ struct device_attribute {
 #define DEVICE_ATTR(_name, _mode, _show, _store) \
 struct device_attribute dev_attr_##_name = __ATTR(_name, _mode, _show, _store)
 
+extern int __must_check device_create_file_mode(struct device *device,
+					const struct device_attribute *entry,
+					mode_t mode);
 extern int __must_check device_create_file(struct device *device,
 					const struct device_attribute *entry);
 extern void device_remove_file(struct device *dev,
include/linux/sysfs.h +10 -0
index f0496b3..222774f 100644
@@ -130,6 +130,9 @@ int __must_check sysfs_rename_dir(struct kobject *kobj, const char *new_name);
 int __must_check sysfs_move_dir(struct kobject *kobj,
 				struct kobject *new_parent_kobj);
 
+int __must_check sysfs_create_file_mode(struct kobject *kobj,
+					const struct attribute *attr,
+					mode_t mode);
 int __must_check sysfs_create_file(struct kobject *kobj,
 				   const struct attribute *attr);
 int __must_check sysfs_create_files(struct kobject *kobj,
@@ -202,6 +205,13 @@ static inline int sysfs_move_dir(struct kobject *kobj,
 	return 0;
 }
 
+static inline int sysfs_create_file_mode(struct kobject *kobj,
+					 const struct attribute *attr,
+					 mode_t mode)
+{
+	return 0;
+}
+
 static inline int sysfs_create_file(struct kobject *kobj,
 				    const struct attribute *attr)
 {
Signature · 1 line
1.7.0.5
Acked-by on v1 1/1
#17 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

In reply to Anton Vorontsov
Quoted 8 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

But you race the creation of the device notifying userspace, and then the file being created, right? Or is that properly taken care of elsewhere?

Quoted 3 lines

Greg, does the patch look OK? If so, I'd like it to go via battery-2.6.git tree, along with patches that need that one.

Looks good with one minor problem:

drivers/base/core.c struct kset *devices_kset; · line 440

Quoted 4 lines
drivers/base/core.c +0 -0
@@ -440,6 +440,27 @@ struct kset *devices_kset;
  * device_create_file - create sysfs attribute file for device.

That should be "device_create_file_mode"

Make that change and then feel free to take it through your tree with an:

on it.

thanks,

greg k-h

#18 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

Quoted 5 lines · Greg KH
Quoted 4 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Quoted 7 lines
Quoted 4 lines

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

But you race the creation of the device notifying userspace, and then the file being created, right?

Yep, you've raised that question once, like 3 years ago. :-)

http://lkml.org/lkml/2007/4/11/452
http://lkml.org/lkml/2007/4/12/144

In short: we can't use attr groups since the attributes creation is conditional. And we especially don't want to use the attr groups for attrs with different modes. But it's not a problem, because...

Quoted 1 line

Or is that properly taken care of elsewhere?

Yep, userland should just listen to uevents, we're sending 'changed' event at the end of the registration. Attributes may appear and disappear dynamically, battery handling userland have to cope with that anyway.

Quoted 4 lines
Quoted 3 lines

Greg, does the patch look OK? If so, I'd like it to go via battery-2.6.git tree, along with patches that need that one.

Quoted 8 lines

Looks good with one minor problem:

drivers/base/core.c struct kset *devices_kset; · line 440

Quoted 4 lines
drivers/base/core.c +0 -0
@@ -440,6 +440,27 @@ struct kset *devices_kset;
  * device_create_file - create sysfs attribute file for device.

That should be "device_create_file_mode"

Thanks for catching! Will change.

Quoted 4 lines

Make that change and then feel free to take it through your tree with an:

on it.

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#19 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

Quoted 14 lines · Anton Vorontsov
Quoted 5 lines · Greg KH
Quoted 4 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Quoted 7 lines
Quoted 4 lines

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

But you race the creation of the device notifying userspace, and then the file being created, right?

Quoted 8 lines

Yep, you've raised that question once, like 3 years ago. :-)

http://lkml.org/lkml/2007/4/11/452
http://lkml.org/lkml/2007/4/12/144

In short: we can't use attr groups since the attributes creation is conditional. And we especially don't want to use the attr groups for attrs with different modes. But it's not a problem, because...

Groups have a filter callback for every member, to decide if the attribute should be created or not.

Kay

#20 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

Quoted 20 lines · Kay Sievers
Quoted 19 lines · Anton Vorontsov
Quoted 5 lines · Greg KH
Quoted 4 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Quoted 7 lines
Quoted 4 lines

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

But you race the creation of the device notifying userspace, and then the file being created, right?

Yep, you've raised that question once, like 3 years ago. :-)

http://lkml.org/lkml/2007/4/11/452
http://lkml.org/lkml/2007/4/12/144

Quoted 6 lines
Quoted 3 lines

In short: we can't use attr groups since the attributes creation is conditional. And we especially don't want to use the attr groups for attrs with different modes. But it's not a problem, because...

Groups have a filter callback for every member, to decide if the attribute should be created or not.

Yeah, that's how we solved that issue a long time ago :)

Can you please switch to using attribute groups now, so that userspace doesn't have to handle 'change' events?

thanks,

greg k-h

#21 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

Quoted 21 lines · Greg KH
Quoted 20 lines · Kay Sievers
Quoted 19 lines · Anton Vorontsov
Quoted 5 lines · Greg KH
Quoted 4 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Quoted 7 lines
Quoted 4 lines

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

But you race the creation of the device notifying userspace, and then the file being created, right?

Yep, you've raised that question once, like 3 years ago. :-)

http://lkml.org/lkml/2007/4/11/452
http://lkml.org/lkml/2007/4/12/144

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

In short: we can't use attr groups since the attributes creation is conditional. And we especially don't want to use the attr groups for attrs with different modes. But it's not a problem, because...

Groups have a filter callback for every member, to decide if the attribute should be created or not.

Yeah, that's how we solved that issue a long time ago :)

But not loud enough for us to notice. ;-)

Quoted 2 lines

Can you please switch to using attribute groups now, so that userspace doesn't have to handle 'change' events?

Yep.

Thanks,

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#22 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

In reply to Kay Sievers
Quoted 20 lines · Kay Sievers
Quoted 19 lines · Anton Vorontsov
Quoted 5 lines · Greg KH
Quoted 4 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Quoted 7 lines
Quoted 4 lines

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

But you race the creation of the device notifying userspace, and then the file being created, right?

Yep, you've raised that question once, like 3 years ago. :-)

http://lkml.org/lkml/2007/4/11/452
http://lkml.org/lkml/2007/4/12/144

Quoted 6 lines
Quoted 3 lines

In short: we can't use attr groups since the attributes creation is conditional. And we especially don't want to use the attr groups for attrs with different modes. But it's not a problem, because...

Groups have a filter callback for every member, to decide if the attribute should be created or not.

Thanks Kay. It seems the callback was added just a few months after the discussion above. ;-)

And this commit looks especially cool:

commit 0f4238958d28044b335644b69df6071cdb04b5ce

Author: James Bottomley <[email protected]>
Date:   Thu Mar 20 20:47:52 2008 -0500

[SCSI] sysfs: make group is_valid return a mode_t

Daniel, I think that today we can just use the attribute group mechanism, it has all needed. Do you want me to prepare a patch to convert existing attributes, or do you to try it yourself?

Just asking to not duplicate efforts.

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#23 lore raw

Re: [PATCH] Introduce {sysfs,device}_create_file_mode

Quoted 34 lines · Anton Vorontsov
Quoted 20 lines · Kay Sievers
Quoted 19 lines · Anton Vorontsov
Quoted 5 lines · Greg KH
Quoted 4 lines · Anton Vorontsov

We need to create attributes with different modes across devices. We can do this by modifying attr.mode between device_create_file invocations, but that is racy in case of globally defined attrs.

Quoted 7 lines
Quoted 4 lines

Luckily, there's sysfs_add_file_mode() function that seems to do exactly what we want, and if we use it, we don't need any locks to avoid races. Though, it isn't exposed via device-drivers core API.

But you race the creation of the device notifying userspace, and then the file being created, right?

Yep, you've raised that question once, like 3 years ago. :-)

http://lkml.org/lkml/2007/4/11/452
http://lkml.org/lkml/2007/4/12/144

Quoted 6 lines
Quoted 3 lines

In short: we can't use attr groups since the attributes creation is conditional. And we especially don't want to use the attr groups for attrs with different modes. But it's not a problem, because...

Groups have a filter callback for every member, to decide if the attribute should be created or not.

Thanks Kay. It seems the callback was added just a few months after the discussion above. ;-)

And this commit looks especially cool:

commit 0f4238958d28044b335644b69df6071cdb04b5ce

Quoted 8 lines
Author: James Bottomley <[email protected]>
Date:   Thu Mar 20 20:47:52 2008 -0500

[SCSI] sysfs: make group is_valid return a mode_t

Daniel, I think that today we can just use the attribute group mechanism, it has all needed. Do you want me to prepare a patch to convert existing attributes, or do you to try it yourself?

Would be good if you did that, just to see how this is interface meant to be used exactly. I'll adopt my patches accordingly then.

Thanks,
Daniel

#24 lore raw

PATCH 1/1 power_supply: Use attribute groups

This fixes a race between power supply device and initial attributes creation, plus makes it possible to implement writable properties.

---

On Thu, May 13, 2010 at 11:33:04AM +0200, Daniel Mack wrote:
[...]

Quoted 9 lines
Quoted 9 lines
Quoted 6 lines
Quoted 3 lines

In short: we can't use attr groups since the attributes creation is conditional. And we especially don't want to use the attr groups for attrs with different modes. But it's not a problem, because...

Groups have a filter callback for every member, to decide if the attribute should be created or not.

Thanks Kay. It seems the callback was added just a few months after the discussion above. ;-)

[...]

Quoted 6 lines
Quoted 3 lines

Daniel, I think that today we can just use the attribute group mechanism, it has all needed. Do you want me to prepare a patch to convert existing attributes, or do you to try it yourself?

Would be good if you did that, just to see how this is interface meant to be used exactly. I'll adopt my patches accordingly then.

OK. It took me quite some time as my hx4700 refused to boot. I still don't know why it doesn't boot, but I implemented test_power driver and was able to test the draft.

Daniel, it works for me, and implementing writable properties should be straightforward now (see is_visible callback).

Thanks,

 drivers/power/power_supply.h       |    7 +--
 drivers/power/power_supply_core.c  |   48 +++++++++++-----
 drivers/power/power_supply_sysfs.c |  114 ++++++++++++------------------------
 include/linux/power_supply.h       |    1 +
 4 files changed, 75 insertions(+), 95 deletions(-)
drivers/power/power_supply.h +2 -5
index f38ba48..018de2b 100644
@@ -12,15 +12,12 @@
 
 #ifdef CONFIG_SYSFS
 
-extern int power_supply_create_attrs(struct power_supply *psy);
-extern void power_supply_remove_attrs(struct power_supply *psy);
+extern void power_supply_init_attrs(struct device_type *dev_type);
 extern int power_supply_uevent(struct device *dev, struct kobj_uevent_env *env);
 
 #else
 
-static inline int power_supply_create_attrs(struct power_supply *psy)
-{ return 0; }
-static inline void power_supply_remove_attrs(struct power_supply *psy) {}
+static inline void power_supply_init_attrs(struct device_type *dev_type) {}
 #define power_supply_uevent NULL
 
 #endif /* CONFIG_SYSFS */
drivers/power/power_supply_core.c +34 -14

91 lines not on this page · raw message

drivers/power/power_supply_sysfs.c +38 -76

169 lines not on this page · raw message

include/linux/power_supply.h +1 -0
index ebd2b8f..c5f73a3 100644
@@ -114,6 +114,7 @@ enum power_supply_property {
 	POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG,
 	POWER_SUPPLY_PROP_TIME_TO_FULL_NOW,
 	POWER_SUPPLY_PROP_TIME_TO_FULL_AVG,
+	POWER_SUPPLY_PROP_TYPE, /* use power_supply.type instead */
 	/* Properties of type `const char *' */
 	POWER_SUPPLY_PROP_MODEL_NAME,
 	POWER_SUPPLY_PROP_MANUFACTURER,
Signature · 1 line
1.7.0.1
#25 lore raw

Re: [PATCH] power_supply: Use attribute groups

Hi Anton,

Quoted 3 lines · Anton Vorontsov

This fixes a race between power supply device and initial attributes creation, plus makes it possible to implement writable properties.

Thanks a lot. This works for me, but I have two minor comments below ...

[...]

Quoted 33 lines
drivers/power/power_supply_sysfs.c +8 -2
index 5b6e352..f95d934 100644
@@ -41,6 +41,9 @@ static struct device_attribute power_supply_attrs[];
 static ssize_t power_supply_show_property(struct device *dev,
 					  struct device_attribute *attr,
 					  char *buf) {
+	static char *type_text[] = {
+		"Battery", "UPS", "Mains", "USB"
+	};
 	static char *status_text[] = {
 		"Unknown", "Charging", "Discharging", "Not charging", "Full"
 	};
@@ -58,12 +61,15 @@ static ssize_t power_supply_show_property(struct device *dev,
 	static char *capacity_level_text[] = {
 		"Unknown", "Critical", "Low", "Normal", "High", "Full"
 	};
-	ssize_t ret;
+	ssize_t ret = 0;
 	struct power_supply *psy = dev_get_drvdata(dev);
 	const ptrdiff_t off = attr - power_supply_attrs;
 	union power_supply_propval value;
 
-	ret = psy->get_property(psy, off, &value);
+	if (off == POWER_SUPPLY_PROP_TYPE)
+		value.intval = psy->type;
+	else
+		ret = psy->get_property(psy, off, &value);
 
 	if (ret < 0) {
 		if (ret == -ENODATA)

drivers/power/power_supply_sysfs.c static ssize_t power_supply_show_property(struct device *dev, · line 100

Quoted 10 lines
drivers/power/power_supply_sysfs.c +3 -0
@@ -85,10 +91,13 @@ static ssize_t power_supply_show_property(struct device *dev,
 		return sprintf(buf, "%s\n", technology_text[value.intval]);
 	else if (off == POWER_SUPPLY_PROP_CAPACITY_LEVEL)
 		return sprintf(buf, "%s\n", capacity_level_text[value.intval]);
+	else if (off == POWER_SUPPLY_PROP_TYPE)
+		return sprintf(buf, "%s\n", type_text[value.intval]);
 	else if (off >= POWER_SUPPLY_PROP_MODEL_NAME)
 		return sprintf(buf, "%s\n", value.strval);
 
 	return sprintf(buf, "%d\n", value.intval);
+return 0;

This return is superflous :)

And with this approach, we don't need to initialize the .mode field in the POWER_SUPPLY_ATTR anmore.

I'll then rebase my patches for writeable properties and resend them.

Thanks,
Daniel

#26 lore raw

PATCH 1/3 power_supply: Use attribute groups

In reply to Anton Vorontsov

From: Anton Vorontsov <[email protected]>

This fixes a race between power supply device and initial attributes creation, plus makes it possible to implement writable properties.

[Daniel Mack - removed superflous return statement
and dropped .mode attribute from POWER_SUPPLY_ATTR]

---
 drivers/power/power_supply.h       |    7 +--
 drivers/power/power_supply_core.c  |   48 +++++++++++----
 drivers/power/power_supply_sysfs.c |  115 ++++++++++++------------------------
 include/linux/power_supply.h       |    1 +
 4 files changed, 75 insertions(+), 96 deletions(-)
drivers/power/power_supply.h +2 -5
index f38ba48..018de2b 100644
@@ -12,15 +12,12 @@
 
 #ifdef CONFIG_SYSFS
 
-extern int power_supply_create_attrs(struct power_supply *psy);
-extern void power_supply_remove_attrs(struct power_supply *psy);
+extern void power_supply_init_attrs(struct device_type *dev_type);
 extern int power_supply_uevent(struct device *dev, struct kobj_uevent_env *env);
 
 #else
 
-static inline int power_supply_create_attrs(struct power_supply *psy)
-{ return 0; }
-static inline void power_supply_remove_attrs(struct power_supply *psy) {}
+static inline void power_supply_init_attrs(struct device_type *dev_type) {}
 #define power_supply_uevent NULL
 
 #endif /* CONFIG_SYSFS */
drivers/power/power_supply_core.c +34 -14

91 lines not on this page · raw message

drivers/power/power_supply_sysfs.c +38 -77

172 lines not on this page · raw message

include/linux/power_supply.h +1 -0
index ebd2b8f..c5f73a3 100644
@@ -114,6 +114,7 @@ enum power_supply_property {
 	POWER_SUPPLY_PROP_TIME_TO_EMPTY_AVG,
 	POWER_SUPPLY_PROP_TIME_TO_FULL_NOW,
 	POWER_SUPPLY_PROP_TIME_TO_FULL_AVG,
+	POWER_SUPPLY_PROP_TYPE, /* use power_supply.type instead */
 	/* Properties of type `const char *' */
 	POWER_SUPPLY_PROP_MODEL_NAME,
 	POWER_SUPPLY_PROP_MANUFACTURER,
Signature · 1 line
1.7.1
#27 lore raw

PATCH 2/3 pda_power: add support for writeable properties

In reply to Anton Vorontsov

This patch adds support for writeable power supply properties and exposes them as writeable to sysfs.

A power supply implementation must implement two new function calls in order to use that feature:

int set_property(struct power_supply *psy,
enum power_supply_property psp, const union power_supply_propval *val);

int property_is_writeable(struct power_supply *psy,

                            enum power_supply_property psp);
Cc Anton Vorontsov <[email protected]>
Cc David Woodhouse <[email protected]>
Cc Alexey Starikovskiy <[email protected]>
Cc Len Brown <[email protected]>
Cc Mark Brown <[email protected]>
Cc Matt Reimer <[email protected]>
Cc Evgeniy Polyakov <[email protected]>
Cc Tejun Heo <[email protected]>
---
 drivers/power/power_supply_sysfs.c |   38 +++++++++++++++++++++++++++++++++--
 include/linux/power_supply.h       |    5 ++++
 2 files changed, 40 insertions(+), 3 deletions(-)
drivers/power/power_supply_sysfs.c +35 -3
index 6eb49ef..6a779fe 100644
@@ -33,7 +33,7 @@
 {									\
 	.attr = { .name = #_name },					\
 	.show = power_supply_show_property,				\
-	.store = NULL,							\
+	.store = power_supply_store_property,				\
 }
 
 static struct device_attribute power_supply_attrs[];
@@ -99,6 +99,29 @@ static ssize_t power_supply_show_property(struct device *dev,
 	return sprintf(buf, "%d\n", value.intval);
 }
 
+static ssize_t power_supply_store_property(struct device *dev,
+					   struct device_attribute *attr,
+					   const char *buf, size_t count) {
+	ssize_t ret;
+	struct power_supply *psy = dev_get_drvdata(dev);
+	const ptrdiff_t off = attr - power_supply_attrs;
+	union power_supply_propval value;
+	long long_val;
+
+	/* TODO: support other types than int */
+	ret = strict_strtol(buf, 10, &long_val);
+	if (ret < 0)
+		return ret;
+
+	value.intval = long_val;
+
+	ret = psy->set_property(psy, off, &value);
+	if (ret < 0)
+		return ret;
+
+	return count;
+}
+
 /* Must be in the same order as POWER_SUPPLY_PROP_* */
 static struct device_attribute power_supply_attrs[] = {
 	/* Properties of type `int' */
@@ -159,8 +182,17 @@ static mode_t power_supply_attr_is_visible(struct kobject *kobj,
 	int i;
 
 	for (i = 0; i < psy->num_properties; i++) {
-		if (psy->properties[i] == attrno)
-			return 0444;
+		int property = psy->properties[i];
+
+		if (property == attrno) {
+			mode_t mode = S_IRUSR | S_IRGRP | S_IROTH;
+
+			if (psy->property_is_writeable &&
+			    psy->property_is_writeable(psy, property) > 0)
+				mode |= S_IWUSR;
+
+			return mode;
+		}
 	}
 
 	return 0;
include/linux/power_supply.h +5 -0
index c5f73a3..30083a8 100644
@@ -145,6 +145,11 @@ struct power_supply {
 	int (*get_property)(struct power_supply *psy,
 			    enum power_supply_property psp,
 			    union power_supply_propval *val);
+	int (*set_property)(struct power_supply *psy,
+			    enum power_supply_property psp,
+			    const union power_supply_propval *val);
+	int (*property_is_writeable)(struct power_supply *psy,
+				     enum power_supply_property psp);
 	void (*external_power_changed)(struct power_supply *psy);
 	void (*set_charged)(struct power_supply *psy);
 
Signature · 1 line
1.7.1
#28 lore raw
Quoted 2 lines · Daniel Mack

This patch adds support for writeable power supply properties and exposes them as writeable to sysfs.

Please properly document this in Documentation/ABI as you are changing the userspace ABI.

thanks,

greg k-h

#29 lore raw

PATCH 1/1 power/ds2760_battery: document ABI change

Quoted 1 line

From 7ed6b078c1cb718509a0faf79ac53f768fa5cfc4 Mon Sep 17 00:00:00 2001

From: Daniel Mack <[email protected]>
Date: Tue, 18 May 2010 22:26:40 +0200
Subject: [PATCH] power/ds2760_battery: document ABI change

Add some documentation for the newly added writeable properties.

---

Quoted 10 lines · Greg KH
Quoted 2 lines · Daniel Mack

This patch adds support for writeable power supply properties and exposes them as writeable to sysfs.

Please properly document this in Documentation/ABI as you are changing the userspace ABI.

thanks,

greg k-h

Is something like the following appropriate?

 Documentation/ABI/testing/sysfs-class-power |   21 +++++++++++++++++++++
 1 files changed, 21 insertions(+), 0 deletions(-)
 create mode 100644 Documentation/ABI/testing/sysfs-class-power
Documentation/ABI/testing/sysfs-class-power new file +21 -0
new file mode 100644
index 0000000..f46ad66
@@ -0,0 +1,21 @@
+What:		/sys/class/power/ds2760-battery.*/charge_now
+Date:		May 2010
+KernelVersion:	2.6.35
+Contact:	Daniel Mack <[email protected]>
+Description:
+		This file is writeable and can be used to set the current
+		coloumb counter value inside the battery monitor chip. This
+		is needed for unavoidable corrections of aging batteries.
+		A userspace daemon can monitor the battery charging logic
+		and once the counter drops out of considerable bounds, take
+		appropriate action.
+
+What:		/sys/class/power/ds2760-battery.*/charge_full
+Date:		May 2010
+KernelVersion:	2.6.35
+Contact:	Daniel Mack <[email protected]>
+Description:
+		This file is writeable and can be used to set the assumed
+		battery 'full level'. As batteries age, this value has to be
+		amended over time.
+
Signature · 1 line
1.7.1
#30 lore raw

Re: [PATCH] power/ds2760_battery: document ABI change

Quoted 7 lines · Daniel Mack
Quoted 1 line

From 7ed6b078c1cb718509a0faf79ac53f768fa5cfc4 Mon Sep 17 00:00:00 2001

From: Daniel Mack <[email protected]>
Date: Tue, 18 May 2010 22:26:40 +0200
Subject: [PATCH] power/ds2760_battery: document ABI change

Add some documentation for the newly added writeable properties.

I added 'Suggested-by: Greg KH <[email protected]>' tag here.

Quoted 7 lines

---

Quoted 4 lines · Greg KH
Quoted 2 lines · Daniel Mack

This patch adds support for writeable power supply properties and exposes them as writeable to sysfs.

Quoted 8 lines
Quoted 6 lines

Please properly document this in Documentation/ABI as you are changing the userspace ABI.

thanks,

greg k-h

Is something like the following appropriate?

Looks good to me, as well as patches 1-3 (though in the first patch I fixed power_supply_attr_groups to be static, it was a negligence from my original patch).

I applied all these patches to battery-2.6.git, thanks!

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2
#31 lore raw

PATCH 3/3 power/ds2760_battery: make charge_now and charge_full writeable

In reply to Anton Vorontsov

For userspace tools and daemons, it might be necessary to adjust the charge_now and charge_full properties of the ds2760 battery monitor, for example for unavoidable corrections due to aging batteries.

Cc Anton Vorontsov <[email protected]>
Cc Matt Reimer <[email protected]>
Cc Evgeniy Polyakov <[email protected]>
Cc Tejun Heo <[email protected]>
Cc David Woodhouse <[email protected]>
Cc Alexey Starikovskiy <[email protected]>
Cc Len Brown <[email protected]>
Cc Mark Brown <[email protected]>
---
 drivers/power/ds2760_battery.c |   64 ++++++++++++++++++++++++++++++++++++++++
 1 files changed, 64 insertions(+), 0 deletions(-)
drivers/power/ds2760_battery.c +64 -0
index 3bf8d1f..4d3b272 100644
@@ -304,6 +304,28 @@ static void ds2760_battery_write_rated_capacity(struct ds2760_device_info *di,
 	w1_ds2760_recall_eeprom(di->w1_dev, DS2760_EEPROM_BLOCK1);
 }
 
+static void ds2760_battery_write_active_full(struct ds2760_device_info *di,
+					     int active_full)
+{
+	unsigned char tmp[2] = {
+		active_full >> 8,
+		active_full & 0xff
+	};
+
+	if (tmp[0] == di->raw[DS2760_ACTIVE_FULL] &&
+	    tmp[1] == di->raw[DS2760_ACTIVE_FULL + 1])
+		return;
+
+	w1_ds2760_write(di->w1_dev, tmp, DS2760_ACTIVE_FULL, sizeof(tmp));
+	w1_ds2760_store_eeprom(di->w1_dev, DS2760_EEPROM_BLOCK0);
+	w1_ds2760_recall_eeprom(di->w1_dev, DS2760_EEPROM_BLOCK0);
+
+	/* Write to the di->raw[] buffer directly - the DS2760_ACTIVE_FULL
+	 * values won't be read back by ds2760_battery_read_status() */
+	di->raw[DS2760_ACTIVE_FULL] = tmp[0];
+	di->raw[DS2760_ACTIVE_FULL + 1] = tmp[1];
+}
+
 static void ds2760_battery_work(struct work_struct *work)
 {
 	struct ds2760_device_info *di = container_of(work,
@@ -426,6 +448,45 @@ static int ds2760_battery_get_property(struct power_supply *psy,
 	return 0;
 }
 
+static int ds2760_battery_set_property(struct power_supply *psy,
+				       enum power_supply_property psp,
+				       const union power_supply_propval *val)
+{
+	struct ds2760_device_info *di = to_ds2760_device_info(psy);
+
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
+		/* the interface counts in uAh, convert the value */
+		ds2760_battery_write_active_full(di, val->intval / 1000L);
+		break;
+
+	case POWER_SUPPLY_PROP_CHARGE_NOW:
+		/* ds2760_battery_set_current_accum() does the conversion */
+		ds2760_battery_set_current_accum(di, val->intval);
+		break;
+
+	default:
+		return -EPERM;
+	}
+
+	return 0;
+}
+
+static int ds2760_battery_property_is_writeable(struct power_supply *psy,
+						enum power_supply_property psp)
+{
+	switch (psp) {
+	case POWER_SUPPLY_PROP_CHARGE_FULL:
+	case POWER_SUPPLY_PROP_CHARGE_NOW:
+		return 1;
+
+	default:
+		break;
+	}
+
+	return 0;
+}
+
 static enum power_supply_property ds2760_battery_props[] = {
 	POWER_SUPPLY_PROP_STATUS,
 	POWER_SUPPLY_PROP_VOLTAGE_NOW,
@@ -460,6 +521,9 @@ static int ds2760_battery_probe(struct platform_device *pdev)
 	di->bat.properties	= ds2760_battery_props;
 	di->bat.num_properties	= ARRAY_SIZE(ds2760_battery_props);
 	di->bat.get_property	= ds2760_battery_get_property;
+	di->bat.set_property	= ds2760_battery_set_property;
+	di->bat.property_is_writeable =
+				  ds2760_battery_property_is_writeable;
 	di->bat.set_charged	= ds2760_battery_set_charged;
 	di->bat.external_power_changed =
 				  ds2760_battery_external_power_changed;
Signature · 1 line
1.7.1
#32 lore raw
In reply to Daniel Mack

On Tue, May 11, 2010 at 07:58:12PM +0200, Daniel Mack wrote:
[...]

Quoted 4 lines
Quoted 1 line

Plus, that way you don't need is_writable().

Ugh, really? I would _much_ prefer to actually _see_ which property is writeable, just from looking at the file attributes in sysfs.

Well, yeah... that would be also good for userland apps (GUI apps, in particular). Though, I'm not yet sure how to implement it without modifying a global array...

To avoid the race that I described in previous email we could insert some mutex, but I'd like to avoid the global stuff.

Signature · 3 lines
Anton Vorontsov
email: [email protected]
irc://irc.freenode.net/bd2