linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Denis CIOCCA <denis.ciocca@st.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	linux-iio <linux-iio@vger.kernel.org>,
	Daniel Palmer <daniel@0x0f.com>, Mario TESI <mario.tesi@st.com>
Subject: Re: [RFC PATCH 2/2] iio: st-accel: Add support for Silan SC7A20 and SC7A30E
Date: Thu, 20 Aug 2020 15:34:23 +0300	[thread overview]
Message-ID: <CAHp75VcWWAWt4Up3XOQ5j9f5x+vEiE+f1ySF9pcPpZJhRJpj9w@mail.gmail.com> (raw)
In-Reply-To: <AM7PR10MB3670BE44AE8227C29E8AC48CED5D0@AM7PR10MB3670.EURPRD10.PROD.OUTLOOK.COM>

On Wed, Aug 19, 2020 at 9:19 PM Denis CIOCCA <denis.ciocca@st.com> wrote:
>
> Hi Jonathan,
>
> I strongly disagree that these parts will be supported by STMicroelectronics driver.
> We DO NOT want to find out one day that we need to modify our structure in order to support competition. If they need to support this chip, please provide a new driver for that part leaving STMicroelectronics driver managing our parts.

I'm not sure I understand this passage.
Are you telling we have to have Amount_of_Vendors * cloned_component drivers?
This is NOT how Linux kernel works, really.
Look at the pca953x GPIO expander driver, for example. It has tons of
clones supported and no-one died.

> > On Sun, 16 Aug 2020 at 18:55, Andy Shevchenko
> > <andy.shevchenko@gmail.com> wrote:
> > > No SoB tag?! Hint: `git commit -a -s --amend` would fix this if you
> > > have properly configured Git.
> > >
> >
> > Sorry I wasn't aware it was needed for an RFC.
> >
> > > On top of that, can you add Datasheet: tag with links to the actual
> > > component datasheets?
> >
> > I will do that for the v1 of the patch series. All of the datasheets I've found so
> > far are mostly Chinese but the register tables are in English. I've collected
> > them together
> > here: http://linux-chenxing.org/silan/index.html


-- 
With Best Regards,
Andy Shevchenko

  parent reply	other threads:[~2020-08-20 12:34 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 [this message]
2020-08-12  9:20 ` [RFC PATCH 0/2] iio: st-accel: Add support for Silan clones Jonathan Cameron

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=CAHp75VcWWAWt4Up3XOQ5j9f5x+vEiE+f1ySF9pcPpZJhRJpj9w@mail.gmail.com \
    --to=andy.shevchenko@gmail.com \
    --cc=daniel@0x0f.com \
    --cc=denis.ciocca@st.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=mario.tesi@st.com \
    /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).