| Age | Commit message (Collapse) | Author |
|---|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
hes-tracking-s3c64xx-dma-support-1235439162-1235439227
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-s3c64xx-dma-support-1235439162-1235439227 / 3d6a1b21cf5fbdb6250d781b0a4900a7a0768aa1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-s3c64xx-dma-support-1235439162
stable-tracking-hist top was MERGE-via-mokopatches-tracking-s3c64xx-dma-support-1235439162 / 893e864e65adffc9eb085ed4f8b552a31dcec840 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-s3c64xx-dma-support
mokopatches-tracking-hist top was s3c64xx-dma-support / 2515f9a1d53d19b1e61d639875aedcbe7929666e ... parent commitmessage:
From: Ben Dooks <ben@simtec.co.uk>
S3C64XX: DMA support
Add support for the DMA blocks in the S3C64XX series
of CPUS, which are based on the ARM PL080 PrimeCell
system.
Unfortunately, these DMA controllers diverge from the
PL080 design by adding another DMA controller register
and configuration for OneNAND.
Signed-off-by: Ben Dooks <ben@simtec.co.uk>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
It's always a good idea to first define the data structures you use. ;-)
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
For GTA02 we can remove GTA02_HDQ (not used anywhere) and
S3C2410_CLOCK (already selected by CPU_S3C2442).
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
This reverts commit fe8b7ff1a79648146501f37d467fcb2f2bea0164.
I undo the reordering of the options here, as it hides what
really happend.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
For GTA02 we can remove GTA02_HDQ (not used anywhere) and
S3C2410_CLOCK (already selected by CPU_S3C2442). Additionally I reordered
the options a bit.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
If the PCF50633 ADC is disabled, but the charger is enabled we can't determine
the charger type using the pulldown. The safest thing we can do is to fallback
to 100mA that should be supplied according to the USB specs.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
If the vibrator is disabled we don't need to register a platform device.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
We select the PCF50633 core part, which depends on I2C, in our Kconfig. However,
make oldconfig does not automatically resolve this "depends on I2C" dependency.
We should select I2C for GTA02 as it's needed anyway.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
The GSM interface of all MACH_NEO1973s require the Samsung serial console,
so we should automatically select it.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
Move the battery section within the HDQ_GPIO_BITBANG ifdef because it uses
functions only available if HDQ bitbanging is enabled.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
If we disable CONFIG_CHARGER_PCF50633 the build fails with a bunch of errors.
This patch defines placeholders for the functions that require the charger. All
users of the function pointers care about the case when they are NULL, so this
won't break anything. Furthermore a small restructuring of the mach file was
necessary to not sprinkle ifdefs all over.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
Remove the old config option and use the correct new one instead.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
We have this in the S3C2442 machine section now.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
This patch cleans some cruft from neo1973-pm-gsm.c and makes
some changes to the power code for gsm.
First, on probe it enforces GSM is OFF.
Second, when GSM is OFF, it changes the RTS and TXD pins on
UART 0 to be inputs, instead of driving into a dead subsystem
and costing us ~70mA @ 5V constant dissipation (these 3.3V pins
were found at 1.5V due to that).
Third it asserts the GPIO peripheral function when ON, to keep
the same flow for the new interrupt generation workaround code.
Since several people worked on this area before, and maybe the
assertion of GSM OFF is different (it's OFF from bootloader though)
or maybe something else gets broken, I send the patch for comment
before applying it.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Added support for HDQ to GTA03.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
Since the pwm code in mach-2410 can be reused for 6410, move it to plat-s3c.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
The code for creating FIQ handlers in C is moved to
arch/arm/kerne/fiq.c
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
This implements a proper scheme of controlling powering on of the Calypso
GSM modem which should be activated with a "push-button" connected to
MODEM_ON line.
Also a workaround for firmware bug of moko10 and earlier implemented to
force calypso to pull IRQ line down after powering on.
The "reset" sysfs node is left for compatibility with userspace (without it
gsm0710muxd breaks) but it does nothing (NC on hardware level on GTA02
anyway).
I tested flashing the GSM firmware (on GTA02) with this patch (using only
fluid and power_on node) and can confirm that it's working as reliably as
with accessing gpio directly per instructions.
The credit goes to Joerg Reisenweber for discussions and clarifications on
how this should be done properly.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Pardon me if I am too verbose but this is my first opportunity to send a patch.
I was wishing to try andy-tracking kernels on GTA01 long ago but It
was FOSDEM and recent threads on the lists asking for GTA01 that made
me do it.
When I participated on the thread
http://n2.nabble.com/empiezo-a-amargarme-con-los-kernels-necesito-consejo-td2347206.html
in the Spanish mailing list asking what kernel to use with which
distribution, I responded that only FSO based supported 2.6.28 and
upwards. I could not resist to brag that I tested 2.6.29 on GTA01 but
only with kexec ( it is possible that my wording was more ambiguous on
the thread).
Nelson Asked if I had problems booting it with u-boot. I tried and was
successful but this time I played a Little with the interface and vala
term and noticed that the on screen keyboard was changing the key
pressed.
Using http://svn.openmoko.org/developers/tick/touchtest/touch_test.py
shown that most of the Up and sometimes the previous Move to where
landing on ([290..310],575).
Revising the code shown that the some of the filters and the option to
disable them were missing on mach-gta01.c.
I have tested the kernel with the patch applied with the filters
disabled and also with them enabled. When the filters are active I
still receive some misplaced up events but much less (the raster
terminal keyboard is usable).
Signed-off-by:Jose Luis Perez Diez <perezdiez@gmail.com>
|
|
This strips out the v1 and v2 GTA02 revision specific defines
(we do not support these internal non-shipped revisions) and
fixes a bug in the glamo reset resource found from that.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
This break gta02.h out of s3c2410 jail and brings it into the
more logical mach-s3c2442 dir.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
On Mon, Feb 16, 2009 at 05:55:47PM +0800, Andy Green wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Balaji -
>
> I am working on the sound driver on GTA03 at the moment, I just noticed
> this when I pulled out the USB cable
>
> [ 6905.100000] pcf50633 0-0073: usb curlim to 0 mA
> [ 6905.100000] Division by zero in kernel.
> [ 6905.100000] [<c002d5b0>] (dump_stack+0x0/0x14) from [<c002d5dc>]
> (__div0+0x18/0x20)
> [ 6905.110000] [<c002d5c4>] (__div0+0x0/0x20) from [<c0143f9c>]
> (Ldiv0+0x8/0x10)
> [ 6905.120000] [<c01ec7a0>] (pcf50633_mbc_usb_curlim_set+0x0/0x12c) from
> [<c01ec914>] (pcf50633_mbc_irq_handler+0x48/0xf4)
> [ 6905.130000] [<c01ec8cc>] (pcf50633_mbc_irq_handler+0x0/0xf4) from
> [<c019e288>] (pcf50633_irq_call_handler+0x28/0x2c)
> [ 6905.140000] r5:00000004 r4:00000000
> [ 6905.150000] [<c019e260>] (pcf50633_irq_call_handler+0x0/0x2c) from
> [<c019eab8>] (pcf50633_irq_worker+0x2f0/0x33c)
> [ 6905.160000] [<c019e7c8>] (pcf50633_irq_worker+0x0/0x33c) from
> [<c00548d8>] (run_workqueue+0xb0/0x138)
> [ 6905.180000] r7:c7826000 r6:c7ba8d50 r5:c7807200 r4:c7ba8d54
> [ 6905.190000] [<c0054828>] (run_workqueue+0x0/0x138) from [<c00554e8>]
> (worker_thread+0xec/0x100)
> [ 6905.200000] r8:00000000 r7:00000000 r6:c7807200 r5:c7826000 r4:c7827fb0
> [ 6905.220000] [<c00553fc>] (worker_thread+0x0/0x100) from [<c00588f0>]
> (kthread+0x5c/0x94)
> [ 6905.230000] r6:c00553fc r5:c7807200 r4:c7826000
> [ 6905.240000] [<c0058894>] (kthread+0x0/0x94) from [<c0046e54>]
> (do_exit+0x0/0x24c)
> [ 6905.250000] r6:00000000 r5:00000000 r4:00000000
>
> It's funny because what I see as the only divide in there is
>
> mbcc5 = (ma << 8) / mbc->pcf->pdata->chg_ref_current_ma;
> pcf50633_reg_write(mbc->pcf, PCF50633_REG_MBCC5, mbcc5);
Oops, chg_ref_current_ma is not defined for mach-om-gta03.c. Sorry :(
here's a patch.
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Temporarily force the CODEC power on to allow testing
of the WM8753 without having to update the drive for
the regulator framework.
Signed-off-by: Ben Dooks <ben@simtec.co.uk>
|
|
s3c_gpio_cfgpin and s3c_gpio_setpull to allow modules
to use them (such as ASoC drivers)
Signed-off-by: Ben Dooks <ben@simtec.co.uk>
|
|
Apparetly setting the number of VTs to 8 gets rid of the
android flickering issue, this patch does it for GTA01/2/3
configs.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Sascha's last changes didn't take care about case where blocker stuff
is disabled.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
|
|
|
|
The overrun bit has used only if the rx interrupt error is enabled.
Signed-off-by: Michael Trimarchi <michael@panicking.kicks-ass.org>
|
|
Signed-off-by: Matt Hsu <matt_hsu@openmoko.org>
|
|
Move the regulator handling stuff away from s3cmci.c to mach-gta01.c.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
The DMA used for S3C2440 is also used for S3C2442, so we also need the defines.
This patch is rebased on the latest andy-tracking branch.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
The dependency on ARCH_S3C2440 forces us to select at least one S3C2440 machine to get the makefile system to select the required options for our
S3C2442 GTA02. By removing this option I can build fine with only the GTA02 machine selected.
Signed-off-by: Sven Rebhan <odinshorse@googlemail.com>
|
|
Please ignore the previous patch. Here's the right one. I'll now write
100 times "I shall git-pull before making changes." Sorry.
- Werner
---------------------------------- cut here -----------------------------------
> I already tested and measured the signal of the "/MODEM_RST","/MODEM_ON"
[...]
> + s3c_gpio_setpull(GTA03_GPIO_MODEN_ON, S3C_GPIO_PULL_NONE);
~~~~~~~~
Here's a patch that changes GTA03_GPIO_MODEN_ON to GTA03_GPIO_MODEM_ON.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
hes-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414-1233879505
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414-1233879505 / 1c405b6ccee468298e7ccbfd9a3a3f4d123207b0 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414
stable-tracking-hist top was MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011-1233879414 / 71be0a45396066b1f8f27f8f4f87937247a129e1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011
mokopatches-tracking-hist top was MERGE-via-master-MERGE-via-master-hist-1232625318-1233879011 / 1be1b01373f572a02c6f1f99863c8c11ed2f9f5b ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-master-MERGE-via-master-hist-1232625318
master top was MERGE-via-master-hist-1232625318 / dd4b117123ae66451695810017eb72fbdfc05df5 ... parent commitmessage:
From: merge <null@invalid>
MERGE-master-patchset-edits
|
|
Remove the spew from GTA02 POWER_SUPPLY debugging messages,
it's just the HDQ stuff filling up dmesg every 30s or so.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: DKAY_CHEN <dkay_chen@openmoko.com>
|
|
Unlike SMDK we use 48MHz xtal on GTA03, don't copy
platform phy clock init from SMDK then
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
The naming of our defconfigs is currently inconsistent: three of them
end in -defconfig and use - also as an internal separator. One sends
in _defconfig but uses - as internal separator, and one ends in
_defconfig without needing an internal separator so far.
All the other defconfigs end in _defconfig. 21 use _ also as
internal separator and 5 use -.
So most of our names differ from the style everyone else is following
and there's also inconsistency among our names.
The git patch below renames them to the dominant all _ scheme.
There's always some latent undesirability for such cleanup patches
that may break some habits or scripts. So if there are strong
sentiments against doing this now, I won't push the issue. But in
general, the sooner one gets those little things done, the better.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Received: from mail.openmoko.org ([unix socket])
by mail.openmoko.org (Cyrus v2.1.18-IPv6-Debian-2.1.18-5.1) with LMTP; Fri, 30 Jan 2009 23:00:03 +0000
X-Sieve: CMU Sieve 2.2
Return-path: <openmoko-kernel-bounces@lists.openmoko.org>
Received: from sita.openmoko.org ([88.198.124.203])
by mail.openmoko.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
(Exim 4.63)
(envelope-from <openmoko-kernel-bounces@lists.openmoko.org>)
id 1LT2LD-0001st-Fo
for andy@imap.openmoko.org; Fri, 30 Jan 2009 23:00:03 +0000
Received: from localhost ([127.0.0.1] helo=sita.openmoko.org)
by sita.openmoko.org with esmtp (Exim 4.63)
(envelope-from <openmoko-kernel-bounces@lists.openmoko.org>)
id 1LT2Kb-0001Xw-JH; Fri, 30 Jan 2009 23:59:25 +0100
Received: from mail.openmoko.org ([88.198.124.205])
by sita.openmoko.org with esmtp (Exim 4.63)
(envelope-from <werner@openmoko.org>) id 1LT2KV-0001Xn-Lv
for openmoko-kernel@lists.openmoko.org; Fri, 30 Jan 2009 23:59:22 +0100
Received: from 175-205-16-190.fibertel.com.ar ([190.16.205.175] helo=ws)
by mail.openmoko.org with esmtpsa (TLS-1.0:DHE_RSA_AES_128_CBC_SHA1:16)
(Exim 4.63) (envelope-from <werner@openmoko.org>) id 1LT2KS-0001Xk-0U
for openmoko-kernel@lists.openmoko.org; Fri, 30 Jan 2009 22:59:19 +0000
Received: by ws (sSMTP sendmail emulation); Fri, 30 Jan 2009 22:02:47 -0200
Date: Fri, 30 Jan 2009 22:02:47 -0200
From: Werner Almesberger <werner@openmoko.org>
To: openmoko-kernel@lists.openmoko.org
Message-ID: <20090131000247.GF4526@almesberger.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on sita.openmoko.org
X-Spam-Level:
X-Spam-Status: No, score=-2.6 required=5.0 tests=AWL, BAYES_00, UPPERCASE_50_75
autolearn=no version=3.2.3
Subject: [PATCH] back out Android wakelocks breaking suspend
X-BeenThere: openmoko-kernel@lists.openmoko.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion regarding the OpenMoko Linux Kernel and boot loader
<openmoko-kernel.lists.openmoko.org>
List-Unsubscribe: <http://lists.openmoko.org/mailman/listinfo/openmoko-kernel>,
<mailto:openmoko-kernel-request@lists.openmoko.org?subject=unsubscribe>
List-Archive: <http://lists.openmoko.org/pipermail/openmoko-kernel>
List-Post: <mailto:openmoko-kernel@lists.openmoko.org>
List-Help: <mailto:openmoko-kernel-request@lists.openmoko.org?subject=help>
List-Subscribe: <http://lists.openmoko.org/mailman/listinfo/openmoko-kernel>,
<mailto:openmoko-kernel-request@lists.openmoko.org?subject=subscribe>
Sender: openmoko-kernel-bounces@lists.openmoko.org
Errors-To: openmoko-kernel-bounces@lists.openmoko.org
In current andy-tracking, a resume gets almost immediately followed
by another suspend, so we can never really leave suspend. This is
somehow caused by the Android wakelocks.
I think the most expedite way to deal with this is to back them out
of our configurations until they've been properly debugged, which
is what this patch does.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
GTA02 config suitable for bootloader menu application
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
