linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zubair Lutfullah :" <zubair.lutfullah-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Jonathan Cameron <jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: Rob Mosher
	<nyt-fuEpAR7jH0UNb0vsIHg089HuzzzSOjJt@public.gmane.org>,
	Zubair Lutfullah
	<zubair.lutfullah-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Sebastian Andrzej Siewior
	<bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
	robertcnelson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
	Samuel Ortiz <sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	Dmitry Torokhov
	<dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>,
	linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Lee Jones <lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Subject: Re: ti_am33x_adc sampling bugs
Date: Tue, 1 Apr 2014 06:42:00 +0100	[thread overview]
Message-ID: <20140401054158.GA3261@gmail.com> (raw)
In-Reply-To: <c21be082-4ad8-46e2-a5f3-ad29b4239d94-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>


Sorry for taking this long to reply.

The confusion here is due to vendor/mainline trees for the kernel.

This discussion should have been carried out on 
https://github.com/beagleboard/kernel/issues
instead of the kernel mailing lists.

Sorry Jonathan.

The IIO-map-interface patch is in the vendor tree for the Beaglebone.

And it is not intended to be mainlined. Just like the other TI wiki stuff.

But it used to make life a little easier before the IIO sysfs entries were fixed
for the am335x ADC.

The patch was kept as it is because of the ton of guides/wikis out there for the
Beaglebone asking for AIN0/AIN7 pins.

And iirc capemgr (another out of tree module which is being mainlined) used it.
Which made it necessary to keep this.

As far as patch 19 (Add continuous sampling) is concerned, I didn't observe it 
causing these bugs. But it is good that you have pointed them out.
Thank-you.

Could you please go through the patch and suggest a fix as well?

Seems like a FIFO isn't cleared somewhere..

Hope this clears the confusion.

Again, this discussion should have been carried out 
https://github.com/beagleboard/kernel/issues

Not the kernel mailing list.

Regards
ZubairLK

> 

  parent reply	other threads:[~2014-04-01  5:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53379DF2.7050004@rznt.com>
     [not found] ` <5337B3F4.30500@countercultured.net>
     [not found]   ` <CAExKytzRv4CT9zTor=-fc5Mfv+xG9uTjQP=LWosVnhEHsa9Y0A@mail.gmail.com>
     [not found]     ` <CAExKytzRv4CT9zTor=-fc5Mfv+xG9uTjQP=LWosVnhEHsa9Y0A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-03-31  4:04       ` ti_am33x_adc sampling bugs Rob Mosher
2014-03-31  8:17         ` Rob Mosher
2014-03-31 16:14           ` Jonathan Cameron
     [not found]             ` <d8950cff-fd37-46bb-b438-d42f15851602-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2014-03-31 16:47               ` Rob Mosher
2014-03-31 20:59                 ` Jonathan Cameron
2014-03-31 21:03                   ` Rob Mosher
2014-03-31 21:20                     ` Jonathan Cameron
     [not found]                       ` <c21be082-4ad8-46e2-a5f3-ad29b4239d94-2ueSQiBKiTY7tOexoI0I+QC/G2K4zDHf@public.gmane.org>
2014-04-01  5:42                         ` Zubair Lutfullah : [this message]
     [not found]                           ` <20140401054158.GA3261-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2014-04-04 13:41                             ` gmane-G/ASJRsgvFgvW+L+VdN226ESeJV5RFUqQQ4Iyu8u01E

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=20140401054158.GA3261@gmail.com \
    --to=zubair.lutfullah-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=balbi-l0cyMroinI0@public.gmane.org \
    --cc=bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org \
    --cc=dmitry.torokhov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=jic23-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
    --cc=lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=linux-iio-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-input-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=nyt-fuEpAR7jH0UNb0vsIHg089HuzzzSOjJt@public.gmane.org \
    --cc=robertcnelson-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=sameo-VuQAYsv1563Yd54FQh9/CA@public.gmane.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).