[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110406160654.e629dfde.ospite@studenti.unina.it>
Date: Wed, 6 Apr 2011 16:06:54 +0200
From: Antonio Ospite <ospite@...denti.unina.it>
To: Johannes Berg <johannes@...solutions.net>
Cc: linux-wireless@...r.kernel.org, openezx-devel@...ts.openezx.org,
"John W . Linville" <linville@...driver.com>,
Liam Girdwood <lrg@...mlogic.co.uk>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>,
linux-kernel@...r.kernel.org, Marek Vasut <marek.vasut@...il.com>,
Guiming Zhuo <gmzhuo@...il.com>
Subject: Re: [PATCH] rfkill: Regulator consumer driver for rfkill
On Wed, 06 Apr 2011 11:29:38 +0200
Johannes Berg <johannes@...solutions.net> wrote:
> On Wed, 2011-04-06 at 11:21 +0200, Antonio Ospite wrote:
>
> > + if (regulator_is_enabled(vcc)) {
> > + dev_dbg(&pdev->dev, "Regulator already enabled\n");
> > + rfkill_data->reg_enabled = 1;
> > + }
> > + rfkill_init_sw_state(rf_kill, !rfkill_data->reg_enabled);
> > +
> > + ret = rfkill_register(rf_kill);
>
> We recently had a thread about how rfkill_init_sw_state() isn't quite
> working the right way. Also, it is indented to be used for devices that
> keep their state over resume. I think you should remove it here and rely
> on rfkill to sync you after registration.
>
> Cf. the long thread here:
> http://thread.gmane.org/gmane.linux.acpi.devel/49577
>
Ok, but I still need to replace that call with a rfkill_set_sw_state()
to expose the initial status of the regulator to the rfkill system,
right?
> Other than that, no comments from me from an rfkill POV.
>
> johannes
>
Thanks I am waiting a couple of days before sending a v2.
Regards,
Antonio
--
Antonio Ospite
http://ao2.it
PGP public key ID: 0x4553B001
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists