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>,
	Drivers <Drivers@analog.com>,
	"device-drivers-devel@blackfin.uclinux.org"
	<device-drivers-devel@blackfin.uclinux.org>
Subject: Re: [PATCH] staging: iio: dds: ad9834: Enable driver support for AD9833 and AD9834 DDS devices
Date: Tue, 30 Nov 2010 17:02:59 +0000	[thread overview]
Message-ID: <4CF52E43.2000105@cam.ac.uk> (raw)
In-Reply-To: <544AC56F16B56944AEC3BD4E3D591771312F0818BD@LIMKCMBX1.ad.analog.com>

On 11/30/10 16:44, Hennerich, Michael wrote:
>> Jonathan Cameron wrote on 2010-11-30:
>>>> From a generalization point of view we don't care that the square wave
>>>> is a random bonus option the part happens to be able to kick out.
>>>> Ideally we want a naming scheme that makes it's relationship to the
>>>> other waveforms apparent though and it's not entirely obvious how to
>>>> handle that (e.g. how to handle the double frequency square wave this
>>>> part can produce). Things will get more fun if parts have multiple
>>>> outputs tied to one dds channel.
>>>
>>> Actually that's the case here on the AD9834. The signbit is an
>>> independent output. It therefore can't be handled with the
>> dds0_wavetype file.
>> Then have dds0_wavetype0 (sine triangle) and dds0_wavetype1 (square).
>> Document that the second index is only required if there are multiple
>> physical outputs from a given channel.
> 
> How to disable dds0_wavetype1 (square)?
> 
> (square off)?
Nope, it's just like the other output in that it can be disabled so give
it it's own disable attribute.  The naming currently proposed looks a little
strange for this... hmm.  Perhaps change to dds0_out1_wavetype etc for the
other elements.
dds0_out_disable (for both) and dds0_out1_disable allows this channel to be
separately disabled.
> 
> Not all combinations of dds0_wavetype0 (sine triangle) are allowed with the signbit output.
That's fine.  You have dds0_out1_wavtype_available and dds0_out0_wavetype_available
to say what is possible for each of the two outputs of dds0.  
> 
> 
>>> It can be enabled/disabled while the DDS generates a sine wave on the
>>> main output.
>>>
>>> On the AD9833 the signbit square wave feature is routed to the DDS
>> main output.
>> Then that part just has the dds0_wavetype (triangle sine square) as
>> suggested above.
> 
> That's how I implemented it for the AD9833
Excellent, I had missed that.
> 
> Greetings,
> Michael
> 
> --
> Analog Devices GmbH      Wilhelm-Wagenfeld-Str. 6      80807 Muenchen
> Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 4036
> Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
> 
> 
> 


      reply	other threads:[~2010-11-30 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 15:51 [PATCH] staging: iio: dds: ad9834: Enable driver support for AD9833 and AD9834 DDS devices michael.hennerich
2010-11-29 23:12 ` Jonathan Cameron
2010-11-30 15:20   ` Hennerich, Michael
2010-11-30 16:12     ` Jonathan Cameron
2010-11-30 16:44       ` Hennerich, Michael
2010-11-30 17:02         ` Jonathan Cameron [this message]

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=4CF52E43.2000105@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