| Age | Commit message (Collapse) | Author |
|---|
|
Hello,
this patch adds "force-shutdown" feature for GTA02. When the power button is
held pressed for 8 seconds, the power is turned off. No need to remove the
battery anymore. Patch is against andy-tracking.
Signed-off-by: Ondrej Zary <linux@rainbow-software.org>
Signed-off-by: Nicolas Dufresne <nicolas.dufresne@gmail.com>
|
|
Add to_irq method to convert gpio to irq
for external interrupt group (GPN).
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
If no battery is connected, we periodically get a burst of HDQ error
messages (at least on 3D7K), interrupting whatever we're doing on
the console.
This patch reduces this to only one message per sequence of errors,
and one more message if communication with HDQ is successful later.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
The power mode of ROUT1 is always off which results
in the voice only comes from left channel (LOUT1).
This issues is fixed by adding dapm control for ROU1 channel.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
Reported-by: Candy Chou <candy_chou@openmoko.com>
|
|
This patch explicitly enabled to "camif" clock, to make the driver
work again with Qi commit a24b5fcf84d2cf633a3f660edd23fa4c2a3da231.
Note that this is not fully tested since the Qi change also broke
the LCM driver.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch adds the real "camif" clock (off HCLK.)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Identifiers related to the "camera" clock were mis-named as camif.
This patch renames them.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This dirty hack adds camera activation/deactivation on open/close.
This code will have to move to a machine/platform area later. The
general driver is the wrong place for it.
It also removes the unconditional activation and moves the domain
setting to the rest of the power control code. (Thanks, Andy !)
Note that opening the camera now always takes about 20 seconds
until the settings are downloaded, not just on the first open.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Filter chains should be completely opaque to the drivers that use it.
We fix this with this patch.
~ Make the "filter chain" a new object.
~ We can build with CONFIG_TOUCHSCREEN_FILTER=n with no problems in
a cleaner way.
~ Update s3c2410_ts.c to use the filter_chain object.
~ Cleanups.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
~ Make a few symbols constant.
~ Export symbols explicitly.
~ Move ts_filter.c to ts_filter_chain.c (this will make sense later).
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
This patch defines a ts_filter_configuration structure to
avoid using void* in the filter initialization, fixing another
upstream correction. This also makes the initialization more readable.
Tested in GTA02/rev6.
Other changes:
~ Comment filter configuration structures.
~ ts_filter.c:ts_filter_chain_create improved.
~ Small cleanups.
~ More TODOs/FIXMEs.
~ Updated GTA02 filter configuration.
~ Updated GTA01 filter configuration.
~ Updated mach-s3c2410/include/mach/ts.h for the new ts. configuration
structure.
~ Updated all the filters to use the new configuration structure.
~ Removed MAX_TS_FILTER_CHAIN constant that is no longer needed.
No more evil casts left it seems.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
This patch turns upstream feedback into API modifications and code
improvements. There will be more patches implementing upstream
corrections but this one is the that will make most of the invasive
changes and make the most important improvements to the API.
Tested in a GTA02/rev06.
The goals of this patch are:
* Replace recursive calls with iteration.
* General code improvements.
* Make ts_filter_mean.c a reference for the rest of the filters.
* Make the (almost)minimum number of changes to the other filters so
that they compile and work, patches for cleaning these up will
come next.
* Filters should do what they were doing before.
Some important changes:
* Move "struct ts_filter tsf" in the private structures to force
a crash (or break things) if we forget to remove an open-coded cast.
* ts_filter.c/ts_filter.h
~ API modifications.
* s3c2410_ts.c:
~ Use the new API.
~ Cleanups.
* ts_filter_mean.c
~ Replace with a simple mean.
~ Use as a reference for the new API.
~ Move private structure from the .h to the .c.
* ts_filter_group.c
~ Update to use the new API.
* ts_filter_median.c
~ Update to use the new API.
* ts_filter_linear.c
~ Remove functions that are no longer needed.
Note:
I might leave some TODOs and FIXMEs with this patch. Most of them
will be removed shortly.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This lets us turn off CONFIG_S3C_DEV_CAMIF and suppress it
turning on power (still seemed to issue clock though).
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
This patch does some light cleanup on the camera driver:
- removed unused return values or unused initializations
- remove backslashes at regular line ends (Python-style ?)
- removed redundant casts
- remove redundant parentheses
- wrapped long lines
- general whitespace cleanup
- fixed broken logic in s3c_camif_v4l2_g_input and s3c_camif_v4l2_g_output
- let mutex that really really wants to be a semaphore have its way
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
The PLL converts a 26.6 MHz input clock to 87.8 MHz, which is later
divided by two and becomes PCLK. (See comments below for details.)
All this looks like a textbook example for platform stuff, but let's
take it one step a time.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
s3c64xx_setrate_clksrc used the clock selection shift sclk->shift instead
of the divider shift sclk->divider_shift, causing clocks to be clobbered.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
s3c64xx_roundrate_clksrc got the rate vs. parent order wrong.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
[ Resending it. Seems that commit 9e723603e46500e2c9fbf09ac823de210bf05d31
used one of the empty mails I got with formail :-( ]
Add camera interface clock to S3C6410.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch does some light cleanup on the S5K4BA driver:
- change structure initializers from field: to .field = syntax
- exlicitly name fields in structure initializers
- added proper error handling to sensor_read
- use ARRAY_SIZE
- remove redundant parentheses and braces
- change // to /* ... */
- remove non-ASCII characters
- general whitespace cleanup
- removed an unused variable warning
(4xa_sensor.h is only partially cleaned up.)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch does some cleanup on the camera interface driver:
- remove backslashes at regular line ends (Python-style ?)
- removed unused return values or unused initializations
- combined duplicated or otherwise highly redundant code
- remove redundant parentheses
- wrapped long lines
- general whitespace cleanup
- s3c_camif_input_msdma_codec, s3c_camif_input_msdma_preview,
s3c_camif_set_target_format: fixed clearing of old register values
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch does some light cleanup on the camera driver:
- removed unused return values or unused initializations
- remove backslashes at regular line ends (Python-style ?)
- removed redundant casts
- remove redundant parentheses
- wrapped long lines
- general whitespace cleanup
- fixed broken logic in s3c_camif_v4l2_g_input and s3c_camif_v4l2_g_output
- let mutex that really really wants to be a semaphore have its way
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
The current version of CPU detection patch from Mark Brown and
Kyungmin Park takes a dump on system_rev. This patch changes it
to retain the low 16 of system_rev from the bootloader ATAG, and
adds access #defines and changes to use them.
No doubt they'll issue a better version of the CPU detection
patch and then this can be reverted.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Use the regulator framework to provide optional support for DVFS in
the S3C64XX cpufreq driver. When a software controllable regulator
is configured the driver will use it to lower the supply voltage when
running at a lower frequency, giving improved power saving.
When regulator support is disabled or no regulator can be obtained
for VDDARM the driver will fall back to scaling only the frequency.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
This patch provides initial support for CPU frequency scaling on the
Samsung S3C64XX series processors. Currently only S3C6410 processors
are supported, though addition of another data table with supported
clock rates should be sufficient to enable support for further CPUs.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Add support for reconfiguring the clock for the ARM core, enabling
CPUfreq support. Currently only the divider for ARMCLK may be changed,
ARMPLL is left static.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Stroe the CPU ID to system_rev and use it to detect the CPU architecture.
Even though s3c64xx has almost same IPs, some IPs such as OneNAND are different.
Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=d9235e3a8bdcef02865eed27c0d6012d253f11e7
om3d7k: Add support for s3c_ohci device.
Adds s3c_ohci support to om3d7k.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=b55b8e56a4a7e43b7243be48f77a326236a37c68
USB: Change s3c2410_ohci into s3c_ohci and change gta02 to use it
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Give the regulator supplies names corresponding to the names their
supplies are given in the schematic, making it easier to tie the
software up with the schematic.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
At least one of the speaker options should disable the speaker.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
http://lists.openmoko.org/pipermail/openmoko-kernel/2009-March/009387.html
)
Change accelerometers to use ABS events rather than REL events.
[Obviously if this patch is accepted we need to tell developers about
it. I have a number of other improvements to the accelerometers I
hope to deliver over the next couple of weeks. They will have minimal
or zero disruption to current code. ]
REL events should be used when there is no absolute reference, and
only changes are meaningful. The classic example is a "mouse" where
the absolute position of the device is not measurable and not
particularly meaning, but change in position from one time to the next
is interesting.
With REL events, a value of '0' is not reported, as 'not change' is
not interesting.
With REL events, the expectation is that successive values will be
eventually summed (possibly with acceleration and clipping
adjustments) to get a usable value.
ABS events should be used when there is an absolute references against
which things that be measured.
With ABS events, the 'current value' is meaningful and can be read
(EVIOCGABS).
With ABS events, the value '0' is very meaningful and is reported.
However if consecutive values are the same, the value is only reported
once.
ABS events can be used as-is or compared with previous events to get
some measure of change.
An obvious example is a touchscreen where each measure in
independently meaningful.
Acceleration is an absolute value as it is measuring against a frame
of reference. '0' acceleration is just as meaningful as any other
value, and finding the 'current' acceleration is each direction is a
potentially useful thing to do.
The Freerunner accelerometers currently report REL events. This is
wrong. So this patch changes them to report ABS events.
With this patch, the min/max/level/fuzz values are left at zero. It
might be useful to make use of these in a subsequent patch.
min/max/level can be used to calibrate the accelerometers if accuracy
is important.
fuzz could possibly be used in conjunction with the 'threshold' sysfs
value to get less frequent, lower-precision reports.
This may well break some applications that read accelerometer data.
This cannot be helped, but it is quite easy to write code that copes
with the incorrect EV_REL events as well as the more correct and
useful EV_ABS events.
Signed-off-by: NeilBrown <neilb@suse.de>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
The camera driver reduced all IO drivers from their reset defaults of
6 mA to only 2 mA, which caused severe signal distortion at higher
speeds. This patch sets them to 8 mA and also removes apparently
useless repetitions of the setting.
Note that the correct setting of the I2C pullups still needs to be
verified.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
for 3d7k.
By parsing kernel command, 3d7k can probe two different LCM driver accordingly.
The default attached LCM device is l1k002, if you wanna to use jbt6k74, you don't
need to re-compile the kernel. Just add one option om_3d7k_lcm=jbt6k74 in
boot/append-OM_3D7K in rootfs.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
- provide clean sysfs to control RGB channel directly.
They are looked like the following:
channel_mode
channel_pwm
channel_cur
- add platform data to export RGB channel accordingly.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
LED INT is connected to EXT group6_9, the handling of EXT group1~group9
is not yet implemented. Besides, we don't need this IRQ now.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
