On Fri, Sep 29, 2017 at 03:34:05PM -0700, Tony Lindgren wrote: > With the recently introduced omap clkctrl module binding, we can start > moving omap hwmod data to device tree and drivers from arch/arm/mach-omap2. > > To start doing this, let's introduce a device tree binding for TI > sysc interconnect target module hardware. The sysc manages module clocks, > idlemodes and interconnect level resets. Each interconnect target module > can have one or more child devices connected to it. > > TI sysc interconnect target module hardware is independent of the > interconnect. It is used at least with TI L3 interconnect (Arteris NoC) > and TI L4 interconnect (Sonics s3220). The sysc is mostly used for > interaction between module and PRCM. It participates in the OCP Disconnect > Protocol but other than that is mostly indepenent of the interconnect. > > As all the features may not be supported for a given sysc module, we > need to use device tree configuration for the revision of the interconnect > target module. > > Note that the interconnect target module control registers are always > sprinked at varying locations in the unused address space of the first > child device IP block. To avoid device tree reg conflicts, the sysc device > provides ranges for it's children. > > For a non-intrusive transition from static hwmod data to using device > tree defined TI interconnect target module binding, we can keep things > working with static hwmod data if device tree property "ti,hwmods" is > specified for the the interconnect target module. > > Note that additional properties for sysc capabilities will be added > later on. For now, we can already use this binding for interconnect > target modules that do not have any child device drivers available. > This allows us to idle the unused interconnect target modules during > init without the need for legacy hwmod platform data for doing it. > > Cc: Benoît Cousson <bcousson@xxxxxxxxxxxx> > Cc: Dave Gerlach <d-gerlach@xxxxxx> > Cc: Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx> > Cc: Liam Girdwood <lgirdwood@xxxxxxxxx> > Cc: Mark Brown <broonie@xxxxxxxxxx> > Cc: Mark Rutland <mark.rutland@xxxxxxx> > Cc: Mauro Carvalho Chehab <mchehab@xxxxxxxxxx> > Cc: Nishanth Menon <nm@xxxxxx> > Cc: Matthijs van Duin <matthijsvanduin@xxxxxxxxx> > Cc: Paul Walmsley <paul@xxxxxxxxx> > Cc: Peter Ujfalusi <peter.ujfalusi@xxxxxx> > Cc: Rob Herring <robh+dt@xxxxxxxxxx> > Cc: Sakari Ailus <sakari.ailus@xxxxxx> > Cc: Suman Anna <s-anna@xxxxxx> > Cc: Tero Kristo <t-kristo@xxxxxx> > Cc: Tomi Valkeinen <tomi.valkeinen@xxxxxx> > Signed-off-by: Tony Lindgren <tony@xxxxxxxxxxx> > --- > Documentation/devicetree/bindings/bus/ti-sysc.txt | 93 +++++++++++++++++++++++ > 1 file changed, 93 insertions(+) > create mode 100644 Documentation/devicetree/bindings/bus/ti-sysc.txt One typo below, otherwise: Reviewed-by: Rob Herring <robh@xxxxxxxxxx> > diff --git a/Documentation/devicetree/bindings/bus/ti-sysc.txt b/Documentation/devicetree/bindings/bus/ti-sysc.txt > new file mode 100644 > --- /dev/null > +++ b/Documentation/devicetree/bindings/bus/ti-sysc.txt > @@ -0,0 +1,93 @@ > +Texas Instruments sysc interconnect target module wrapper binding > + > +Texas Instruments SoCs can have a generic interconnect target module > +hardware for devices connected to various interconnects such as L3 > +interconnect (Arteris NoC) and L4 interconnect (Sonics s3220). The sysc > +is mostly used for interaction between module and PRCM. It participates > +in the OCP Disconnect Protocol but other than that is mostly indepenent s/indepenent/independent/ > +of the interconnect. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
