From: Wolfram Sang <wsa@the-dreams.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-input@vger.kernel.org, linux-sh@vger.kernel.org,
linux-i2c@vger.kernel.org, Geert Uytterhoeven <geert@glider.be>
Subject: Re: [PATCH] input: adxl34x: Add OF match support
Date: Thu, 15 Jan 2015 15:36:37 +0100 [thread overview]
Message-ID: <20150115143637.GA5057@katana> (raw)
In-Reply-To: <2445803.jDZCe1u2Wf@avalon>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
> > > 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" :(
> >
> > That seems like a development, review and/or merge process failure to me, I
> > wouldn't avoid generic compatible strings for that reason only.
Well, I think different here, but let's skip this discussion as it is
not really needed right now...
> > As the ADXL346 is backward-compatible with the ADXL345, and as the driver
> > doesn't support the ADXL346-specific features, how about adding only the
> > adxl345 for now, and using compatible = "adi,adxl346", "adi,adxl345"; for
> > the ADXL346 ?
>
> I spoke too fast. The driver supports ADXL346-specific features, but does so
> by detecting the device model at runtime.
>
> I still believe it would make sense to list both the 346 and 345 models in DT
> for 346 devices, as they're compatible with the 345.
I agree.
> > > 2) also add "34x" as a compatible but mark it as deprecateed
> > > 3) delete "34x" from trivial devices
> >
> > OK.
Yay :)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-input@vger.kernel.org, linux-sh@vger.kernel.org,
linux-i2c@vger.kernel.org, Geert Uytterhoeven <geert@glider.be>
Subject: Re: [PATCH] input: adxl34x: Add OF match support
Date: Thu, 15 Jan 2015 14:36:37 +0000 [thread overview]
Message-ID: <20150115143637.GA5057@katana> (raw)
In-Reply-To: <2445803.jDZCe1u2Wf@avalon>
[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]
> > > 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" :(
> >
> > That seems like a development, review and/or merge process failure to me, I
> > wouldn't avoid generic compatible strings for that reason only.
Well, I think different here, but let's skip this discussion as it is
not really needed right now...
> > As the ADXL346 is backward-compatible with the ADXL345, and as the driver
> > doesn't support the ADXL346-specific features, how about adding only the
> > adxl345 for now, and using compatible = "adi,adxl346", "adi,adxl345"; for
> > the ADXL346 ?
>
> I spoke too fast. The driver supports ADXL346-specific features, but does so
> by detecting the device model at runtime.
>
> I still believe it would make sense to list both the 346 and 345 models in DT
> for 346 devices, as they're compatible with the 345.
I agree.
> > > 2) also add "34x" as a compatible but mark it as deprecateed
> > > 3) delete "34x" from trivial devices
> >
> > OK.
Yay :)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-01-15 14:36 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
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 [this message]
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=20150115143637.GA5057@katana \
--to=wsa@the-dreams.de \
--cc=geert@glider.be \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
/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: link
Be 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.