All of lore.kernel.org
 help / color / mirror / Atom feed
From: Francesco VIRLINZI <francesco.virlinzi@st.com>
To: linux-pm@lists.linux-foundation.org
Subject: Info on LDM, domain system and SOCs
Date: Wed, 05 Sep 2007 13:54:39 +0000	[thread overview]
Message-ID: <46DEB51F.3010000@st.com> (raw)

Hi all
I'm looking the Linux Driver Model (LDM) and the PM issues.

I see the LDM is only "bus-oriented".
Is there an "official" reason why it doesn't track clock and voltage?

In a SOCs usually there is more than one clock therefore it could be 
useful track not only the clock (as already done by the linux/clock.h) 
but also the relationship between clock-and-device.

For this reason I'm working on a generic framework domain (to track 
clocks and voltage with the same API) and the relationship between 
domains and devices.

The basic idea is something like:

struct device_driver {
    ...
    domain_ret_t (*domain_notifier)(struct domain_event * event, struct 
device* dev);
};

struct device {
    ...
    struct dev_dmn_info     clk;
    struct dev_dmn_info     vltg;
};

And in the future it tries to have a dynamic power management with all 
the info the system has on each device (bus_type, parent_device, 
clock_parent, voltage_parent).

Do you think is it a good idea? (if no why?)
Did somebody do something like that? (if no why?)

Ciao
 Francesco

             reply	other threads:[~2007-09-05 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-05 13:54 Francesco VIRLINZI [this message]
2007-09-10 13:17 ` Info on LDM, domain system and SOCs Igor Stoppa
2007-09-10 16:19   ` Francesco VIRLINZI
2007-09-17 21:17     ` Amit Kucheria
2007-09-24 11:14       ` Francesco VIRLINZI
2007-09-24  9:29         ` Igor Stoppa
2007-09-24 10:05         ` Amit Kucheria

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=46DEB51F.3010000@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 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.