All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: Jonathan Cameron <jic23@cam.ac.uk>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"uclinux-dist-devel@blackfin.uclinux.org"
	<uclinux-dist-devel@blackfin.uclinux.org>,
	"Getz, Robin" <Robin.Getz@analog.com>
Subject: Re: IIO:ADC Scan Modes
Date: Tue, 04 May 2010 11:47:39 +0100	[thread overview]
Message-ID: <4BDFFB4B.1040409@cam.ac.uk> (raw)
In-Reply-To: <4BDFF8EE.2000201@cam.ac.uk>

On 05/04/10 11:37, Jonathan Cameron wrote:
> Hi Michael
>> The way available scan modes are handled in the max1363 driver doesn't
>> nicely equate to the AD7997, AD7997 or AD7991 series of ADCs.
>> These devices feature up to 8 Channels while each channel can be independently
>> included into the scan sequence.
>> (this would require up to 256 'named' modes)
> I agree entirely.  The approach originally used in max1363 has gone in the latest
> patch set posted the other day (indeed the set you reference below)
>>
>> A while ago we talked about this - and you said you would abandon the
>> 'named' scan mode selection - and come up with something like a scan_elements
>> directory with channel control files (enable/disable), and some sort of mechanism
>> that rejects invalid combinations.
>>
>> I noticed some additions ...
>> [PATCH 04/19] staging:iio: Support functions for scan mask matching
> Yup.  That's what max1363 now does. In the same series, see
> [PATCH 08/19] staging:iio:max1363 move to new abi.
> 
> (as the new abi didn't allow the 'named' scan mode approach!)

As a footnote.  The max1363 changes are about the least tested and most complex
part of that patch set, so any comments from anyone on that or other aspects of
the set are welcome!  I'll need to get these to Greg fairly soon if they are going
to merge in the next window.

> Other than some renaming, the lis3l20dq for example has done the scan_elements
> approach from the start (as have some of the others.)
> 
> Jonathan
> 
> 
>>
>> But the sysfs interface is not in place.
>> Is this something you're still planning to put into place?
>>
>> Best regards,
>> Michael
>>
>>
>> ------------------------------------------------------------------
>> ********* Analog Devices GmbH              Open Platform Solutions
>> **  *****
>> **     ** Wilhelm-Wagenfeld-Strasse 6
>> **  ***** D-80807 Munich
>> ********* Germany
>> Registergericht München HRB 40368,  Geschäftsführer: Thomas Wessel, William A. Martin, Margaret K. Seif
>>
>>
> 
> --
> 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:[~2010-05-04 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-04  9:48 IIO:ADC Scan Modes Hennerich, Michael
2010-05-04 10:37 ` Jonathan Cameron
2010-05-04 10:47   ` Jonathan Cameron [this message]
2010-05-04 10:53   ` 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=4BDFFB4B.1040409@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Michael.Hennerich@analog.com \
    --cc=Robin.Getz@analog.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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 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.