[RFC PATCH 03/10] documentation/dt: Add l3-noc bindings
b-cousson at ti.com
Thu Sep 8 20:18:47 EDT 2011
On 9/8/2011 8:06 PM, Grant Likely wrote:
> On Wed, Aug 24, 2011 at 03:09:09PM +0200, Benoit Cousson wrote:
>> Add documentation for the l3-noc bindings.
>> Signed-off-by: Benoit Cousson<b-cousson at ti.com>
>> Cc: Randy Dunlap<rdunlap at xenotime.net>
>> .../devicetree/bindings/arm/omap/l3-noc.txt | 18 ++++++++++++++++++
>> 1 files changed, 18 insertions(+), 0 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/arm/omap/l3-noc.txt
>> diff --git a/Documentation/devicetree/bindings/arm/omap/l3-noc.txt b/Documentation/devicetree/bindings/arm/omap/l3-noc.txt
>> new file mode 100644
>> index 0000000..dbfa878
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/arm/omap/l3-noc.txt
>> @@ -0,0 +1,18 @@
>> +* TI - L3 Network On Chip (NoC)
>> +This version is an implementation of the generic NoC IP
>> +provided by Arteris.
> Hahaha. Here's the documentation. Okay.
>> +Required properties:
>> +- compatible : Should be "ti,l3-noc", "arteris,noc"
> Should probably be "ti,omap4-l3-noc", and it isn't necessary to have a
> value for the IP core vendor... or at least if an arteris value is
> provided, then it should have some form of ip-core version
OK, in that case, the noc version is clearly not obvious to get, so I'll
get rid of that compatible value.
>> +- hwmods: "l3_main_1", ... One hwmod for each noc domain.
> Is there some documentation on how the "hwmods" property is to be
Yes, it is part of the generic OMAP bindings documentation:
> I expect that this should be "ti,hwmods" because this is a TI
> specific property.
More information about the linux-arm-kernel