From: Francesco VIRLINZI <francesco.virlinzi@st.com>
To: linux-pm@lists.linux-foundation.org
Subject: In Embedded system the dev_pm_info.power_state is useful
Date: Fri, 23 May 2008 07:56:51 +0200 [thread overview]
Message-ID: <48365CA3.4070808@st.com> (raw)
Hi all
I'm Francesco Virlinzi and I work in STMicroelectronics, I'm a
developers of STLinux (www.stlinux.com) an
embedded Linux distribution for ST Set Top Box.
I read in the pm mail list that you are going to remove in the kernel the
dev_pm_info.power_state field in the dev_pm_info struct replaced by
bus-specific field.
My request is: don't do that.
In embedded system it' s really useful because there are a lot of
generic IP on a single bus (the pltaform bus)
and the only way to check the power state of each IP is based on
'dev_pm_info.power_state'
without this filed we will have our IP (platform_device) with no power
state concept...
At least we could put it under CONFIG_EMBEDDED.
What do you know?
Regards
Francesco
next reply other threads:[~2008-05-23 5:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 5:56 Francesco VIRLINZI [this message]
2008-05-23 6:17 ` In Embedded system the dev_pm_info.power_state is useful Francesco VIRLINZI
2008-05-23 14:07 ` Alan Stern
2008-05-23 14:32 ` Francesco VIRLINZI
2008-05-23 18:19 ` Alan Stern
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=48365CA3.4070808@st.com \
--to=francesco.virlinzi@st.com \
--cc=linux-pm@lists.linux-foundation.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox