All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	<linux-iio@vger.kernel.org>
Subject: Re: [PATCH 3/6] iio: accel: kxcjk1013: rename registers for KXTF9 compatibility
Date: Tue, 22 Aug 2017 13:47:49 +0100	[thread overview]
Message-ID: <20170822134749.00003e7f@huawei.com> (raw)
In-Reply-To: <20170821214510.av6wufitda7jayiw@qmqm.qmqm.pl>

On Mon, 21 Aug 2017 23:45:10 +0200
Michał Mirosław <mirq-linux@rere.qmqm.pl> wrote:

> On Sun, Aug 20, 2017 at 10:52:22AM +0100, Jonathan Cameron wrote:
> > On Thu, 17 Aug 2017 16:21:36 +0200
> > Michał Mirosław <mirq-linux@rere.qmqm.pl> wrote:  
> > > Rename some registers that are shared between KXTF9 and KXCJK.
> > > Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>  
> > 
> > Hi Michał,
> > 
> > I'm not keen on this change.   Going for generic names is always
> > fragile as all it takes is another part coming along which is almost
> > but not quite the same as you shared register set and we end up with
> > a mess.
> > 
> > General convention for both register values and driver naming is they
> > should be named after one supported part rather than trying to find
> > a generic name that covers all supported parts.
> > 
> > So please revert this change and resend the series.
> > 
> > Sorry to be a pain, but this has gone wrong quite a lot of times in
> > the past!  
> 
> I removed the renaming, but left KXTF9-specific registers with KXTF9_
> prefix. This is hard to avoid as some registers are named differently
> in KXTF9 and KXCJK datasheets, but are otherwise compatible. There is
> also a register that is the same but has different address.

That's what I expected. Thanks.
> 
> I'll send v2 shortly.
> 
> BTW, I browsed through "sell sheets" of Kionix's accelerometers, and
> I would guess that for eg. KXCJK-1013, "KXCJK" is a model, and "1013"
> is variation. KXTF9 has two such variations differing only in supply
> voltages it is calibrated to run with. Based on that I would rename
> the driver to "kxcjk" to save on typing if there are more similar
> parts to add later. There is KXSD9 driver (different register set), so
> this would match clearly.

While that makes sense, be careful not to change anything that is
reflected in userspace ABI and that includes module names.  Tends
to break things in odd ways.

Jonathan
> 
> Best Regards,
> Michał Mirosław
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2017-08-22 12:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-17 14:21 [PATCH 0/6] iio: accel: kxcjk1003: support Kionix KXTF9 Michał Mirosław
2017-08-17 14:21 ` [PATCH 1/6] iio: accel: kxcjk1003: refactor ODR setting Michał Mirosław
2017-08-20 10:02   ` Jonathan Cameron
2017-08-17 14:21 ` [PATCH 3/6] iio: accel: kxcjk1013: rename registers for KXTF9 compatibility Michał Mirosław
2017-08-20  9:52   ` Jonathan Cameron
2017-08-21 21:45     ` Michał Mirosław
2017-08-22 12:47       ` Jonathan Cameron [this message]
2017-08-17 14:21 ` [PATCH 2/6] iio: accel: kxcjk1013: extract report_motion_event() from interrupt handler Michał Mirosław
2017-08-20 10:01   ` Jonathan Cameron
2017-08-17 14:21 ` [PATCH 4/6] iio: accel: kxcjk1013: make sysfs/sampling_frequency_avail dynamic Michał Mirosław
2017-08-20  9:53   ` Jonathan Cameron
2017-08-17 14:21 ` [PATCH 6/6] iio: accel: kxcjk1013: add support for KXTF9 Michał Mirosław
2017-08-20 10:00   ` Jonathan Cameron
2017-08-17 14:21 ` [PATCH 5/6] iio: accel: kxcjk1013: make sampling_frequency_avail per-type Michał Mirosław
2017-08-20  9:57   ` 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=20170822134749.00003e7f@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=mirq-linux@rere.qmqm.pl \
    --cc=pmeerw@pmeerw.net \
    /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.