On Tue, Feb 1, 2011 at 9:31 PM, Grant Likely <[email protected]> wrote: > On Mon, Jan 24, 2011 at 01:58:13PM +0800, Thomas Chou wrote: >> From: Walter Goossens <[email protected]> >> >> Signed-off-by: Walter Goossens <[email protected]> >> Signed-off-by: Thomas Chou <[email protected]> >> --- >> v2 use const and add compat version. >> >> drivers/input/serio/altera_ps2.c | 11 +++++++++-- >> 1 files changed, 9 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/input/serio/altera_ps2.c >> b/drivers/input/serio/altera_ps2.c >> index 7998560..63325ee 100644 >> --- a/drivers/input/serio/altera_ps2.c >> +++ b/drivers/input/serio/altera_ps2.c >> @@ -19,6 +19,7 @@ >> #include <linux/platform_device.h> >> #include <linux/io.h> >> #include <linux/slab.h> >> +#include <linux/of.h> >> >> #define DRV_NAME "altera_ps2" >> >> @@ -173,6 +174,12 @@ static int __devexit altera_ps2_remove(struct >> platform_device *pdev) >> return 0; >> } >> >> +static const struct of_device_id altera_ps2_match[] = { >> + { .compatible = "altr,ps2-1.0", }, > > I thought I had seen 'altera' instead of an abbreviation being used in > a previous patch. I don't care much whether 'altr' or 'altera' is > used, but I'd like to know that there is consensus from the Altera > users so that all the drivers use the same prefix.
Oh, and this patch should add documentation to Documentation/devicetree/bindings/spi specifying exactly what device this compatible string represents and what properties are expected to be in the node (if any) beyond the standard reg, interrupts, etc. It doesn't need to be huge and detailed, but it at least needs to show that the string is in use. This comment goes for the other patches that add bindings too. g. _______________________________________________ devicetree-discuss mailing list [email protected] https://lists.ozlabs.org/listinfo/devicetree-discuss
