[RFC PATCH v2 0/6] TI81XX: Add clock and hwmod data
paul at pwsan.com
Wed Oct 5 13:37:04 EDT 2011
On Wed, 5 Oct 2011, Pedanekar, Hemant wrote:
> Paul Walmsley wrote on Tuesday, October 04, 2011 2:54 PM:
> > I've been spending some time with these patches. A few aspects don't make
> > much sense to me. For example, looking at the TRMs, the 816x doesn't seem
> > to have powerdomains for HDVICP0, 1, or 2, although they are listed in the
> > patch.
> Can you please check 18.2.1 in TRM from .
> Above powerdomains are listed there as HDVICP2-0, 1, 2.
I see them there in SPRUGX8. But the most recent revision of the 816x TRM
is SPRUGX9, correct?
SPRUGX9 doesn't list these three powerdomains.
If they're really there, then we should definitely keep your original data
based on SPRUGX8. Maybe you could get some clarification on that from the
> > Will send over the current reworked patches for TI81XX PRCM accessors,
> > powerdomain code & data, and clockdomain code & data. They are intended
> > to apply over the TI814x patches that you sent recently. I'd like to get
> > your opinion(s) on these reworked patches. Please note, so far they have
> > only been compile-tested.
> Thanks, I will try those and respond.
Since they've only been compile-tested so far, they are unlikely to boot.
What I'm most interested in at this point are any comments you might have
about the general approach. For example:
1. considering the first patch, it would be good to get your views on my
A. the TI81xx PRCM is effectively a single IP block, with a single
interconnect target port, with multiple internal PRM/CM instances mixed in
the same IP block;
B. that in some of the internal PRM and CM instances, the register layout
is identical between 816x and 814x, and that those macros, etc. should be
shared; with the 816x-specific macros split into an 816x-specific file and
the 814x-specific macros split into an 814x-specific file;
C. the CM register structure is closer to the OMAP4430 CM register
structure than it is to OMAP3, with the important exception that the
CLKSTCTRL and CLKCTRL registers are not grouped together for each
clockdomain. Instead, all of the the CLKSTCTRL registers are grouped
together, followed by the CLKCTRL registers all grouped together, and
therefore, the OMAP4 *_CDOFFS & OMAP3 *_CLKDM* macro style is basically
2. considering the second and fourth patches,
A. that given the different power management functionality of TI81xx
compared to OMAP4 & OMAP3, that it makes sense to create a new
powerdomain/clockdomain code implementation file, rather than attempting
to modify the OMAP2/3 file;
B. that we should discuss whether it makes sense to remove the powerdomain
names from the clockdomain names, if we can share clock nodes or hwmod
nodes for L3_MED and L3_SLOW between 814x and 816x;
3. considering the third and fifth patches,
A. that the modified powerdomain and clockdomain data (per SPRUGX9) is
correct vs the SPRUGX8 data;
B. that the 814x powerdomains/clockdomains that have been added are
More information about the linux-arm-kernel