linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Daniel Palmer <daniel@0x0f.com>
Cc: <linux-iio@vger.kernel.org>, Denis Ciocca <denis.ciocca@st.com>
Subject: Re: [RFC PATCH 0/2] iio: st-accel: Add support for Silan clones
Date: Wed, 12 Aug 2020 10:20:29 +0100	[thread overview]
Message-ID: <20200812102029.000023d1@Huawei.com> (raw)
In-Reply-To: <20200811134846.3981475-1-daniel@0x0f.com>

On Tue, 11 Aug 2020 22:48:44 +0900
Daniel Palmer <daniel@0x0f.com> wrote:

> This small series adds support for the Silan SC7A20 and SC7A30E
> accelerometers that seem to be clones or at least based on the
> LIS2DH from ST.
> 
> These chips seem to be widely used in car dash recorders and the
> midrived08 dash recorder that I'm trying to mainline support for
> has a SC7A20.
> 
> This is RFC because I'm not sure if adding clone chips into this
> driver is going to cause anyone trouble and I'm thinking there has
> to be a better way of supporting both of the chips that are basically
> the same but have different WAI register values than copy/pasting the
> block and changing the WAI value.

The different WAI value suggests to me that we might be looking at
something made under license, or manufactured for them by ST.

Anyhow, it's not unusual to have cloned parts supported by a common
kernel driver so that shouldn't be a problem.

Only thing to note is we can't necessarily expect Denis to be able
to review any changes to the driver that might affect these parts.

If Denis is willing, we could add an entry to MAINTAINERS for these
and add you as a reviewer so that you should get any future patches
sent to you as well.

Denis, what's your view on this, or can you shed any light on
these parts?


> 
> Daniel Palmer (2):
>   dt-bindings: vendor-prefixes: Add vendor prefix for Silan
>   iio: st-accel: Add support for Silan SC7A20 and SC7A30E
> 
>  .../devicetree/bindings/vendor-prefixes.yaml  |   2 +
>  drivers/iio/accel/st_accel.h                  |   4 +
>  drivers/iio/accel/st_accel_core.c             | 159 +++++++++++++++++-
>  drivers/iio/accel/st_accel_i2c.c              |  10 ++
>  4 files changed, 174 insertions(+), 1 deletion(-)
> 



      parent reply	other threads:[~2020-08-12  9:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-11 13:48 [RFC PATCH 0/2] iio: st-accel: Add support for Silan clones Daniel Palmer
2020-08-11 13:48 ` [RFC PATCH 1/2] dt-bindings: vendor-prefixes: Add vendor prefix for Silan Daniel Palmer
2020-08-16  8:50   ` Jonathan Cameron
2020-08-11 13:48 ` [RFC PATCH 2/2] iio: st-accel: Add support for Silan SC7A20 and SC7A30E Daniel Palmer
2020-08-16  8:52   ` Jonathan Cameron
2020-08-16  9:27     ` Daniel Palmer
2020-08-16  9:40       ` Jonathan Cameron
2020-08-16  9:55   ` Andy Shevchenko
2020-08-16 11:59     ` Daniel Palmer
2020-08-19 18:19       ` Denis CIOCCA
2020-08-20  9:01         ` Jonathan Cameron
2020-08-20  9:17           ` Greg KH
2020-08-20 12:27         ` Daniel Palmer
2020-08-20 12:56           ` Andy Shevchenko
2020-08-20 12:34         ` Andy Shevchenko
2020-08-12  9:20 ` Jonathan Cameron [this message]

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=20200812102029.000023d1@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=daniel@0x0f.com \
    --cc=denis.ciocca@st.com \
    --cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).