All of lore.kernel.org
 help / color / mirror / Atom feed
From: Naidu Tellapati <Naidu.Tellapati@imgtec.com>
To: "linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"jic23@kernel.org" <jic23@kernel.org>
Subject: pushing SOC specific Trigger provider driver to upstream kernel
Date: Sun, 31 Aug 2014 14:50:17 +0000	[thread overview]
Message-ID: <27E62D98F903554192E3C13AFCC91C3C2B778F57@hbmail01.hb.imgtec.org> (raw)

Hi Mr. Jonathan and all,=0A=
=0A=
My name is Naidu Tellapati from India. I work for Imagination Technologies,=
 India. Thanks in advance for your help in this regard.=0A=
=0A=
After going through some of the emails in the Linux-IIO email archive, we h=
ave taken the following approach to implement our Linux IIO based ADC drive=
r.=0A=
=0A=
We are planning to have two drivers as part of our implementation.=0A=
=0A=
1. Timer's Periodic Interrupt Trigger Provider IIO driver (This driver uses=
 our SOC specific Timer's periodic interrupt)=0A=
=0A=
2. The generic IIO ADC driver (This ADC driver uses the periodic Timer Inte=
rrupt Trigger provided by the above driver)=0A=
=0A=
The plan is to push both the drivers upstream to kernel.org. Now please sug=
gest us, do you consider SOC specific Trigger Provider driver as well for p=
ushing upstream to kernel.org ?=0A=
=0A=
=0A=
Thanks in advance,=0A=
=0A=
Regards,=0A=
Naidu.=0A=
=0A=
=0A=
=0A=

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-31 14:50 Naidu Tellapati [this message]
2014-08-31 15:50 ` pushing SOC specific Trigger provider driver to upstream kernel Jonathan Cameron
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=27E62D98F903554192E3C13AFCC91C3C2B778F57@hbmail01.hb.imgtec.org \
    --to=naidu.tellapati@imgtec.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.