All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Anton Vorontsov <cbouatmailru@gmail.com>,
	Greg KH <gregkh@suse.de>, Kay Sievers <kay.sievers@vrfy.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Maciej Rutecki <maciej.rutecki@gmail.com>
Subject: Re: [Regression] Commit "power_supply: Use attribute groups" breaks KDE battery monitor on openSUSE 11.3 M6
Date: Tue, 25 May 2010 09:08:44 +0200	[thread overview]
Message-ID: <20100525070844.GV30801@buzzloop.caiaq.de> (raw)
In-Reply-To: <201005250255.11924.rjw@sisk.pl>

On Tue, May 25, 2010 at 02:55:11AM +0200, Rafael J. Wysocki wrote:
> On Tuesday 25 May 2010, Daniel Mack wrote:
> > On Tue, May 25, 2010 at 02:20:45AM +0200, Rafael J. Wysocki wrote:
> > > On Tuesday 25 May 2010, Rafael J. Wysocki wrote:
> > > > On Tuesday 25 May 2010, Daniel Mack wrote:
> > > > > On Tue, May 25, 2010 at 12:28:24AM +0200, Rafael J. Wysocki wrote:
> > > > > > Your commit 5f487cd34f4337f9bc27ca19da72a39d1b0a0ab4 (power_supply: Use
> > > > > > attribute groups) unfortunately breaks KDE 4.4's battery monitor from openSUSE
> > > > > > 11.3 Milestone 6 on my Acer Ferrari One.  Apparently, the battery monitor can't
> > > > > > access the sysfs battery attributes with this commit applied.
> > > > > 
> > > > > Can you still see the attributes in sysfs?
> > > > 
> > > > Yes, I can.
> > > 
> > > Ah, sorry.  The 'type' property is not present (I didn't notice that before).
> > 
> > Ah. That I didn't see. Does the (untested) patch below help?
> > 
> > Daniel
> > 
> > From ea5c518fb287d5e80e9a46ba1f9a17c45141187c Mon Sep 17 00:00:00 2001
> > From: Daniel Mack <daniel@caiaq.de>
> > Date: Tue, 25 May 2010 02:39:45 +0200
> > Subject: [PATCH] power_supply: fix regression for 'type' property
> > 
> > Commit 5f487cd34f4337f9bc27ca19da72a39d1b0a0ab4 (power_supply: Use
> > attribute groups) causes a regression the power supply core does not
> > export the 'type' attribute anymore.
> > 
> > POWER_SUPPLY_PROP_TYPE is handled by the power supply core without the
> > low-level driver, so power_supply_attr_is_visible() must always return
> > the entry as readable.
> > 
> > Signed-off-by: Daniel Mack <daniel@caiaq.de>
> > Reported-by: Rafael J. Wysocki <rjw@sisk.pl>
> 
> Yes, that's it, thanks.

Good, thanks for testing.

I think Anton will pick this for battery-2.6.git.


Daniel


> >  drivers/power/power_supply_sysfs.c |    6 ++++--
> >  1 files changed, 4 insertions(+), 2 deletions(-)
> > 
> > diff --git a/drivers/power/power_supply_sysfs.c b/drivers/power/power_supply_sysfs.c
> > index 6a86cdf..9d30eeb 100644
> > --- a/drivers/power/power_supply_sysfs.c
> > +++ b/drivers/power/power_supply_sysfs.c
> > @@ -179,14 +179,16 @@ static mode_t power_supply_attr_is_visible(struct kobject *kobj,
> >  {
> >  	struct device *dev = container_of(kobj, struct device, kobj);
> >  	struct power_supply *psy = dev_get_drvdata(dev);
> > +	mode_t mode = S_IRUSR | S_IRGRP | S_IROTH;
> >  	int i;
> >  
> > +	if (attrno == POWER_SUPPLY_PROP_TYPE)
> > +		return mode;
> > +
> >  	for (i = 0; i < psy->num_properties; i++) {
> >  		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;
> > 
> 

  reply	other threads:[~2010-05-25  7:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 22:28 [Regression] Commit "power_supply: Use attribute groups" breaks KDE battery monitor on openSUSE 11.3 M6 Rafael J. Wysocki
2010-05-24 22:32 ` Daniel Mack
2010-05-24 23:03   ` Rafael J. Wysocki
2010-05-25  0:20     ` Rafael J. Wysocki
2010-05-25  0:47       ` Daniel Mack
2010-05-25  0:55         ` Rafael J. Wysocki
2010-05-25  7:08           ` Daniel Mack [this message]
2010-05-25 10:27             ` [GIT PULL] battery-2.6.git Anton Vorontsov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100525070844.GV30801@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=akpm@linux-foundation.org \
    --cc=cbouatmailru@gmail.com \
    --cc=gregkh@suse.de \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.