aboutsummaryrefslogtreecommitdiff
path: root/drivers/mfd/glamo
AgeCommit message (Collapse)Author
2009-03-26Fix MMC buffer locationsThomas White
This fixes the MMC buffer locations in glamo-mci.c, which were broken by the reorganisation of Glamo's memory. Signed-off-by: Thomas White <taw@bitwiz.org.uk>
2009-03-26Pass core Glamo device to DRM moduleThomas White
This adds a missing statement to let glamo-drm.c know the core Glamo handle, so it can manipulate registers such as the 2D and 3D clocks. Signed-off-by: Thomas White <taw@bitwiz.org.uk>
2009-03-26Tidy up Glamo memory map declarationsThomas White
This just cosmetically tidies up the declarations in glamo-core.h. We have to be very clear about what lives where in the memory. Signed-off-by: Thomas White <taw@bitwiz.org.uk>
2009-03-26Remove Glamo's 2D, 3D, JPEG and MPEG devicesThomas White
This patch removes the platform devices corresponding to Glamo's 2D, 3D, JPEG and MPEG engines. These will later be handled via DRM. Signed-off-by: Thomas White <taw@bitwiz.org.uk>
2009-03-26Initial DRM driver for GlamoJorge Zapata
2009-03-26Import part of Thomas White DRM tree:Jorge Zapata
Handle new memory layout. The "not-needed" memory should not be taken by the framebuffer driver. Use that for the DRM driver. Add the cmdq platform device Set aside 4k for hardware cursor, reject cursors that don't fit.
2009-03-26Kconfig/Makefile DRM platform supportJorge Zapata
2009-03-26Glamo fb: needs cfb_{fillrect,copyarea,imageblit} to linkRask Ingemann Lambertsen
The kernel would fail to link because cfb_fillrect, cfb_copyarea and cfb_imageblit weren't build. This patch fixes it. Signed-off-by: Rask Ingemann Lambertsen <rask@sygehus.dk>
2009-03-02Subject: Get rid of board_info information in glamo and s3c24xx_gpio ↵Balaji Rao
spigpio_info. X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=740c6704e830829d8539a6cc34346ff1980cd9ee Get rid of board_info information in glamo and s3c24xx_gpio spigpio_info. The board info does not belong there and has been removed. In spi_s3c24xx_gpio, board_info has been removed in mainline. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-02-20fix-glamo-mci-move-stop-out-of-isr.patchAndy Green
This patch moves the bulk transfer action outside of interrupt context, along with the STOP transmission action for multiblock transfers. It's prompted by https://docs.openmoko.org/trac/ticket/2180 But it can impact throughput to SD card, so it's for testing currently. Signed-off-by: Andy Green <andy@openmoko.com>
2009-02-20fix pan displaySean McNeil
It looks like I made a mistake in the original pan implementation that is now getting exercised. The following fixes pan again. Cheers, Sean
2009-02-01debug-add-more-glamo-mem-speed-options.patchAndy Green
People on bug https://docs.openmoko.org/trac/ticket/2217 experiencing problems with default emmory settings on Glamo reported that changing reg 0x200 <- 0xef0 as in 2.6.24 made the problem not reproducible any more. However this changes three bitfields, two are to do with waitstates before sampling read and write cycles off the bus, and the last is to do with which PLL provides the clock to the memory interface unit logic. The old settings has all three of these very conservative, 3 waitstates and using the 50MHz PLL instead of the 90MHz one; the new default setting has all of these at their fastest of 0 wait states and the 90MHz PLL. This patch adds some more granular tests to the same glamo3362.slow_memory= parameter to see if we can find some middle ground. For example the issue may be the waitstates and not the PLL source, in which case even users with the bad Glamo behaviour can have the advantage of the faster PLL / bus bandwidth. 0 90MHz PLL, no wait states (default) 1 50MHz PLL, 3 wait states 2 50MHz PLL, 2 wait states 3 50MHz PLL, 1 wait state 4 50MHz PLL, no wait states 5 90MHz PLL, 3 wait states 6 90MHz PLL, 2 wait states 7 90MHz PLL, 1 wait state Signed-off-by: Andy Green <andy@openmoko.com>
2009-01-29Subject: glamo_fix_improper_xrandr_geometry_setting.patchBalaji Rao
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=3b09161ffa5f29870d1f2cab1442f79ff2017b69 glamo_fix_improper_xrandr_geometry_setting.patch Switching to xrandr -o 3 from xrandr -o 1 caused the screen to look crazy because of the way lcd geometry is set in glamo. This patch fixes it. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-01-28Subject: fix_glamo_xrandr_bug.patchBalaji Rao
X-Git-Url: http://git.openmoko.org/?p=kernel.git;a=commitdiff_plain;h=40fe0a30c75937a476ea50220814ca8b1fd81b45 fix_glamo_xrandr_bug.patch This patch reintroduces the 2-cycle delay used when accessing glamo-fb registers. This seems to be required even when the corresponding registers in HOST_BUS are off. Signed-off-by: Balaji Rao <balajirrao@openmoko.org>
2009-01-28debug-glamo-allow-slower-memory-bus.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2009-01-27fix-glamo-core-from-balaji-tree.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2009-01-22MERGE-via-pending-tracking-hist-MERGE-via-stable-tracking-MERGE-via-mokopatc ↵merge
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>
2009-01-19Make glamo-fb.c build without CONFIG_PMWerner Almesberger
Fix suspend/resume dummy in glamo-fb.c Signed-off-by: Werner Almesberger <werner@openmoko.org>
2009-01-15avoid using irq_desc in glamo-mci.cWerner Almesberger
When building the MMC subsystem as modules, drivers/mfd/glamo/glamo-mci.ko cannot access irq_desc, because it isn't exported by kernel/irq/handle.c All the functions that indirectly access irq_desc are inlined, so they cannot be used to avoid having to resolve irq_desc. Fortunately, we can solve the problem locally: we don't really need to access irq_desc anyway. This patch splits glamo_mci_irq into a small wrapper that implements the IRQ handler interface and the main code that doesn't need to know about the semantics of the latter. Then we simply call the main code with the information we already have. Signed-off-by: Werner Almesberger <werner@openmoko.org> Tested-by: Rafael Ignacio Zurita <rizurita@yahoo.com>
2009-01-04fix-glamo-mci-ambiguous-timeout.patchAndy Green
Sometimes we see failures with cards where the status is eg, 0x310. This corresponds to a "no data" timeout and an assertion that the data is present. This patch makes the data present status have priority over the timeout status. Signed-off-by: Andy Green <andy@openmoko.com>
2008-12-04MERGE-via-pending-tracking-hist-MERGE-via-stable-tracking-workaround-glamo-m ↵merge
mc-insanity-1228425445 pending-tracking-hist top was MERGE-via-stable-tracking-workaround-glamo-mmc-insanity-1228425445 / 8c97326a7ad33d8690a4b433abc14918e5900e58 ... parent commitmessage: From: merge <null@invalid> MERGE-via-stable-tracking-hist-workaround-glamo-mmc-insanity- stable-tracking-hist top was workaround-glamo-mmc-insanity- / 7a55cd6f948a33c4452dd99da39e15efe832f2e2 ... parent commitmessage: From: sprite_tm <unknown@invalid> workaround-glamo-mmc-insanity-timeout-warning-only.patch Modified version of one line patch from https://docs.openmoko.org/trac/ticket/2078 by sprite_tm Signed-off-by: Andy Green <andy@openmoko.com>
2008-12-01fix-glamo-mci-no-wait-ack-deselect.patchAndy Green
Now the card is powered when we send the last command from the stack, SELECT CARD with arg 0, we learn that the card can't reply when deselected. So detect SELECT CARD and arg 0 and don't bother waiting for an ack that isn't coming. This chops three seconds off suspend :-) Signed-off-by: Andy Green <andy@openmoko.com>
2008-12-01fix-glamo-mmc-reduce-insanity-timeout.patchAndy Green
Nothing on the card can really take 3s.. reduce to 300ms Signed-off-by: Andy Green <andy@openmoko.com>
2008-12-01fix-err-strength-debug-msg.patchAndy Green
Now Qi is changed to default to loglevel 4 where it will show KERN_ERR on LCM, we need to reduce the debugging KERN_ERR traffic so as not to obscure the real things. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-20glamo_mci_use_regulator_api.patchBalaji Rao
Changes the glamo-mci driver to use the regulator API.
2008-11-19Make the console turn off the backlight when blanking the screen.Andy Green
Work in progress.
2008-11-19fix-glamo-gpio-resume.patchAndy Green
Glamo GPIO are not set correctly after resume / reset action. This patch forces them to correct state for GTA02. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19page-flip.patchSean McNeil
Signed-off-by: Sean McNeil <sean@mcneil.com>
2008-11-19From a54bd9e2376337320c36965830fd3167c4063356 Mon Sep 17 00:00:00 2001Chia-I Wu
Subject: [PATCH] glamofb: Initialize only visible part of the memory. It takes lots of time (0.5 seconds) to initialize the whole memory. As only the visible part matters, we could just initialize that part. Signed-off-by: Chia-I Wu <olv@openmoko.com>
2008-11-19meddle-wsod.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-suspend-remove-reg-dump-and-restore.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-resume-dont-restuff-regs-do-reinit-in-framebuffer-resume.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19tracking-glamo-suspend-even-more-meddling.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19cleanup-after-adding-andy-tracking-patchset.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-mci-ignore-command-properly.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-rebase-dust.patchAndy Green
Last rebase to stable-2.6.26 left some trash from rebasing the patches on top of this, clean it back out Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19debug-glamo-syslog-dumps.patchAndy Green
More effort to refine power code that does the suspend and resume actions Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19debug-resume-hang.patchAndy Green
Weeks of frantic effort to control Glamo, traced the issue to two outcomes: nWAIT is forced down and the device is hard locked, or we survive immediate Glamo resume and die again with nWAIT forced down when the framebuffer driver tries to flash the soft cursor. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19glamo-resume-meddling.patchAndy Green
Big chunk of trying to own Glamo resume and not really succeeding Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-remove-resume-dependencies-on-pmu-for-pmu-children.patchAndy Green
All that stuff should be enforced by device tree now, out with it Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-suspend-cant-use-pll-host-bus-clock-during-suspend.patchAndy Green
Hum well that's the idea, Glamo did not play ball Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-mci-no-need-for-suspend-fake-command.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-reparenting-panic-sd-boot.patchAndy Green
We panic on SD boot now we changed Glamo order, because it didn't succeed to bring up mmcblk0p1. But, if you do loglevel=8 then it works OK. So we are racing with something... Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-probe-fail-bail.patchAndy Green
Backout from failed probe was quite broken. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19debug-glamo-drop-lcm-reset-during-glamo-probe.patchAndy Green
We shouldn't have to reset it in glamo probe Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-migrate-irq-init-before-register-init.patchAndy Green
Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamo-irq-recursive-locking.patchAndy Green
Running heavily instrumented kernel, get report about glamo IRQ spinlock probem. [ 8.795000] ============================================= [ 8.795000] [ INFO: possible recursive locking detected ] [ 8.795000] 2.6.24 #782 [ 8.795000] --------------------------------------------- [ 8.795000] swapper/1 is trying to acquire lock: [ 8.795000] (&irq_desc_lock_class){++..}, at: [<c0077ae4>] handle_level_irq+0x24/0x120 [ 8.795000] [ 8.795000] but task is already holding lock: [ 8.795000] (&irq_desc_lock_class){++..}, at: [<c01be628>] glamo_irq_demux_handler+0x24/0x140 [ 8.795000] [ 8.795000] other info that might help us debug this: [ 8.795000] 1 lock held by swapper/1: [ 8.795000] #0: (&irq_desc_lock_class){++..}, at: [<c01be628>] glamo_irq_demux_handler+0x24/0x140 [ 8.795000] [ 8.795000] stack backtrace: [ 8.795000] [<c002ec28>] (dump_stack+0x0/0x14) from [<c006ad74>] (__lock_acquire+0x9a0/0xdec) [ 8.795000] [<c006a3d4>] (__lock_acquire+0x0/0xdec) from [<c006b264>] (lock_acquire+0xa4/0xc0) [ 8.795000] [<c006b1c0>] (lock_acquire+0x0/0xc0) from [<c02f7878>] (_spin_lock+0x44/0x78) [ 8.795000] [<c02f7834>] (_spin_lock+0x0/0x78) from [<c0077ae4>] (handle_level_irq+0x24/0x120) [ 8.795000] r6:c03e11c0 r5:0000005c r4:c03e11c0 [ 8.795000] [<c0077ac0>] (handle_level_irq+0x0/0x120) from [<c01be708>] (glamo_irq_demux_handler+0x104/0x140) [ 8.795000] r7:00000038 r6:c03e11c0 r5:00000008 r4:c03e0560 [ 8.795000] [<c01be604>] (glamo_irq_demux_handler+0x0/0x140) from [<c003c934>] (s3c_irq_demux_extint8+0x94/0xa4) [ 8.795000] r8:00000002 r7:00000003 r6:00000000 r5:c03df958 r4:00000000 [ 8.795000] [<c003c8a0>] (s3c_irq_demux_extint8+0x0/0xa4) from [<c0029048>] (__exception_text_start+0x48/0x64) [ 8.795000] r4:00000015 [ 8.795000] [<c0029000>] (__exception_text_start+0x0/0x64) from [<c0029a5c>] (__irq_svc+0x3c/0xb4) Patch removes desc->lock locking around glamo_irq_demux_handler... guess it is OK since we didn't clear interrupt source, can't recurse? Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamofb-defuse-yield-bomb-in-atomic-context.patchAndy Green
If we ever fall through to the yield when we turned off interrupts... it wouldn't be pretty. Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19change-glamo-mci-try-memcpy.patchAndy Green
Trial to see if (mainly 32-bit) memcpy is any better than u16 loop Signed-off-by: Andy Green <andy@openmoko.com>
2008-11-19fix-glamofb-remove-soft-delays.patchAndy Green
The delay versions of the access to registers were based on a misunderstanding of the Glamo docs: it can force nWAIT differently depending on the access type. Therefore we don't need to take special care about delays on CPU side. Signed-off-by: Andy Green <andy@openmoko.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-06-15 04:52:36 +0000