From: Nishant Malpani <nish.malpani25@gmail.com>
To: linux-iio@vger.kernel.org
Cc: Dragos.Bogdan@analog.com
Subject: [RFC] IIO Driver for GSoC 2020
Date: Thu, 26 Mar 2020 23:04:06 +0530 [thread overview]
Message-ID: <147e6ea7-5022-e131-8cec-14fa22278703@gmail.com> (raw)
Hello IIO,
The project proposal for GSoC 2020 under The Linux Foundation [1] must
include a Analog Devices, Inc.'s component for which a novel driver is
to be implemented. My search for a prospective device has culminated to
consider ADXRS290 Gyroscope. About ADXRS290:
- Ultra-low Noise, Dual-Axis (Pitch and Roll) MEMS Gyroscope
- "Recommended for New Designs" phase
- SPI digital output
- Datasheet in [2]
- Product overview in [3]
The existence of any compatible drivers for the above component was
looked for in Analog Device, Inc.'s page that lists all drivers [4] and
their kernel tree [5] and the Linux Kernel Driver database (LKDDb). It
was found to be void and ergo my decision to choose the aforementioned
component.
Is there any other factor I should consider before choosing a component
to make a driver for? Do I go ahead with ADXRS290 gyroscope in my
proposal? If yes, are there any recommendations/suggestions you'd like
to provide for a beginner indulging in making a kernel driver for such a
component?
Thank you for your time.
With regards,
Nishant Malpani
[1] https://wiki.linuxfoundation.org/gsoc/2020-gsoc-iio-driver
[2]
https://www.analog.com/media/en/technical-documentation/data-sheets/ADXRS290.pdf
[3] https://www.analog.com/en/products/adxrs290.html#product-overview
[4] https://wiki.analog.com/resources/tools-software/linux-drivers-all
[5] https://github.com/analogdevicesinc/linux
next reply other threads:[~2020-03-26 17:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 17:34 Nishant Malpani [this message]
2020-03-26 18:47 ` [RFC] IIO Driver for GSoC 2020 Bogdan, Dragos
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=147e6ea7-5022-e131-8cec-14fa22278703@gmail.com \
--to=nish.malpani25@gmail.com \
--cc=Dragos.Bogdan@analog.com \
--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).