From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH v6 17/25] gpio/omap: use pm-runtime framework Date: Fri, 09 Sep 2011 11:04:05 -0700 Message-ID: <87pqj9y4mi.fsf@ti.com> References: <1314798161-19523-1-git-send-email-tarun.kanti@ti.com> <1314798161-19523-18-git-send-email-tarun.kanti@ti.com> <87ehztxmcg.fsf@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from na3sys009aog103.obsmtp.com ([74.125.149.71]:59051 "EHLO na3sys009aog103.obsmtp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759479Ab1IISEO convert rfc822-to-8bit (ORCPT ); Fri, 9 Sep 2011 14:04:14 -0400 Received: by mail-gy0-f171.google.com with SMTP id 3so660044gyh.16 for ; Fri, 09 Sep 2011 11:04:13 -0700 (PDT) In-Reply-To: (Tarun Kanti DebBarma's message of "Fri, 9 Sep 2011 18:02:33 +0530") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "DebBarma, Tarun Kanti" Cc: linux-omap@vger.kernel.org, tony@atomide.com, linux-arm-kernel@lists.infradead.org, Charulatha V "DebBarma, Tarun Kanti" writes: > [...] >>> >>> +static const struct dev_pm_ops gpio_pm_ops =3D { >>> + =C2=A0 =C2=A0 .suspend =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0=3D omap_gpio_suspend, >>> + =C2=A0 =C2=A0 .resume =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =3D omap_gpio_resume, >>> +}; >> >> Please use SET_SYSTEM_SLEEP_PM_OPS(). =C2=A0See > We can use following macro to initialize .suspend and .resume callbac= ks. > But how do we initialize .runtime_suspend and .runtime_resume callbac= ks? > > #define SIMPLE_DEV_PM_OPS(name, suspend_fn, resume_fn) \ > const struct dev_pm_ops name =3D { \ > SET_SYSTEM_SLEEP_PM_OPS(suspend_fn, resume_fn) \ > } > > Do we have something similar to following where we can assign separat= e > pair of callbacks? SET_RUNTIME_PM_OPS() Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html