As opp.txt was moved from:
Documentation/devicetree/bindings/power/
to
Documentation/devicetree/bindings/opp/
in the commit 3566c5b277a4 ("PM / OPP: Create a directory for opp
bindings"), the vendor bindings should also go in that directory.Signed-off-by: Richard Genoud <[email protected]> --- Documentation/devicetree/bindings/opp/opp.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt index 0cb44dc21f97..f099d5d6f80d 100644 --- a/Documentation/devicetree/bindings/opp/opp.txt +++ b/Documentation/devicetree/bindings/opp/opp.txt @@ -51,7 +51,7 @@ accompanied by a corresponding "operating-points-names" property, to uniquely identify the OPP tables. If required, this can be extended for SoC vendor specfic bindings. Such bindings -should be documented as Documentation/devicetree/bindings/power/<vendor>-opp.txt +should be documented as Documentation/devicetree/bindings/opp/<vendor>-opp.txt and should have a compatible description like: "operating-points-v2-<vendor>". Optional properties: -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
