Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752521AbaJIIhr (ORCPT ); Thu, 9 Oct 2014 04:37:47 -0400 Received: from filter1.ibarracuda.nl ([83.247.7.10]:50295 "EHLO filter1.ibarracuda.nl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750873AbaJIIhg (ORCPT ); Thu, 9 Oct 2014 04:37:36 -0400 X-ASG-Debug-ID: 1412843853-0759e748282737c0002-xx1T2L X-Barracuda-Envelope-From: Frans.Klaver@xsens.com X-Barracuda-AUTH-User: xsenscom X-Barracuda-Apparent-Source-IP: 87.249.116.215 Date: Thu, 9 Oct 2014 10:37:31 +0200 From: Frans Klaver To: Guenter Roeck CC: Sebastian Reichel , Subject: Re: [PATCH v3 1/2] power: reset: add LTC2952 poweroff support Message-ID: <20141009083731.GB3588@ci00147.xsens-tech.local> X-ASG-Orig-Subj: Re: [PATCH v3 1/2] power: reset: add LTC2952 poweroff support References: <1412584836-27677-1-git-send-email-frans.klaver@xsens.com> <1412584836-27677-2-git-send-email-frans.klaver@xsens.com> <20141006213210.GA11926@roeck-us.net> <20141007081544.GA25568@ci00147.xsens-tech.local> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline In-Reply-To: <20141007081544.GA25568@ci00147.xsens-tech.local> User-Agent: Mutt/1.5.23 (2014-03-12) X-Originating-IP: [172.16.11.125] X-Barracuda-Connect: rev-215.116.249.87.virtu.nl[87.249.116.215] X-Barracuda-Start-Time: 1412843853 X-Barracuda-Encrypted: AES128-SHA X-Barracuda-URL: http://filter1.ibarracuda.nl:8000/cgi-mod/mark.cgi X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using per-user scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=5.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.10367 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 07, 2014 at 10:15:44AM +0200, Frans Klaver wrote: > On Mon, Oct 06, 2014 at 02:32:10PM -0700, Guenter Roeck wrote: > > On Mon, Oct 06, 2014 at 10:40:35AM +0200, Frans Klaver wrote: > > > +static struct platform_driver ltc2952_poweroff_driver = { > > > + .probe = ltc2952_poweroff_probe, > > > + .remove = ltc2952_poweroff_remove, > > > + .driver = { > > > + .name = "ltc2952-poweroff", > > > + .owner = THIS_MODULE, > > > + .of_match_table = of_ltc2952_poweroff_match, > > > + }, > > > + .suspend = ltc2952_poweroff_suspend, > > > + .resume = ltc2952_poweroff_resume, > > > > I think you are supposed to put the suspend and resume calls into the driver > > structure. The platform code names the callbacks here 'legacy'. > > I'll check that out. They are supposed to go into a pm_ops structure, which is pointed at in driver's pm pointer. I'll drop them in any case. It would lead to a bunch of boiler plate for nothing. Frans -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/