linux-kernel - i2c runtime suspend and system wide suspend

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

Message-ID: <4D1C0CFE.5010008@codeaurora.org>
Date:	Wed, 29 Dec 2010 20:39:26 -0800
From:	Abhijeet Dharmapurikar <adharmap@...eaurora.org>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
CC:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Jean Delvare <khali@...ux-fr.org>,
	Rajendra Nayak <rnayak@...com>,
	Kevin Hilman <khilman@...prootsystems.com>,
	Vishwanath BS <vishwanath.bs@...com>,
	Partha Basak <p-basak2@...com>, linux-kernel@...r.kernel.org,
	linux-arm-msm@...r.kernel.org
Subject: i2c runtime suspend and system wide suspend

The i2c-core driver mixes runtime suspend and system wide suspend, in 
that, during a system wide suspend, it skips calling ->suspend if the 
device is runtime suspended.

I have an interrupt controller running over the i2c bus and that driver 
is oblivious of the runtime pm framework, IOW, it doesn't do any runtime 
pm calls. CONFIG_RUNTIME_PM is enabled however (for some other bus 
drivers). The issue I am facing is that all such i2c devices are assumed 
runtime suspended and the ->suspend for these devices is not invoked 
during systemwide suspend.

Looking around in pci and platform busses, they don't skip calling the 
->suspend callback, actually, they dont check if the device is runtime 
suspended.

The question is, why do we have this special check in i2c bus driver?

Pasted below is the relevant commit.

commit 2f60ba706bd9af84c4eab704243b262e69556f2e

     i2c: Fix bus-level power management callbacks

     There are three issues with the i2c bus type's power management
     callbacks at the moment.  ....
     ....
     ....
     ....  Finally, the system sleep PM
     (ie. suspend/resume) callbacks don't check if the device has been
     already suspended at run time, in which case they should skip
     suspending it.  Also, it looks like the i2c bus type can use the
     generic subsystem-level runtime PM callbacks.

     For these reasons, rework the system sleep PM callbacks provided by
     the i2c bus type to handle hibernation correctly and to invoke the
     "legacy" callbacks for drivers that provide them.  In addition to
     that make the i2c bus type use the generic subsystem-level runtime
     PM callbacks.

Thanks,
Abhijeet

--
Sent by an employee of Qualcomm Innovation Center, Inc. The Qualcomm 
Innovation Center, Inc. is a member of Code Aurora Forum.


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