linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aniroop Mathur <aniroop.mathur@gmail.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: IIO: Why cannot open two iio device node file descriptors simultaneously ?
Date: Sun, 3 Aug 2014 15:02:27 +0530	[thread overview]
Message-ID: <CADYu30--CpVmTowroGJEcKbg78B-xrzGXfdhFxpOYXAgcD41gA@mail.gmail.com> (raw)
In-Reply-To: <53DDEEC6.2070300@metafoo.de>

On Sun, Aug 3, 2014 at 1:41 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
> On 08/02/2014 06:57 PM, Jonathan Cameron wrote:
> [...]
>
>>> So, even after opening iio device node,
>>> can we write the data to IIO device node from user space ?
>>> (I do not see write function in below fileops)
>>
>>
>> Indeed.  Lars was working on some buffered support for DACs but hasn't
>> yet submitted it for mainline inclusion.  Lars how is the buffered output
>> stuff coming along?
>
>
> I still need to do the re-write you wanted me to do, otherwise its working
> fine ;)
>

Great :)
So, it is possible to write data to iio fd ?

char *data;
int nbytes = 24;
int res = write(iio_fd, data, nbytes);

This will work fine ?

If yes, can you please help to tell where is write function defined ?
I could find only read function here
static const struct file_operations iio_event_chrdev_fileops = {
     .read =  iio_event_chrdev_read,
     .poll =  iio_event_poll,
     .release = iio_event_chrdev_release,
     .owner = THIS_MODULE,
     .llseek = noop_llseek,
}

> - Lars
>

Thanks,
Aniroop

  reply	other threads:[~2014-08-03  9:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31 17:07 IIO: Why cannot open two iio device node file descriptors simultaneously ? Aniroop Mathur
2014-08-02 11:28 ` Jonathan Cameron
2014-08-02 13:07   ` Aniroop Mathur
2014-08-02 16:57     ` Jonathan Cameron
2014-08-03  8:11       ` Lars-Peter Clausen
2014-08-03  9:32         ` Aniroop Mathur [this message]
2014-08-04  7:18           ` Lars-Peter Clausen
2014-08-04 15:11             ` Aniroop Mathur
2014-08-04 17:20               ` Lars-Peter Clausen
2014-08-04 19:18                 ` Aniroop Mathur
  -- strict thread matches above, loose matches on Subject: below --
2014-08-01 17:17 Aniroop Mathur

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=CADYu30--CpVmTowroGJEcKbg78B-xrzGXfdhFxpOYXAgcD41gA@mail.gmail.com \
    --to=aniroop.mathur@gmail.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --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;
as well as URLs for NNTP newsgroup(s).