Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@cam.ac.uk>
To: "Hennerich, Michael" <Michael.Hennerich@analog.com>
Cc: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>,
	Drivers <Drivers@analog.com>
Subject: Re: [PATCH] IIO: ADC: New driver for AD7792/AD7793 3 Channel SPI ADC
Date: Tue, 31 May 2011 08:23:20 +0100	[thread overview]
Message-ID: <4DE49768.6050603@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D5917713AAF2F450F@LIMKCMBX1.ad.analog.com>

On 05/27/11 15:46, Hennerich, Michael wrote:
> Jonathan Cameron wrote on 2011-05-26:
>>
>> ...
>>>> What would happen if this driver used any other trigger?  Would
>> everything work?
>>> No. But other drivers can you the trigger. It's not really an
>>> trigger
>> it's a data ready.
>> Most are.  As you say, it is useful to trigger other reads from this,
>> but not to trigger this to read from other sources...
>>>> I think it would do an immediate read which is going to be a problem.
>>>> Perhaps we need a way of restricting triggers.  This one can be used
>>>> by anyone, but the part can only use it's own trigger (I think).
>>> Having the ability to reject alien triggers are nice to have.
>> True enough.  I guess the easiest is some sort of 'filter' callback on
>> trigger connect.
>> Then drivers that care, can reject devices that don't match what they
>> need.  Would probably want one in each direction.  Trigggers can
>> reject devices and devices can reject triggers.
> 
> Are you going to put this in place?
> Or do you want me to look at it?
don't mind either way.  Give me a yell if you start work on it and I'll
do the same.  Whoever gets their first can do it.
> 
> BTW - I'm out next week...
Me too (for most of it anyway!)
 
> Greetings,
> Michael
> 
> --
> Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
> Sitz der Gesellschaft: Muenchen; Registergericht: Muenchen HRB 40368; Geschaeftsfuehrer:Dr.Carsten Suckrow, Thomas Wessel, William A. Martin, Margaret Seif
> 
> 
> 


  reply	other threads:[~2011-05-31  7:15 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 15:02 [PATCH] IIO: ADC: New driver for AD7792/AD7793 3 Channel SPI ADC michael.hennerich
2011-05-26 10:18 ` Jonathan Cameron
2011-05-26 14:29   ` Michael Hennerich
2011-05-26 14:58     ` Jonathan Cameron
2011-05-27  8:09       ` Michael Hennerich
2011-05-27  9:09         ` [Device-drivers-devel] " Michael Hennerich
2011-05-27  9:49           ` Jonathan Cameron
2011-05-27  9:44         ` Jonathan Cameron
2011-05-27 10:23           ` Michael Hennerich
2011-05-27 10:53             ` Jonathan Cameron
2011-05-27 10:55               ` Michael Hennerich
2011-05-27 11:16                 ` Jonathan Cameron
2011-05-27 11:30                   ` Michael Hennerich
2011-05-27 12:23                     ` Jonathan Cameron
2011-05-27 14:46       ` Hennerich, Michael
2011-05-31  7:23         ` Jonathan Cameron [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-07 15:45 michael.hennerich
2011-06-08 14:12 ` 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=4DE49768.6050603@cam.ac.uk \
    --to=jic23@cam.ac.uk \
    --cc=Drivers@analog.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=device-drivers-devel@blackfin.uclinux.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