Linux IIO development
 help / color / mirror / Atom feed
From: Manuel Stahl <manuel.stahl@iis.fraunhofer.de>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: linux-iio@vger.kernel.org, greg@kroah.com, "Hennerich,
	Michael" <Michael.Hennerich@analog.com>
Subject: Re: [PATCH] staging: iio: fix spi cs_change behaviour
Date: Wed, 12 Jan 2011 13:00:24 +0100	[thread overview]
Message-ID: <4D2D97D8.2010207@iis.fraunhofer.de> (raw)
In-Reply-To: <4D2D911F.3000203@cam.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

On 12.01.2011 12:31, Jonathan Cameron wrote:
> On 01/12/11 09:55, Manuel Stahl wrote:
>> The normal behaviour is:
>>   * After all transfers except the last: CS stays active
>>   * After the last transfer: CS goes inactive
>
> Hi Manuel,
>
> Thanks for doing this.
>
> This ideally wants an ack from someone at Analog (Michael perhaps?)
> given it touches so many of their drivers.
>
> I'm not keen on the level of change in the lis3l02dq going in within
> this set. The change looks worthwhile, but it isn't just fixing
> the cs_change problem so it really shouldn't be in this patch.
> We can put that one in place at a later date.
> Same is true for the sca3000 driver.  Please just do the cs_change
> fixes in this patch.

The functions I call do the same as the code that was there before but 
without the cs_change. But I can understand your concern.

> A few cases here remove cases where cs_change is set to 0 anyway.
> Worthy cleanups, but not fixes.  Still those are at least within
> the spirit of the fixes and don't really matter.
>
> Feel free to add my ack to a version with the lis3l02dq and sca3000
> cleanups removed (and appropriate cs_change patches for those two).

Let's see what the analog guy say, then I'll prepare an update.

Regards,
Manuel Stahl

[-- Attachment #2: manuel_stahl.vcf --]
[-- Type: text/x-vcard, Size: 161 bytes --]

begin:vcard
fn:Manuel Stahl
n:Stahl;Manuel
email;internet:manuel.stahl@iis.fraunhofer.de
tel;work:+49 911 58061-6419
x-mozilla-html:FALSE
version:2.1
end:vcard


  reply	other threads:[~2011-01-12 12:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-12  9:55 [PATCH] staging: iio: fix spi cs_change behaviour Manuel Stahl
2011-01-12 11:31 ` Jonathan Cameron
2011-01-12 12:00   ` Manuel Stahl [this message]
2011-02-28 12:45   ` Hennerich, Michael

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=4D2D97D8.2010207@iis.fraunhofer.de \
    --to=manuel.stahl@iis.fraunhofer.de \
    --cc=Michael.Hennerich@analog.com \
    --cc=greg@kroah.com \
    --cc=jic23@cam.ac.uk \
    --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