linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ge Gao <ggao@invensense.com>
To: Jonathan Cameron <jic23@cam.ac.uk>, Jonathan Cameron <jic23@kernel.org>
Cc: linux-iio@vger.kernel.org
Subject: RE: sw_ring.c poll problem
Date: Thu, 17 May 2012 18:08:51 -0700	[thread overview]
Message-ID: <0a0072f9cc413b7489544b461684c953@mail.gmail.com> (raw)
In-Reply-To: <4FB35420.4020001@cam.ac.uk>

Dear Jonathan,
	I check the kfifo buffer implementation under IIO directory. However, I
didn't find the "pollq" is released anywhere as sw_ring does.  Without it,
how can kfifo be polled if it is used by industrial-buffer.c? Thanks.

Best Regards,

Ge GAO


Hi Ge,

I realised after sending that message that I was being rather dismissive of
your query.  Got up far too early this morning (as every morning ;)

Anyhow, to give more details. sw_ring is probably never going to make it out
of staging, hence the move to kfifo_buf. At somepoint we need to work out
how to do equivalent functionality of sw_ring but I've not had time to more
than start looking into this.

As you saw, poll on sw_ring is a watershead signal indicating (in theory and
last I checked it worked) that the ring is more than half full.
Any read that takes the fill level below half (test code just reads half the
size of the buffer), should allow a new passing of the watershead to
resignal poll. It's entirely possible there is a bug in there though I know
it is been getting a fair bit of testing with some other drivers so could be
todo with the precise way you are reading it hitting some corner case? (I'm
stretching...)

Right now I'd just move over to kfifo_buf if I were you. It's much more
'standard' in that it's a fifo and poll indicates if there is anything there
at all.
>> 	Thanks.
>>
>> Best regards,
>>
>> Ge GAO
>> --
>> 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
>

  parent reply	other threads:[~2012-05-18  1:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  1:26 sw_ring.c poll problem Ge Gao
2012-05-16  5:46 ` Jonathan Cameron
2012-05-16  7:15   ` Jonathan Cameron
2012-05-16 17:16     ` Ge Gao
2012-05-18  1:08     ` Ge Gao [this message]
2012-05-18 17:30       ` Jonathan Cameron
2012-05-18 18:26         ` Ge Gao
2012-05-19  9:16           ` Jonathan Cameron
2012-05-19  9:41             ` Lars-Peter Clausen
2012-05-19  9:50               ` Jonathan Cameron
2012-05-19 10:43                 ` Lars-Peter Clausen
2012-05-19 14:12                   ` Jonathan Cameron
2012-05-19 14:21                     ` Jonathan Cameron
2012-05-21 17:03                   ` Ge Gao
2012-05-18 19:27         ` Ge Gao
2012-05-19  9:18           ` 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=0a0072f9cc413b7489544b461684c953@mail.gmail.com \
    --to=ggao@invensense.com \
    --cc=jic23@cam.ac.uk \
    --cc=jic23@kernel.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;
as well as URLs for NNTP newsgroup(s).