| Age | Commit message (Collapse) | Author |
|---|
|
Turns out, this makes Mesa work a lot better.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
The arguments changed between 2.6.32 and 2.6.34.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
(Not tested...)
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
glamo-core didn't ioremap() some areas, so don't try to read them.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
This simplifies the JBT6k74 driver, and adds hooks for the Glamo driver to cooperate
more closely with it.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
This adds modifications to the core of the Glamo driver to expose functionality
to support DRM and KMS.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
This adds the Glamo DRM and KMS driver, but note that modifications are needed
elsewhere to support it.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
This modifies the DRM core in a small number of places to allow platform
devices to be used for direct rendering, alongside PCI devices.
Signed-off-by: Thomas White <taw@bitwiz.org.uk>
|
|
|
|
|
|
Conflicts:
drivers/power/Kconfig
drivers/power/Makefile
|
|
|
|
|
|
|
|
'glamo-2.6.34', 'om-misc-2.6.34' and 'om-s3c-2.6.34' into om-gta02-2.6.34
|
|
|
|
config used in SHR-U, KMS enabled
|
|
config used for qtmoko-v20. It has all freerunner hardware built in - so that
you can boot and your phone hardware is working even without /lib/modules. I
have (hopefully) all drivers from 2.6.29 as modules (usb keyboards etc).
|
|
This adds support for platform_battery driver which allows to specify a set
of power supply properties and callbacks to acquire them. It is needed to
support dumb batteries where all the information about their status can
only be obtained by platform-specific actions such as specific ADC
measurements, some guessimation etc.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
|
|
|
|
This driver can be used for dumb batteries when all knowledge about
their state belongs to the platform that does necessary ADC readings,
conversions, guessimations etc.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
|
|
|
|
This is the only user of the pcf50633 gpio api. Since the custom interface is
going to be replaced with gpiolib all users need to be remove or replaced.
It is safe to be remove it in this case since it is used used to turn a gpio
off which is never going to be turned on.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
On the gta02 we often have a child parent relationship between different
devices. The child devices can only be probed after their parant has been.
Instead of adding a probe completed handler to each device we handle this in a
generic way with a bus notifier.
|
|
|
|
Early verions off uboot used for the gta02 flashed the nand with ecc information
incompatible to s3c2440 hardware ecc. Disable hardware error correction by
default, unless the bootloader explicitly enables it.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
|
|
|
|
|
|
Select usb host and nand device.
|
|
On hardware revision 5 and earlier the leds found on the gta02 are missing a
resistor and reading their gpio pin status will always return 0. So we have to
shadow the led states in software. This is done by "hijacking" the gpio accessor
functions for bank B.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
The gta02 has three leds which are connected though gpio pins and thus can get
supported by using the generic leds-gpio driver.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
The gta02 has two buttons which are connected to gpio pins and thus can get
supported by using the generic gpio-keys driver.
Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
|
|
|
|
|
|
This reduces the code clutter a bit and will ease an the migration to genirq.
|
|
Use a threaded irq instead of normal irq and a workqueue.
|
|
|
|
|
