From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21784 invoked by alias); 27 May 2010 15:44:23 -0000 Received: (qmail 21770 invoked by uid 22791); 27 May 2010 15:44:20 -0000 X-SWARE-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.stmi.com (HELO mail.stmi.com) (70.169.254.5) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 27 May 2010 15:44:10 +0000 X-Ninja-PIM: Scanned by Ninja X-Ninja-AttachmentFiltering: (no action) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: AT91 ADC support Date: Thu, 27 May 2010 15:44:00 -0000 Message-ID: In-Reply-To: <4BFE860D.3060702@dallaway.org.uk> References: <4BFE76A4.1010702@dallaway.org.uk> <4BFE860D.3060702@dallaway.org.uk> From: "Christophe Coutand" To: "John Dallaway" Cc: "Sergei Gavrikov" , X-IsSubscribed: yes Mailing-List: contact ecos-patches-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-patches-owner@ecos.sourceware.org X-SW-Source: 2010-05/txt/msg00047.txt.bz2 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]=20 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. >=20 > 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