From: Andy Shevchenko <andy.shevchenko@gmail.com>
To: "Bogdan, Dragos" <Dragos.Bogdan@analog.com>
Cc: Rohit Sarkar <rohitsarkar5398@gmail.com>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Subject: Re: [GSOC] Choosing a component
Date: Thu, 26 Mar 2020 22:44:34 +0200 [thread overview]
Message-ID: <CAHp75VcxqoSiKiCfsq43_uwQHg6ptDWozTYkwcdX99pBiZT42Q@mail.gmail.com> (raw)
In-Reply-To: <DM5PR03MB3402EFA69C3644DA76FFB4C79CCF0@DM5PR03MB3402.namprd03.prod.outlook.com>
On Thu, Mar 26, 2020 at 7:14 PM Bogdan, Dragos <Dragos.Bogdan@analog.com> wrote:
>
> The IIO community can also suggest an Analog Devices component.
Last month on StackOverflow shows a lot of proposals :-)
Just go with `i2c` tag and see what people are trying to enable (some
sensors have been mentioned several times in different QnA). Also
getting rid of MRAA/UPM is a good idea (moving them to libiio /
libgpiod and moving sensor drivers to kernel).
On top of that there are (plenty I think) projects on GitHub regarding
drivers in user space which, in my opinion, should be rather in
kernel.
Just my two cents.
> 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.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-03-26 20:44 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 [this message]
2020-03-26 20:47 ` Rohit Sarkar
2020-03-28 9:55 ` Rohit Sarkar
2020-03-28 10:41 ` Andy Shevchenko
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=CAHp75VcxqoSiKiCfsq43_uwQHg6ptDWozTYkwcdX99pBiZT42Q@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).