On 09/01/2012 12:05 AM, AnilKumar, Chimata wrote: > On Fri, Aug 31, 2012 at 14:59:21, AnilKumar, Chimata wrote: >> Modify c_can binding documentation according to recent review comments >> on device tree data addition patches. >> diff --git a/Documentation/devicetree/bindings/net/can/c_can.txt b/Documentation/devicetree/bindings/net/can/c_can.txt >> index a43f083..90a70be 100644 >> --- a/Documentation/devicetree/bindings/net/can/c_can.txt >> +++ b/Documentation/devicetree/bindings/net/can/c_can.txt >> @@ -8,6 +8,8 @@ Required properties: >> registers map >> - interrupts : property with a value describing the interrupt >> number >> +- status : describes the node status either "disabled" or >> + "okay" That's a standrd property that applies to any node, and doesn't describe data required by the device itself (as do regs/interrupts) by simply whether the node is activated; I'm not sure it's worth mentioning it in a device-specific binding. A similar comment exists for the pre-existing description of interrupt-parent below. >> Optional properties: >> - interrupt-parent : The parent interrupt controller -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
