linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Naidu Tellapati <Naidu.Tellapati@imgtec.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: pushing SOC specific Trigger provider driver to upstream kernel
Date: Sun, 31 Aug 2014 16:50:46 +0100	[thread overview]
Message-ID: <54034456.5050004@kernel.org> (raw)
In-Reply-To: <27E62D98F903554192E3C13AFCC91C3C2B778F57@hbmail01.hb.imgtec.org>

On 31/08/14 15:50, Naidu Tellapati wrote:
> Hi Mr. Jonathan and all,
> 
For now just cc'd Lars-Peter on the basis Analog have a very similar timer based trigger (still in staging)
and I suspect he has some thoughts on this.

Lars, want to comment?
> My name is Naidu Tellapati from India. I work for Imagination Technologies, India. Thanks in advance for your help in this regard.
> 
> After going through some of the emails in the Linux-IIO email archive, we have taken the following approach to implement our Linux IIO based ADC driver.
> 
> We are planning to have two drivers as part of our implementation.
> 
> 1. Timer's Periodic Interrupt Trigger Provider IIO driver (This driver uses our SOC specific Timer's periodic interrupt)
> 
> 2. The generic IIO ADC driver (This ADC driver uses the periodic Timer Interrupt Trigger provided by the above driver)
> 
> The plan is to push both the drivers upstream to kernel.org. Now please suggest us, do you consider SOC specific Trigger Provider driver as well for pushing upstream to kernel.org ?
> 
> 
> Thanks in advance,
> 
> Regards,
> Naidu.
> 
> 
> 

  reply	other threads:[~2014-08-31 15:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31 14:50 pushing SOC specific Trigger provider driver to upstream kernel Naidu Tellapati
2014-08-31 15:50 ` Jonathan Cameron [this message]
2014-09-02 15:57   ` Lars-Peter Clausen

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=54034456.5050004@kernel.org \
    --to=jic23@kernel.org \
    --cc=Naidu.Tellapati@imgtec.com \
    --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).