From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: Rohit Sarkar <rohitsarkar5398@gmail.com>
Cc: "Bogdan, Dragos" <Dragos.Bogdan@analog.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [GSOC] Choosing a component
Date: Sat, 28 Mar 2020 12:41:50 +0200 [thread overview]
Message-ID: <CAHp75VeZMccYGEqH7Och+hQO8DsNGWce+RN-o3FL4diaB8c=bg@mail.gmail.com> (raw)
In-Reply-To: <5e7f1f28.1c69fb81.33271.73d7@mx.google.com>
On Sat, Mar 28, 2020 at 11:56 AM Rohit Sarkar <rohitsarkar5398@gmail.com> wrote:
> On Thu, Mar 26, 2020 at 05:13:24PM +0000, Bogdan, Dragos wrote:
> > The IIO community can also suggest an Analog Devices component.
> >
> > Rohit, anyway, since the student application period ends soon, you can just think of one component type (e.g., ADC, DAC, etc.), create your plan accordingly and submit your proposal.
> After doing a search through ADI's website, I chose the accelerometers
> ADXL35x series (ADXL355[1] and ADXL357[2]) as a component that I could
> write a driver for, having verified that there are no preexisting drivers
> for the same. Hope this is a decent choice.
Good choice, though one recommendation before you start.
Check carefully that these components really need a separate driver
(instead of extending existing one). In the kernel we have enough
examples of duplication of the drivers by various reasons.
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2020-03-28 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 15:47 [GSOC] Choosing a component Rohit Sarkar
2020-03-26 17:13 ` Bogdan, Dragos
2020-03-26 20:44 ` Andy Shevchenko
2020-03-26 20:47 ` Rohit Sarkar
2020-03-28 9:55 ` Rohit Sarkar
2020-03-28 10:41 ` Andy Shevchenko [this message]
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='CAHp75VeZMccYGEqH7Och+hQO8DsNGWce+RN-o3FL4diaB8c=bg@mail.gmail.com' \
--to=andy.shevchenko@gmail.com \
--cc=Dragos.Bogdan@analog.com \
--cc=linux-iio@vger.kernel.org \
--cc=rohitsarkar5398@gmail.com \
/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).