This is the mail archive of the mailing list for the eCos project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: AT91SAM7S platform, io_plf.h

Now I understand the SAM7X thing.

I noticed that there are the ADC and other defines are already in
var_io.h, so I don't have to type them.

It seems that the ADC is generic to AT91SAM devices (I checked SAM7S,
SAM7A3, SAM7L and SAM9260), they differ only in supported values for
trigger sources, channel number, etc.  I think I will write a driver
that can be used with the Generic ADC driver layer.

On Wed, Sep 17, 2008 at 7:26 PM, Andrew Lunn wrote:
> On Wed, Sep 17, 2008 at 06:11:56PM +0200, Gabor Torok wrote:
>> I was wondering, why there are defines related to AT91SAM7X
>> peripherals in this file belonging to the AT91SAM7S platform. Any
>> idea?
>> I would like to expand the list of the defines (add reset controller,
>> ADC and maybe others) and if the AT91SAM7X aren't needed here, I can
>> remove them.
> The AT91SAM7X is a AT91SAM7S plus an ethernet controller. The easiest
> way to support the 7X was to extend the 7S. So these defines are
> needed.
> The reset control is already defined. It is in the var_io.h because
> all AT91's have the same reset controller.
> When adding the ADC defines you first need to determine what level
> they go. Is the ADC controller specific to AT91SAM7 or is it generic
> to all/many of the AT91 devices? It does look like many different
> AT91SAM devices have ADC controllers. I took a quick look at the
> AT91SAM9XE128 and it seems to have the same ADC controller. Maybe also
> the AT91SAM7L devices use the same controller?
> So to me it looks like the register definition belong in var_io.h.
>   Andrew

Before posting, please read the FAQ:
and search the list archive:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]