From: "Peter 'p2' De Schrijver" <peter.de-schrijver@nokia.com>
To: ext Lesly Arackal Manuel <leslyam@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
'Lesly A M' <x0080970@ti.com>, 'Nishanth Menon' <nm@ti.com>,
'David Derrick' <dderrick@ti.com>,
'Samuel Ortiz' <sameo@linux.intel.com>
Subject: Re: [PATCH v5 3/5] omap3: pm: Generic TRITON power scripts forOMAP3 based boards
Date: Mon, 17 May 2010 13:58:33 +0300 [thread overview]
Message-ID: <20100517105833.GA4736@codecarver.research.nokia.com> (raw)
In-Reply-To: <015501caf28a$5a984e20$ba8818ac@apr.dhcp.ti.com>
Hi,
>
> Hi Peter,
>
> The RES_TYPE field is same for all messages.
>
> The resource which can go to low-power mode with clk_req sig de-asserting is
> configured as RES_TYPE2 = '2'. And the resource which can go to low-power
> mode with sys_off sig de-asserting is configured as RES_TYPE2 = '1'.
>
> The RES_TYPE2 is '2' for P3 wakeup and the msg will applicable for Resource
> which have their TYPE2 field configured '2' (RES_VINTANA1, RES_VINTANA2,
> RES_VINTDIG, VIO, RES_CLKEN, RES_HFCLKOUT).
>
> RES_TYPE2 = '1' for P1_P2 wakeup.
> (Applicable for res: RES_VPLL1, RES_VDD1, RES_VDD2, RES_REGEN,
> RES_NRES_PWRON, RES_SYSEN)
>
Ok. But why not just assign the resources to the appropriate groups ?
Eg. assign VIO to P3 and assign VPLL1 to P1_P2 ? Then you only need one
message type. Also, why are you using RES_TYPE2 instead of RES_TYPE ?
Cheers,
Peter.
--
goa is a state of mind
next prev parent reply other threads:[~2010-05-17 10:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 11:43 [PATCH v5 3/5] omap3: pm: Generic TRITON power scripts for OMAP3 based boards Lesly A M
2010-05-10 14:30 ` Peter 'p2' De Schrijver
2010-05-13 10:52 ` [PATCH v5 3/5] omap3: pm: Generic TRITON power scripts forOMAP3 " Lesly Arackal Manuel
2010-05-17 10:58 ` Peter 'p2' De Schrijver [this message]
2010-05-18 8:48 ` [PATCH v5 3/5] omap3: pm: Generic TRITON power scriptsforOMAP3 " Lesly Arackal Manuel
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=20100517105833.GA4736@codecarver.research.nokia.com \
--to=peter.de-schrijver@nokia.com \
--cc=dderrick@ti.com \
--cc=leslyam@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=sameo@linux.intel.com \
--cc=x0080970@ti.com \
/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.