public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: "Christophe Coutand" <ccoutand@stmi.com>
To: "John Dallaway" <john@dallaway.org.uk>
Cc: "Sergei Gavrikov" <sergei.gavrikov@gmail.com>,
		<ecos-patches@ecos.sourceware.org>
Subject: RE: AT91 ADC support
Date: Thu, 27 May 2010 15:44:00 -0000	[thread overview]
Message-ID: <D6050C555CC56940A7AF32652283027602EAC8BB@mail2.STMIRV01.COM> (raw)
In-Reply-To: <4BFE860D.3060702@dallaway.org.uk>

Hi John,

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.

One additional weakness of the driver is that it is made for up to 8
channels. It is defined nowhere what the targeted CPU can actually
handle, this is left to the user when configuring eCos. I believe this
is pretty fine since the user must anyway know which signal he wants to
sample but you might disagree on that one.

Regards,
Christophe


-----Original Message-----
From: John Dallaway [mailto:john@dallaway.org.uk] 
Sent: 27. mai 2010 16:48
To: Christophe Coutand
Cc: Sergei Gavrikov; ecos-patches@ecos.sourceware.org
Subject: Re: AT91 ADC support

Hi Christophe

Christophe Coutand wrote:

> I originally made it for AT91SAM7S and AT91SAM7X but at the last
minute
> I saw that Atmel was using the same ADC for AT91M55800A, AT91SAM9X
etc..
> so I renamed it to AT91. I thought this would be more future proof.

It's definitely a good idea to keep the package name more generic.

> It remains true that I have not compiled / tested it for anything else
> than AT91SAM7S / AT91SAM7X.
> 
> I can specify which AT91 supports it and update the var_io.h when
> definition are missing.

If it's easy to get the package building for the AT91M55800A targets
(eb55, phycore) then that would be preferable. If not, we can add the
package to the AT91SAM7 targets only (at91sam7sek, at91sam7xek,
sam7ex256) for now.

John Dallaway
eCos maintainer

  reply	other threads:[~2010-05-27 15:44 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 [this message]
2010-05-27 16:08           ` John Dallaway
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=D6050C555CC56940A7AF32652283027602EAC8BB@mail2.STMIRV01.COM \
    --to=ccoutand@stmi.com \
    --cc=ecos-patches@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    --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).