Age | Commit message (Collapse) | Author |
|
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>
|
|
Subject: [PATCH] fix-alsa-bt-dai-registration-missing
|
|
Subject: [PATCH] Typo in I2C device registration
Signed-off-by: Tim Niemeyer <reddog@redlap.wired.rednet.mastersword.de>
|
|
These are the Samsung S3C camera interface register definitions directly
from the 2.6.21 BSP. The only changes to the original code are the removal
of trailing whitespace and the change of location.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
A few dirty hacks to make the camera driver work:
- because V4L no longer guarantees that minor numbers provided by the
client are actually used, the preview/codec selection mechanism falls
apart. We work around this by defaulting to preview when we don't
know better.
- power up the camera in platform code, not cleanly via power control
device.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Enable V4L and camera driver in 3D7K default configuration.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch adds the camera interface driver and the corresponding
configuration option to the 3D7K machine.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Add Samsung S3C camera subsystem to kernel configuration and build process.
Original code is from Samsung's BSP.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This patch makes the Samsung S5K4BA driver work in 2.6.29 and also solves
a few minor issues, such as trailing whitespace.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This is the original Samsung S5K4BA camera driver code from the 2.6.21
BSP. The changes that are needed to make this work in 2.6.29 are in
the next patch.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
These are te I2C IDs for all the Samsung S5K series cameras. This code
is directly from Samsung's BSP.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Add Samsung S3C camera interface driver.
Original code is from Samsung's BSP and was written for 2.6.21.
Only tested on S3C6410.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Update the camera interface driver from 2.6.21 to 2.6.29 and fix some
trivial issues. There are still a few ugly spots, marked with "@@@".
Only tested on S3C6410.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
This is the original Samsung S3C camera driver code from the 2.6.21 BSP.
The changes that are needed to make this work in 2.6.29 are in the next
patch.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Add camera interface clock to S3C6410.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Add doubled HCLK to S3C64xx.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Note: this patch is already on the way upstream but is currently missing
in the Openmoko kernel.
Some of the rate selection logic in s3c64xx_setrate_clksrc uses what
appears to be parent clock selection logic. This patch corrects it.
I also added a check for overly large dividers to prevent them
from changing unrelated clocks.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This one is specially for Candy Chou :-)
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
|
|
The code is borrowed from gta02.
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Reported-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andy Green <andy@openmoko.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>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=522c644d34461fcd65a94cce1fcac9dc0d6cd828
ohci_s3c2410: Implement PM resume functionality
It was observed that that s3c2410_hc's root hub was not autoresumed when the
system was suspended with the root hub itself autosuspended.
As an effect of this, it was observed that the bluetooth module wouldn't get
detected at the hc's roothub ports when powered up after resume. And when
'lsusb' was executed, the roothub got out of autosuspend by force with a
'roothub lost power, resetting' message.
This patch brings the hcd roothub out of resume at global resume thereby
avoiding the issue.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Control for the power for the LM4853 on the GTA02 had been made directly
visible to user space, needlessly burning power when no output was being
produced and causing pops and clicks to be worsened due to a lack of
integration with the power sequencing done by DAPM.
Bring the amplifier power under DAPM control, saving power and reducing
the levels of pops and clicks caused.
The existing control is left in place for the benefit of scenario files
but now has no effect.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
It's a little verbose...
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Factors out a lot of code.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Openmoko had similar controls with "DAPM " prefixed to them - add that
back to maintain compatibility with existing ALSA state files.
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>
|
|
More code cleanup.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Stops anyone wondering what they're needed for.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
It's patchy and we have git history.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
On some systems it is desirable for control for DAPM pins to be provided
to user space. This is the case with things like GSM modems which are
controlled primarily from user space, for example. Provide a helper which
exposes the state of a DAPM pin to user space for use in cases like this.
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=f4fd6631973dbc67a5f4708014e81ca6e610ca05
pcf50633_charger_detection_fix.patch
Fix PCF50633 charger detection code.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
> |> on current andy-tracking / OM_3D7K build.
> |>
> |> I didn't see this before, it seems to related to SPI bitbang, did we
> |> break something?
Here is the patch. I've not tested it, but it's most likely the fix, as
I had seen a similar thing in spi_s3c24xx_gpio.
|
|
Hi,
git 1.6.0 in debian unstable does not put "git-branch" to a directory
that is in PATH anymore
> git-core (1:1.6.0.2-1) experimental; urgency=low
>
> * new upstream point release.
> * debian/git-core.NEWS.Debian: new; mention that most of the programs
> now are installed outside the default $PATH; the "git-xyzzy" form
> in scripts and on the command line is no longer supported in 1.6.0.
so the build script should probably be modified:
|