linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Sean Nyekjaer <sean.nyekjaer@prevas.dk>, linux-iio@vger.kernel.org
Subject: Re: [RFC 2/2] iio: ad5755: added support for switching between voltage and current output
Date: Mon, 25 Jan 2016 17:00:06 +0100	[thread overview]
Message-ID: <56A64686.8030003@metafoo.de> (raw)
In-Reply-To: <1453467296-26356-2-git-send-email-sean.nyekjaer@prevas.dk>

On 01/22/2016 01:54 PM, Sean Nyekjaer wrote:
> DAC ad5755 have both support for voltage and current output, before the driver
> only had support for switching modes at compile time. Not very smart...
> 
> This patch adds support for switching modes from userspace.
> 
> Signed-off-by: Sean Nyekjaer <sean.nyekjaer@prevas.dk>
> ---
> 
> This patch is not done yet :-) I would like to get some feedback of my work.
> I have tested this patch with an ad5755 and it works.
> 
> So if you have any ideas on how I should progress please give me some feedback.

Hi,

I'd like to better understand why this is necessary (or not). What is your
usecase where you need to support switching at runtime?

- Lars


  parent reply	other threads:[~2016-01-25 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-22 12:54 [RFC 1/2] iio: core: added support for a single output that supports both current and voltage Sean Nyekjaer
2016-01-22 12:54 ` [RFC 2/2] iio: ad5755: added support for switching between voltage and current output Sean Nyekjaer
2016-01-24 15:49   ` Jonathan Cameron
2016-01-25 15:05     ` Sean Nyekjær
2016-01-25 17:17       ` Jonathan Cameron
2016-01-25 16:00   ` Lars-Peter Clausen [this message]
2016-01-26  6:15     ` Sean Nyekjær
     [not found] ` <2C284AAE-21FB-4EFE-AD1C-2F010B15C845@jic23.retrosnub.co.uk>
2016-01-22 14:37   ` [RFC 1/2] iio: core: added support for a single output that supports both current and voltage Sean Nyekjær
2016-01-22 16:49     ` Jonathan Cameron
2016-01-24 15:14       ` 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=56A64686.8030003@metafoo.de \
    --to=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=sean.nyekjaer@prevas.dk \
    /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).