| Age | Commit message (Collapse) | Author |
|---|
|
I had a patch by Vasily Khoruzhick <anarsoul@gmail.com>
in the linux-arm-kernel as a guide for some of the changes.
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
Without this patch we cannot make the s3c2410/s3c2440 touchscreen
driver work.
Is this delay device-dependant?
Is there a better way to do this?
We specify the delay value (S3C2410_ADCDLY).
Signed-off-by: Vasily Khoruzhick <anarsoul@gmail.com>
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
|
|
This patch allow us to efficiently modify the number of
remaining conversions from the client side. This us useful
when we do not know in advance how many conversions we will
need or when we need to cancel pending conversions.
This change is simple enough to be compatible with existing
code that can just define the new pointer in the callback
and ignore it.
Sample usage:
http://tinyurl.com/s3c2410-ts-c (function stylus_adc_action).
Signed-off-by: Nelson Castillo <arhuaco@freaks-unidos.net>
Signed-off-by: Ben Dooks <ben-linux@fluff.org>
|
|
After suspending with GPS powered on power_on sysfs node reports 0 and GPS
is actually unpowered but "echo 1 > power_on" has no effect. This patch
fixes it.
Reported and analised by Timo Juhani Lindfors <timo.lindfors@iki.fi>,
ticket #2293.
Signed-off-by: Paul Fertser <fercerpav@gmail.com>
|
|
Machines that do not route the USB vbus signal to a GPIO can use this
mechanism as an alternate way for the udc driver to detect the usb
connect/disconnect state, which is useful (for example) to enable the
link up/down state to be determined for the g_ether gadget.
Signed-off-by: Mike Westerhof <mwester@dls.net>
|
|
Signed-off-by: Tim Niemeyer <tim.niemeyer@mastersword.de>
|
|
added bus link from neo1973-pm-gps.0 to gta01-pm-gps.0
added pwron attr wich is the same as power_on
also one typo fixed (3V instead of 3V3 in gps_power_3v_set)
[ Werner: Documentation/CodingStyle line 83, don't ignore the error if
sysfs_create_group fails. ]
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Change RTS and TXD pins on UART 0 to be inputs only on GTA02.
On GTA01 the UART 0 maybe used otherwise.
[ Werner: removed unexplained addition of DEBUG, Documentation/CodingStyle
lines 105, 224, and 448. ]
Signed-off-by: Tim Niemeyer <reddog@mastersword.de>
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
~ 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>
|
|
|
|
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>
|
|
Clean out more switch() on version that has no point given the
actual features that (don't) differ on supported GTA02 versions.
We take care about forcing GPS regulator off on neo1973-pm-gps probe,
but we don't take care about killing the UART GPIO so they don't
drive into the powered-down subsystem. We took care of doing that when
we turned off the thing already, but we cannot just call the OFF code
from the probe due to problems with regulator state init.
Reported-by: Rask Ingemann Lambersten <rask@sygehus.dk>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
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 14:13:43 +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 1LSu7r-000566-Sm
for andy@imap.openmoko.org; Fri, 30 Jan 2009 14:13:43 +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 1LSu7M-0004nA-JB; Fri, 30 Jan 2009 15:13:12 +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 1LSu7H-0004n3-4S
for openmoko-kernel@lists.openmoko.org; Fri, 30 Jan 2009 15:13:10 +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 1LSu7F-0004mk-Pb
for openmoko-kernel@lists.openmoko.org; Fri, 30 Jan 2009 14:13:07 +0000
Received: by ws (sSMTP sendmail emulation); Fri, 30 Jan 2009 13:16:38 -0200
Date: Fri, 30 Jan 2009 13:16:38 -0200
From: Werner Almesberger <werner@openmoko.org>
To: openmoko-kernel@lists.openmoko.org
Message-ID: <20090130151638.GA10711@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 autolearn=ham
version=3.2.3
Subject: [PATCH] fix #if vs. #ifdef cpp warning in neo1973_pm_gps.c
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
#if is a poor substitute for #ifdef :-)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
|
|
clean-29-rc2-merge-freakage.patch
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=445395c9fcfb78ea62ab5a69b84c2c12efe01cff
pcf50606_rebase_changes,patch
This patch brings into andy-tracking all changes related to pcf50606 from old
balaji-tracking.
|
|
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=57b3df284f5a79346f2b25003f76c6702cf84c25
pcf50633_rebase_changes.patch
This patch brings all changes from balaji-tracking originally intended for
upstream into andy-tracking.
|
|
On Wed, Jan 21, 2009 at 08:51:41PM +0000, Andy Green wrote:
> Today I got Ben Dooks to uplevel his tree to 29-rc1, I am rebasing it
> tonight, but ssh access to git.openmoko.org git:// is broken right now.
>
Oh, I forgot! Then you might encounter the pcf50633 driver from upstream
which has lots of differences from what we have on andy-tracking. So,
here I'm attaching a patch that applies to current andy-tracking which
is how the pcf50633/mach-gta02.c should look like after rebase. You can
probaly look into it in case of confusion..
Or you can apply it before rebase ? Probably you can..
Hope it helps,
Balaji
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
hes-tracking-fix-stray-endmenu-patch-1232632040-1232632141
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040-1232632141 / fdf777a63bcb59e0dfd78bfe2c6242e01f6d4eb9 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040
stable-tracking-hist top was MERGE-via-mokopatches-tracking-fix-stray-endmenu-patch-1232632040 / 90463bfd2d5a3c8b52f6e6d71024a00e052b0ced ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-fix-stray-endmenu-patch
mokopatches-tracking-hist top was fix-stray-endmenu-patch / 3630e0be570de8057e7f8d2fe501ed353cdf34e6 ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
fix-stray-endmenu.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Allow the GPS module to be powered during suspend so it can keep the fix.
This has to be enabled by writing 1 to .../neo1973-pm-gps.0/keep_on_in_suspend
Signed-off-by: Vladimir Koutny <vlado@ksp.sk>
|
|
Fix re-enabling of GPS on resume
The call to gps_pwron_set(0) during suspend would clear power_was_on
flag so the on/off status was always lost. Additionally when enabling/
disabling the regulator check its actual state, not power_was_on flag
(they don't match on resume).
Signed-off-by: Vladimir Koutny <vlado@ksp.sk>
|
|
This patch cleans up the GTA02 WLAN power control platform device:
- remove misleading /sys/devices/platform/gta02-pm-wlan.0/power_on
Users really wishing to play with reset can just gpio j12=0
- rename gta02_wlan_power to gta02_wlan_reset, because that's what it
truly is
- remove handling of GTA02_CHIP_PWD because
- it's not used, say our schematics
- even if it is, it's sampled long before we could affect it
- move SDIO-specific conversion from "power switch" to "reset
button" logic from gta02_wlan_reset to gta02_s3c_mmc_set_power
- removed mutex protection because we now only have a single user
A note in passing: we can probably do away with gta02_pm_wlan
completely once upstream rfkill adds better support for type-based
control.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
Here's a bunch of changes to neo1973_pm_gps.c. The thing I set out to
change was just the initial power state, but there's so much wrong in
there, I couldn't resist slaying some evil on the way:
- update the copyright year
- show slightly more confidence in operator precedence
- simplify #ifdef rat's nest a little
- rename "pwron" sysfs file to "power_on", to conform to all the rest
- wrap lines longer than 80 columns
- use PTR_ERR, not cast
- reduce redundancy and increase readability in code patching
gta01_gps_sysfs_entries
- on GTA02 and if booted by u-boot, GPS is powered on. Power it off,
like on GTA01 or with Qi.
It's still nasty, but slightly less painful to look at now. Tested on
GTA02 and tested that it still compiles for GTA01.
The name change from "pwron" to "power_on" may be controversial. If
this causes undue misery for distribution makers, please holler.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
-the-ar6000-1232104308
pending-tracking-hist top was MERGE-via-stable-tracking-rfkill-support-for-the-ar6000-1232104308 / 09faeb511e9e6872c79b4d1ea2f3b5fefc16f3a1 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-rfkill-support-for-the-ar6000-
stable-tracking-hist top was rfkill-support-for-the-ar6000- / e82f8ffa04ebcb05506c8e22268371c3c3b03173 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
rfkill support for the AR6000 driver
This patch adds rfkill support to the AR6000 driver. The driver does
not directly implement an rfkill device but uses the help of a special
platform device, such that the latter can retain rfkill state when the
AR6k driver is removed (e.g., because of suspend).
If an attempt is made to bring the driver up (module load, bind, or
resume) while rfkill is blocking, only the driver's data structures
are initialized, but function activation and most of the rest of the
setup is deferred until the rfkill block is removed.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
hes-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516-1229082771
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516-1229082771 / f410ecd0cc4642ae8b0f69c15fe349ea5639f5e2 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516
stable-tracking-hist top was MERGE-via-mokopatches-tracking-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488-1229082516 / 18f9a76ecc30ba8eee5de0627de3e7eb049775c3 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488
mokopatches-tracking-hist top was MERGE-via-master-MERGE-via-master-hist-1229078937-1229079488 / 7eb66508f95eeebbd7ad3487c5183b76524d4765 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-master-MERGE-via-master-hist-1229078937
master top was MERGE-via-master-hist-1229078937 / ff0b5902f29135a782a3bfb68e3429b86669aea4 ... parent commitmessage:
From: merge <null@invalid>
MERGE-master-patchset-edits
|
|
pending-tracking-hist top was MERGE-via-pending-tracking-hist-1228898320 / 75e06011b6a2ab443295941791f0e71913d837d5 ... parent commitmessage:
From: merge <null@invalid>
MERGE-pending-tracking-patchset-edits
|
|
pending-tracking-hist top was fix-s3c_irq_demux_extint8-to-h / e3a894b0f1fae0caa2224a5d1b3c409fcac9f5cc ... parent commitmessage:
From: Balaji Rao <balajirrao@openmoko.org>
Fix s3c_irq_demux_extint8 to handle masked but pending IRQs
Hi,
It was observed that even after the move to level irq on pcf50633, the
problem of 'the phone doesn't resume if POWER is pressed during
transition to standby' remains.
The original problem was due to a lost edge.
The present problem - When POWER is pressed during the transition,
handle_level_irq runs which looks at the IRQ_DISABLED flag set by
pcf50633_suspend and masks the irq on chip. Now when the cpu wakes up
(level keeps hitting us), s3c_irq_demux_extint8 runs, which tries to
handle all pending irqs. But before it does so, it applies the mask
and hence not all pending irqs were acked and hence, our pmu's irq
(level) caused an irq flood..
This patch clears those interrupts which are masked, but pending. Fixes
the problem for me. Mildly tested.
Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
|
|
pending-tracking-hist top was s3c24xx-needs-gpio_track / da546f30820208681442d98d29aadd2e6a909a09 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
S3C24xx needs GPIO_TRACK
s3c_gpiolib_getchip for 24xx assumes that, as far as addressing is
concerned, all ports have 32 pins. However, there are two flaws in
this logic:
1) gpiolib only assigns pin number for real pins (with the
exception of gaps added with CONFIG_S3C_GPIO_SPACE), and
2) not all ports have the same number of pins.
This patch makes 24xx use the more generic platform s3c_gpiolib_getchip,
like we do on 6410.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
S3C24xx: make GPIOs end at H10
At least on 2410 and 2442, GPIOs don't end at G10 but at H10 or
even J12.
Port J is treated as a special case throughout much of the S3C
code, so I'm not sure what the plan is for it now. However, it
seems safe to include port H.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
S3C24xx: GPIO G has 16 pins
At least on 2410 and 2442, GPIO port G has 16 pins.
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
toolchain-on-1228470136
pending-tracking-hist top was MERGE-via-stable-tracking-build-fix-path-to-toolchain-on-1228470136 / 21b67ab8e79998b0a534263282dab1dda0f11b00 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-build-fix-path-to-toolchain-on
stable-tracking-hist top was build-fix-path-to-toolchain-on / ca14ba894df9b28822066c578dde48d7dbe931de ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
build-fix-path-to-toolchain-one-at-last.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
There's a bug in calculation of IRQ_EINT_BIT introduced on the test
branch for pm changes for s3c by Ben Dooks fixed in this patch.
There's also a bit of a mystery about how wake gets to wake EINT
set of interrupts, I added a couple of lines that make it work for
EINT4+ but not sure what's meant to be there for EINT0-3.
Still, this gets GTA02 resume working again.
cc: Ben Dooks <ben-linux@fluff.org>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
pending-tracking-hist top was patch-andy-tracking-merge-brea / 2010fb7565e8239f893d3631c3b1ccc7766f26b9 ... parent commitmessage:
From: Werner Almesberger <werner@openmoko.org>
PATCH-andy-tracking-merge-breakage-pending-tracking-fix.patch
Fix merge breakage in pending-tracking. With this patch,
0b519f14e15365213924505e2e3019c1ff159aa9 builds for GTA02 and it
even boots ! ;-)
Signed-off-by: Werner Almesberger <werner@openmoko.org>
|
|
hes-tracking-MERGE-via-master-1228302402-1228302766-1228303138
pending-tracking-hist top was MERGE-via-stable-tracking-MERGE-via-mokopatches-tracking-MERGE-via-master-1228302402-1228302766-1228303138 / 27d86638fe294ef1d1a8f527564ec37bb20e7ef2 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-stable-tracking-hist-MERGE-via-mokopatches-tracking-MERGE-via-master-1228302402-1228302766
stable-tracking-hist top was MERGE-via-mokopatches-tracking-MERGE-via-master-1228302402-1228302766 / 66e84c4be853030f1cea816a124cf76a741ecc08 ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-mokopatches-tracking-hist-MERGE-via-master-1228302402
mokopatches-tracking-hist top was MERGE-via-master-1228302402 / de9177f7bd127e9b6fa6213018c7c731b8ca0d0c ... parent commitmessage:
From: merge <null@invalid>
MERGE-via-master-
master top was / 3838a80929f91d35c6d987e518bf9ea397f3e13c ... parent commitmessage:
From: Andy Green <andy@openmoko.com>
fix-wm8753-DBG.patch
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Sean noticed that the fixes yesterday for pm_bt only set the drvdata
on GTA02 path, it will trash GTA01 operation of it.
Reported-by: Sean McNeil <sean@mcneil.com>
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Hum seems the rfkill stuff was broken somewhere along the line,
some of it thinks the rfkill pointer is in the pdev private data
and some gets confused about the bt_data pointer being in dev
private data... this patch cleans it out so the rfkill pointer
is held in the bt_data struct, which is created for gta01 or 02
now.
Before these changes it will blow up on resume due to dereferencing
the wrong pointer to the wrong thing.
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
|
Signed-off-by: Andy Green <andy@openmoko.com>
|
