From: Geert Uytterhoeven <geert@linux-m68k.org> To: Wolfram Sang <wsa@the-dreams.de> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>, "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>, Linux-sh list <linux-sh@vger.kernel.org>, Linux I2C <linux-i2c@vger.kernel.org> Subject: Re: [PATCH] input: adxl34x: Add OF match support Date: Thu, 15 Jan 2015 13:03:16 +0000 [thread overview] Message-ID: <CAMuHMdXjB6-Fwk2+FLRNEynVgBXOm52n92QA-ZMTxsekPMtdsQ@mail.gmail.com> (raw) In-Reply-To: <20150115125321.GD2549@katana> On Thu, Jan 15, 2015 at 1:53 PM, Wolfram Sang <wsa@the-dreams.de> wrote: >> There are three compatible strings defined for the ADXL345 and ADXL346 in >> Documentation/devicetree/bindings/i2c/trivial-devices.txt: "adi,adxl345", >> "adi,adxl346", "adi,adxl34x". Given that the last one is a fallback for the >> first two I don't see a need to add the specific compatible strings to the >> driver for now. If a new totally incompatible chip named ADXL347 comes out we >> will need a new driver which won't be allowed to use the "adi,adxl34x" >> compatible string. > > Been there, got bitten. We only found out too late, because one driver > was in i2c and the other in GPIO (or LED even?), both using "953x" :( Yep, pca953x => leds-pca953x >> An option would be to remove "adi,adxl34x" from >> Documentation/devicetree/bindings/i2c/trivial-devices.txt, in which case the >> driver should match explicitly on "adi,adxl345" and "adi,adxl346". That might >> clash with the DT ABI stability requirements though. > > I do prefer this: > > 1) add specific compatible values to the driver. We do those updates for > new devices all the time > 2) also add "34x" as a compatible but mark it as deprecateed > 3) delete "34x" from trivial devices > > Everyone OK with that? Sounds fine to me. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org> To: Wolfram Sang <wsa@the-dreams.de> Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>, Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>, "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>, Linux-sh list <linux-sh@vger.kernel.org>, Linux I2C <linux-i2c@vger.kernel.org> Subject: Re: [PATCH] input: adxl34x: Add OF match support Date: Thu, 15 Jan 2015 14:03:16 +0100 [thread overview] Message-ID: <CAMuHMdXjB6-Fwk2+FLRNEynVgBXOm52n92QA-ZMTxsekPMtdsQ@mail.gmail.com> (raw) In-Reply-To: <20150115125321.GD2549@katana> On Thu, Jan 15, 2015 at 1:53 PM, Wolfram Sang <wsa@the-dreams.de> wrote: >> There are three compatible strings defined for the ADXL345 and ADXL346 in >> Documentation/devicetree/bindings/i2c/trivial-devices.txt: "adi,adxl345", >> "adi,adxl346", "adi,adxl34x". Given that the last one is a fallback for the >> first two I don't see a need to add the specific compatible strings to the >> driver for now. If a new totally incompatible chip named ADXL347 comes out we >> will need a new driver which won't be allowed to use the "adi,adxl34x" >> compatible string. > > Been there, got bitten. We only found out too late, because one driver > was in i2c and the other in GPIO (or LED even?), both using "953x" :( Yep, pca953x => leds-pca953x >> An option would be to remove "adi,adxl34x" from >> Documentation/devicetree/bindings/i2c/trivial-devices.txt, in which case the >> driver should match explicitly on "adi,adxl345" and "adi,adxl346". That might >> clash with the DT ABI stability requirements though. > > I do prefer this: > > 1) add specific compatible values to the driver. We do those updates for > new devices all the time > 2) also add "34x" as a compatible but mark it as deprecateed > 3) delete "34x" from trivial devices > > Everyone OK with that? Sounds fine to me. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
next prev parent reply other threads:[~2015-01-15 13:03 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-18 2:15 [PATCH] input: adxl34x: Add OF match support Laurent Pinchart 2014-12-18 2:15 ` Laurent Pinchart 2014-12-18 8:21 ` Wolfram Sang 2014-12-18 8:21 ` Wolfram Sang 2014-12-18 12:49 ` Laurent Pinchart 2014-12-18 12:49 ` Laurent Pinchart 2014-12-18 13:03 ` Geert Uytterhoeven 2014-12-18 13:03 ` Geert Uytterhoeven [not found] ` <CAMuHMdXcfe0JQhZzGSAoqjKR346-QJrvyi=afHF7cAaHKa56pw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2014-12-18 19:23 ` Laurent Pinchart 2014-12-18 19:23 ` Laurent Pinchart 2015-01-05 8:27 ` Laurent Pinchart 2015-01-05 8:27 ` Laurent Pinchart 2015-01-06 13:28 ` Geert Uytterhoeven 2015-01-06 13:28 ` Geert Uytterhoeven 2015-01-15 12:53 ` Wolfram Sang 2015-01-15 12:53 ` Wolfram Sang 2015-01-15 13:03 ` Geert Uytterhoeven [this message] 2015-01-15 13:03 ` Geert Uytterhoeven 2015-01-15 14:19 ` Laurent Pinchart 2015-01-15 14:19 ` Laurent Pinchart 2015-01-15 14:23 ` Laurent Pinchart 2015-01-15 14:23 ` Laurent Pinchart 2015-01-15 14:36 ` Wolfram Sang 2015-01-15 14:36 ` Wolfram Sang 2015-01-15 14:38 ` Laurent Pinchart 2015-01-15 14:38 ` Laurent Pinchart 2015-01-15 14:23 ` Geert Uytterhoeven 2015-01-15 14:23 ` Geert Uytterhoeven
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAMuHMdXjB6-Fwk2+FLRNEynVgBXOm52n92QA-ZMTxsekPMtdsQ@mail.gmail.com \ --to=geert@linux-m68k.org \ --cc=laurent.pinchart+renesas@ideasonboard.com \ --cc=laurent.pinchart@ideasonboard.com \ --cc=linux-i2c@vger.kernel.org \ --cc=linux-input@vger.kernel.org \ --cc=linux-sh@vger.kernel.org \ --cc=wsa@the-dreams.de \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.