From: John Dallaway <john@dallaway.org.uk>
To: Christophe Coutand <ccoutand@stmi.com>
Cc: Sergei Gavrikov <sergei.gavrikov@gmail.com>,
ecos-patches@ecos.sourceware.org
Subject: Re: AT91 ADC support
Date: Thu, 27 May 2010 16:08:00 -0000 [thread overview]
Message-ID: <4BFE98EF.1030406@dallaway.org.uk> (raw)
In-Reply-To: <D6050C555CC56940A7AF32652283027602EAC8BB@mail2.STMIRV01.COM>
Hi Christophe
Christophe Coutand wrote:
> It's pretty easy to add the required definition for the AT91M55800A
> targets. The only thing I see now is that this device contains 2 ADCs
> which I have not considered before. I guess there are several ways out
> of this:
>
> 1- Update the actual AT91 ADC driver to make full use of the AT91M55800A
> targets. I guess should be done by loading a second ADC instance (one
> for each ADC. I have not been through all the thinking here...).
>
> 2- or limit the AT91 driver to use only ADC0 of the AT91M55800A target
> for the time being.
>
> 3- or exclude AT91M55800A targets for the time being.
>
> IMO #1 is best but I cannot give any time frame for completing it.
In that case, I would suggest option #2 for now. Someone else (who has
an AT91M55800A on their desk) may be interested in adding support for
the second ADC.
John Dallaway
eCos maintainer
next prev parent reply other threads:[~2010-05-27 16:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-22 9:40 Christophe Coutand
2010-05-27 13:42 ` John Dallaway
2010-05-27 13:52 ` Sergei Gavrikov
2010-05-27 14:16 ` Christophe Coutand
2010-05-27 14:47 ` John Dallaway
2010-05-27 15:44 ` Christophe Coutand
2010-05-27 16:08 ` John Dallaway [this message]
2010-05-27 16:37 ` Kurt Siedenburg
2010-05-27 16:37 ` Sergei Gavrikov
2010-05-27 19:49 ` Christophe Coutand
2010-05-27 21:44 ` Sergei Gavrikov
2010-05-29 10:24 ` Sergei Gavrikov
2010-05-29 13:10 ` John Dallaway
2010-05-30 10:34 ` Sergei Gavrikov
2010-05-30 12:40 ` Christophe Coutand
2010-05-30 13:46 ` Sergei Gavrikov
2011-02-22 11:33 ` John Dallaway
2010-05-27 21:37 ` Christophe Coutand
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=4BFE98EF.1030406@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ccoutand@stmi.com \
--cc=ecos-patches@ecos.sourceware.org \
--cc=sergei.gavrikov@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 read-only IMAP folder(s) and NNTP newsgroup(s).