On Wed, Apr 30, 2014 at 5:32 PM, Geert Uytterhoeven <geert@xxxxxxxxxxxxxx> wrote: > Hi Wolfram, > > CC devicetree > > On Thu, May 1, 2014 at 12:21 AM, Wolfram Sang <wsa@xxxxxxxxxxxxx> wrote: >> From: Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx> >> >> Reported-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx> >> Signed-off-by: Wolfram Sang <wsa+renesas@xxxxxxxxxxxxxxxxxxxx> >> --- >> .../devicetree/bindings/i2c/i2c-sh_mobile.txt | 26 ++++++++++++++++++++++ >> 1 file changed, 26 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt >> >> diff --git a/Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt b/Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt >> new file mode 100644 >> index 000000000000..d2153ce36fa8 >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/i2c/i2c-sh_mobile.txt >> @@ -0,0 +1,26 @@ >> +Device tree configuration for Renesas IIC (sh_mobile) driver >> + >> +Required properties: >> +- compatible : "renesas,iic-<soctype>". "renesas,rmobile-iic" as fallback > > Please also list all supported values, so checkpatch can validate DTS compatible > properties against this binding document. You could add this pattern to checkpatch as well. I really wish Renesas would follow normal convention of <vendor>,<chip>-<device>. Rob -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
