[PATCH 01/10] dt-bindings: bus: Minimal TI sysc interconnect target module binding

Tony Lindgren
2017-09-25T17:44:14Z

* Matthijs van Duin <matthijsvanduin@gmail.com> [170925 10:22]:
> On Mon, Sep 25, 2017 at 07:25:20AM -0700, Tony Lindgren wrote:
> > * Matthijs van Duin <matthijsvanduin@gmail.com> [170924 23:36]:
> > > Is the meaning of these documented anywhere? I'm assuming one of them
> > > corresponds to the standard omap2/3 sysconfig/sysstatus
> >
> > Yes that's the type1 sysc.
> >
> > > and one to the standard omap4/5 sysconfig
> >
> > Yeah and that's what we call sysc type 2 in the kernel.
>
> Might it then not make more sense to call those something like
> ti,omap2-sysc and ti,omap4-sysc respectively?

OK that's a good idea.

> > The sysc type3 is what we have on am335x/ti81xx, see:
> >
> > $ git grep -B10 -A1 "&omap_hwmod_sysc_type3" arch/arm/mach-omap2
>
> Ah... three "foreign" modules with an idlemode carelessly thrown into a
> register without care for existing layouts. I think these are more just
> exceptional cases which happen to agree by coincidence since they all
> just added idlemode in the simplest way possible, but I can understand
> how it came to be viewed as a standard type.

So we shall then name this fine centauroid sysc ti,81xx-sysc?

> > > ISS (omap4/5, dm814x) is also fun since it has top-level sysconfig, but
> > > most of the child modules (e.g. isp5 and simcop) also have their own
> > > sysconfig, and some child modules of simcop again have sysconfig.
> >
> > Interesting. Sounds like there's yet another interconnect instance
> > lurking there similar to L4 ABE?
>
> ISS has a 32-bit configuration interconnect and a 64/128-bit data
> interconnect:
> .......................................
> : ISS :
> : :
> L3 --:--> configuration interconnect <-------:-- Cortex-M3/M4 subsystem
> : |||||||||| | | :
> : vvvvvvvvvv | | :
> : submodules | '---. :
> : |||||||| | | :
> : vvvvvvvv v v :
> : data interconnect --> BTE --> CBUFF --:--> L3
> '.......................................'
>
> It also has a local prcm controller to manage all this, and an irq
> combiner. See the section "ISS Power Management" (8.1.2.4 in the public
> omap5 TRM, SWPU249AF) for a better diagram of all this. The various
> versions of ISS differ somewhat in the submodules but all share the same
> overall structure.

OK thanks for the pointer.

> One of the ISS submodules, SIMCOP, is itself again a fairly complicated
> subsystem with two local interconnects, of which you can find a block
> diagram in the "ISS Still Image Coprocessor" chapter (8.4).

OK

> Having a local interconnect is itself not a particularly rare thing (you
> can find one in ABE, DSS, CPSW, PRUSS, PWMSS, etc), but ISS does have
> unusual complexity with its multiple interconnects and nested subsystems.

OK

Regards,

Tony