Datasheet

8
AVR32416
Figure 3-1 Frame buffer and LCD driver software overview
The main part is the frame buffer driver with the underlying LCD controller driver and
a frame buffer. These parts are necessary components in order to build up a
functioning system. Depending on the LCD an extra LCD driver may be needed to do
configuring or power up/down through interfaces like SPI or GPIO. A LCD driver can
be tied to the frame buffer driver by using a low level LCD abstraction layer. By doing
so some functions of the LCD driver can be controlled from the frame buffer driver
over the low level abstraction layer or directly by the low level abstraction layer.
Currently only one frame buffer event is handled by the low level abstraction layer
which will turn the LCD display on/off by using the LCD driver. The low level
abstraction layer provides also a direct interface to a user-space application which
offers more specific controls like contrast. More information about the low level
abstraction layer is available in chapter “LCD low level abstraction layer”.
3.4 Kernel configuration
To enable the needed drivers the kernel must be configured properly. This can be
done by running
make ARCH=avr32 menuconfig
in the source directory of the Linux kernel. If you are using Buildroot you can use
make linux26-menuconfig
in the Buildroot source directory to get into the Linux kernel configuration system.
All software should be compiled into the kernel and not as modules. Among other
advantages this is the only way to provide an early startup image on the screen. In
the kernel configuration enable the following for the frame buffer support:
Device Drivers ->
Graphics support ->
Support for frame buffer devices
And the following for the LCD controller driver:
Device Drivers ->
32105-AVR32-07/08