mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harinath Nampally <harinath922@gmail.com>
To: Martin Kepplinger <martink@posteo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>
Cc: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
	gregkh@linuxfoundation.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, amsfield22@gmail.com
Subject: Re: [PATCH] iio: accel: mma8452: Bugfix to enbale and allow different events to work parallely.
Date: Thu, 17 Aug 2017 07:55:45 -0400	[thread overview]
Message-ID: <9202ac3c-cc5b-2b45-ba37-d6a24364b9e6@gmail.com> (raw)
In-Reply-To: <13587F36-588D-4011-8E70-A8892F81887E@posteo.de>

> This patch fixes by detaching the event related information from
> chip_info struct,
>>> and based on channel type and event direction the corresponding
> event configuration registers
>>> are picked dynamically. Hence multiple events can be handled in
> read/write callbacks.
>> which chip can have which event(s)?
> I am planning to add 'supported events' field in
>
> struct mma_chip_info which indicates which chip can have which events.
> During initialization in 'mma_chip_info_table' would set this
> 'supported events' field for each chip.
> But I wonder should I add those changes as part of this patch?
> is it necessary or can it be documentation?
I think its not necessary as we only have Freefall and Transient events 
for now.
Ok I will just update the documentation.
>
> And this patch should have been called "v2". please include a persistent version history to v3 of this patch.
Sure I will send v3 patch, should I use '--in-reply-to' option of git 
send-email to send v3 patch as reply to
original thread?

On 08/17/2017 07:24 AM, Martin Kepplinger wrote:
>>>> This patch fixes by detaching the event related information from
>> chip_info struct,
>>>> and based on channel type and event direction the corresponding
>> event configuration registers
>>>> are picked dynamically. Hence multiple events can be handled in
>> read/write callbacks.
>>> which chip can have which event(s)?
>> I am planning to add 'supported events' field in
>>
>> struct mma_chip_info which indicates which chip can have which events.
>> During initialization in 'mma_chip_info_table' would set this
>> 'supported events' field for each chip.
>> But I wonder should I add those changes as part of this patch?
> is it necessary or can it be documentation?
>
> And this patch should have been called "v2". please include a persistent version history to v3 of this patch.

  reply	other threads:[~2017-08-17 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 22:44 Harinath Nampally
2017-08-16 13:12 ` Peter Meerwald-Stadler
2017-08-17  0:39   ` Harinath Nampally
2017-08-17 11:24     ` Martin Kepplinger
2017-08-17 11:55       ` Harinath Nampally [this message]
2017-08-17 14:40         ` Jonathan Cameron
2017-08-19  0:05           ` Harinath Nampally

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=9202ac3c-cc5b-2b45-ba37-d6a24364b9e6@gmail.com \
    --to=harinath922@gmail.com \
    --cc=amsfield22@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome