summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorBenoit Cousson <b-cousson@ti.com>2011-07-10 05:56:29 -0600
committerPaul Walmsley <paul@pwsan.com>2011-07-10 05:56:29 -0600
commita5322c6f3a3b0a81347c57de2f3a86b851b49bcf (patch)
tree40eef11d93a8ea7213e8bc2084a9e570478038bf /net
parentc84584139aaeef7631df152e13cbf319d8e55950 (diff)
downloadblackbird-op-linux-a5322c6f3a3b0a81347c57de2f3a86b851b49bcf.tar.gz
blackbird-op-linux-a5322c6f3a3b0a81347c57de2f3a86b851b49bcf.zip
OMAP4: hwmod data: Add clock domain attribute
In OMAP PRCM terminology, the clock domain is defined as a group of IPs that share some clocks and most of the time an interface clock. Every IP does belong to a clockdomain. For the moment the clock domain attribute is affected to a clock node. The issue with that approach, is that a clock might or not belong to a clock domain. Moreover during module transition, it is up to a module to handle properly the clock domain state and not to a clock node. Create a clkdm_name attribute to provide this information per hwmod. Populate this attribute for every OMAP4 hwmod entries. Future cleanup series with remove that information from the OMAP4 clock when it is relevant. Signed-off-by: Benoit Cousson <b-cousson@ti.com> Cc: Paul Walmsley <paul@pwsan.com> Cc: Rajendra Nayak <rnayak@ti.com> [paul@pwsan.com: fix the mpuss_clkdm name] Signed-off-by: Paul Walmsley <paul@pwsan.com>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud