linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Giuseppe Barba <giuseppe.barba@st.com>,
	Denis Ciocca <denis.ciocca@st.com>
Subject: Re: [PATCH 2/4] iio: st_sensors: read each channel individually
Date: Sun, 17 Apr 2016 12:22:04 +0100	[thread overview]
Message-ID: <571371DC.7000506@kernel.org> (raw)
In-Reply-To: <CACRpkdYW2iSKtHhJUj5ZaWdFJjmbhF+wRw+P04sQZ=7mwxcefw@mail.gmail.com>

On 11/04/16 07:50, Linus Walleij wrote:
> On Sun, Apr 10, 2016 at 4:29 PM, Jonathan Cameron <jic23@kernel.org> wrote:
>> On 29/03/16 09:15, Linus Walleij wrote:
>>> On Mon, Mar 28, 2016 at 11:20 AM, Linus Walleij <linus.walleij@linaro.org> wrote:
> 
>>> So there are sensors out there that doesn't work well
>>> with the bulk read optimization.
>>>
>>> I think this patch should be applied for fixes, tell me if
>>> you need it rebased as the first patch (though I think it
>>> will just apply).
>>>
>>> Giuseppe/Denis? Agree?
>>
>> Anyone want to comment on this?
> 
> I'd say apply it.
> 
> If bulk mode should be supported it needs to be opt-in
> since the LIS331DL obviously cannot handle it.
> 
Unfortunately the context has changed a lot due to your earlier patch:

iio: st_sensors: simplify buffer address handling
which is in the togreg branch this is based on, but hasn't yet hit
mainline.  Looking at dates it must have 'just missed' the last merge
window.

Given how different they are I think we are going to have to do different
patches for current tree and a backported one.

So I'll pick this up in the togreg branch so we can move forward with
that but can you roll one against current mainline as well.

Thanks,

Jonathan


  reply	other threads:[~2016-04-17 11:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 13:18 [PATCH 1/4] iio: st_sensors: simplify buffer address handling Linus Walleij
2016-03-24 13:18 ` [PATCH 2/4] iio: st_sensors: read each channel individually Linus Walleij
2016-03-28  8:03   ` Jonathan Cameron
2016-03-28  9:20     ` Linus Walleij
2016-03-28  9:37       ` Jonathan Cameron
2016-03-29  8:15       ` Linus Walleij
2016-04-10 14:29         ` Jonathan Cameron
2016-04-11  6:50           ` Linus Walleij
2016-04-17 11:22             ` Jonathan Cameron [this message]
2016-04-17 18:47               ` Linus Walleij
2016-03-24 13:18 ` [PATCH 3/4] iio: st_sensors: verify interrupt event to status Linus Walleij
2016-03-28  8:09   ` Jonathan Cameron
2016-04-12 12:34     ` Linus Walleij
2016-04-17 11:24       ` Jonathan Cameron
2016-05-03 17:58   ` Crestez Dan Leonard
2016-05-03 20:10     ` Linus Walleij
2016-05-04  7:35       ` Jonathan Cameron
2016-05-04 14:34         ` Linus Walleij
2016-05-04 18:14           ` Crestez Dan Leonard
2016-05-06  9:14             ` Linus Walleij
2016-03-24 13:18 ` [PATCH 4/4] iio: st_sensors: support open drain mode Linus Walleij
2016-03-28  9:12   ` Jonathan Cameron
2016-03-31  8:15     ` Linus Walleij
2016-04-03  9:33       ` Jonathan Cameron
2016-03-28  3:42 ` [PATCH 1/4] iio: st_sensors: simplify buffer address handling Denis Ciocca
2016-03-28  7:52   ` Jonathan Cameron
2016-03-28  8:16     ` Denis Ciocca
2016-03-28  8:27       ` 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=571371DC.7000506@kernel.org \
    --to=jic23@kernel.org \
    --cc=denis.ciocca@st.com \
    --cc=giuseppe.barba@st.com \
    --cc=linus.walleij@linaro.org \
    --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).