linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Joachim Eastwood <manabian@gmail.com>,
	Martin Kepplinger <martink@posteo.de>
Cc: knaack.h@gmx.de, Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH v2] iio: accel: add Freescale MMA7455L/MMA7456L 3-axis accelerometer driver
Date: Sun, 25 Oct 2015 11:29:41 +0000	[thread overview]
Message-ID: <562CBD25.5040404@kernel.org> (raw)
In-Reply-To: <CAGhQ9Vy72fG4AVNe_esOUd4d8=3UQj6Sada3_v7pZ1MEc=cjrA@mail.gmail.com>

On 20/10/15 12:03, Joachim Eastwood wrote:
> On 20 October 2015 at 09:48, Martin Kepplinger <martink@posteo.de> wrote:
>> Am 2015-10-19 um 21:00 schrieb Joachim Eastwood:
>>> Add support for Freescale MMA7455L/MMA7456L 3-axis in 10-bit mode for
>>> I2C and SPI bus. This rather simple driver that currently doesn't
>>> support all the hardware features of MMA7455L/MMA7456L.
>>>
>>> Tested on Embedded Artist's LPC4357 Dev Kit with MMA7455L on I2C bus.
>>>
>>> Data sheets for the two devices can be found here:
>>> http://cache.freescale.com/files/sensors/doc/data_sheet/MMA7455L.pdf
>>> http://cache.freescale.com/files/sensors/doc/data_sheet/MMA7456L.pdf
>>>
>>> Signed-off-by: Joachim Eastwood <manabian@gmail.com>
>>> ---
>>> Hi,
>>>
>>> This version address the comments from Lars-Peter Clausen, Peter
>>> Meerwald and Martin Kepplinger. Thanks for all the constructive
>>> feedback!
>>>
>>> Changes since v1:
>>> * limit retries to 3 in mma7455_drdy
>>> * remove mma7455_show_scale_avail
>>> * use chan->address instead of chan->scan_index for reg addr
>>> * check that val2 is 0 when setting sample freq
>>> * use __le16 to hint about endianess in mma7455_trigger_handler
>>> * fix endianess in mma7455_read_raw function
>>> * add mma7456 id
>>> * split it into several source files to support both i2c and spi
>>>
>>> I compared the register summary for MMA7455L/MMA7456L and I am
>>> unable to find any difference at all.
>>>
>>>  drivers/iio/accel/Kconfig        |  22 +++
>>>  drivers/iio/accel/Makefile       |   5 +
>>>  drivers/iio/accel/mma7455.h      |  20 +++
>>>  drivers/iio/accel/mma7455_core.c | 321 +++++++++++++++++++++++++++++++++++++++
>>>  drivers/iio/accel/mma7455_i2c.c  |  57 +++++++
>>>  drivers/iio/accel/mma7455_spi.c  |  53 +++++++
>>>  6 files changed, 478 insertions(+)
>>>  create mode 100644 drivers/iio/accel/mma7455.h
>>>  create mode 100644 drivers/iio/accel/mma7455_core.c
>>>  create mode 100644 drivers/iio/accel/mma7455_i2c.c
>>>  create mode 100644 drivers/iio/accel/mma7455_spi.c
>>>
>>>  config MMA8452
>>>       tristate "Freescale MMA8452Q Accelerometer Driver"
>>>       depends on I2C
>>> diff --git a/drivers/iio/accel/Makefile b/drivers/iio/accel/Makefile
>>> index ebd2675b2a02..dfb9289393fb 100644
>>> --- a/drivers/iio/accel/Makefile
>>
>> You don't base your work on top of the current -next tree. But that's
>> where this most likely will go, if integrated. Please make it apply to
>> linux-next.
> 
> Sure I can based it off linux-next or would one of the branches on
> git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git be better?
It doesn't matter that much unless lots of work is being done on a
given driver.  Either linux-next or the togreg branch of the above.

The testing branch usually contains the latest stuff but may rebase
as it's really there for automated builds.

Actually I don't really mind basing on last full kernel release either
or on staging-next which is our upstream.

At worst you get a tiny bit of merge fun.

Jonathan

> 
> 
> regards,
> Joachim Eastwood
> 


  reply	other threads:[~2015-10-25 11:29 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-17 22:25 [PATCH] iio: accel: add Freescale MMA7455L 3-axis accelerometer driver Joachim Eastwood
2015-10-19 10:45 ` Lars-Peter Clausen
2015-10-19 12:19   ` Joachim Eastwood
2015-10-19 12:23     ` Lars-Peter Clausen
2015-10-19 12:38       ` Joachim Eastwood
2015-10-19 11:00 ` Peter Meerwald
2015-10-19 12:26   ` Joachim Eastwood
2015-10-19 12:38     ` Peter Meerwald
2015-10-19 11:10 ` Martin Kepplinger
2015-10-19 12:34   ` Joachim Eastwood
2015-10-19 12:56     ` Martin Kepplinger
2015-10-19 13:43       ` Joachim Eastwood
2015-10-19 14:09         ` Martin Kepplinger
2015-10-19 14:14           ` Lars-Peter Clausen
2015-10-19 19:00 ` [PATCH v2] iio: accel: add Freescale MMA7455L/MMA7456L " Joachim Eastwood
2015-10-19 21:07   ` Joachim Eastwood
2015-10-20  7:48   ` Martin Kepplinger
2015-10-20 11:03     ` Joachim Eastwood
2015-10-25 11:29       ` Jonathan Cameron [this message]
2015-10-20  8:05   ` Lars-Peter Clausen
2015-10-20 11:00     ` Joachim Eastwood
2015-10-20 11:05       ` Lars-Peter Clausen
2015-10-20 11:52         ` Joachim Eastwood
2015-10-20 20:50 ` [PATCH v3] " Joachim Eastwood
2015-10-25 11:45   ` Jonathan Cameron
2015-10-29 17:34     ` Joachim Eastwood
2015-10-30 10:00       ` Jonathan Cameron
2015-10-31 12:49 ` [PATCH v4] " Joachim Eastwood
2015-10-31 21:37   ` Martin Kepplinger
2015-11-01 18:01     ` Jonathan Cameron
2015-11-02 11:07       ` Martin Kepplinger
2015-11-08 15:47         ` Jonathan Cameron
2015-11-01 18:01   ` Jonathan Cameron
2015-11-01 18:02     ` Jonathan Cameron
2015-11-03 22:17       ` Joachim Eastwood
2015-11-08 15:49         ` 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=562CBD25.5040404@kernel.org \
    --to=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=manabian@gmail.com \
    --cc=martink@posteo.de \
    --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 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).