- 12 Sep, 2008 9 commits
-
-
Viktor Rosendahl authored
This "changed" variable is kind of deprecated. We used to have a spinlock [which was later deemed unecessary] around the first if clause in the *_watermark_state() functions; the variable was needed in order to move the operation in the second if clause out of the lock section. Signed-off-by: Viktor Rosendahl <viktor.rosendahl@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Viktor Rosendahl authored
The purpose of this patch is to get rid of the lame percentage calculations in lowmem.c. Currently, the limits (measured in pages) are calculated from percentages every time somebody from userspace requests some memory. With this patch, the limits are in pages and furthermore, they are specified as minimum amount of "free pages", instead of as maximum amount of "used pages". "Free" means free pages or such pages that can easily be freed by the VM system. This patch changes the names of the lowmem sysctl limits in /proc/sys/vm: lowmem_deny_watermark => lowmem_deny_watermark_pages lowmem_notify_low => lowmem_notify_low_pages lowmem_notify_high => lowmem_notify_high_pages The following read only value disappears: lowmem_used_pages The following read only value is introduced: lowmem_free_pages The old value can be calculated from userspace with the following pseudocode: if lowmem_free_pages < lowmem_allowed_pages lowmem_used_pages = lowmem_allowed_pages - lowmem_free_pages else lowmem_used_pages = 0; Note that the value of lowmem_free_pages is only accurate when the system is rather low on memory (otherwise it's a bit too pessimistic), this was true also for the lowmem_used_pages metric. Signed-off-by: Viktor Rosendahl <viktor.rosendahl@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Viktor Rosendahl authored
As far as I can understand, using proc_dointvec_minmax() instead of proc_dointvec only makes sense if you supply the min and/or max values in the extra1 and extra2 fields of the struct. Signed-off-by: Viktor Rosendahl <viktor.rosendahl@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Henrik Saari authored
Security: Kernel OOM-killer and allocation denial use different rules Original patch created by Leonid Moiseichuk <leonid.moiseichuk@nokia.com> Fixes the issue with the oom killer and lowmem module being inconsistent; processes that are important enough to be protected from the oom killer should not be denied memory either. Signed-off-by: Henrik Saari <henrik.saari@nokia.com> Signed-off-by: Viktor Rosendahl <viktor.rosendahl@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
David Brownell authored
Make the twl4030 RTC initialization follow the driver model better. The platform device is created (if needed) as part of twl4030 setup instead of as a board-specific thing, and fits properly into the driver model tree. The only minor glitch here is on boards using platform_data to pass MSECURE initialization hooks to the RTC driver. The right solution probably just removes that platform_data, and might even make Linux follow the principle of "least privilege" (at the hardware level!) instead of always holding this signal high. Pending better handling of MSECURE, this patch just does what the RTC init does, but earlier: MSECURE is always high, so the RTC time and calendar registers can be updated (and presumably a bunch of non-RTC privileged operations will be allowed too). Yet to be done: set up the IRQ resource; make the rtc driver use that IRQ resource; and properly issue wakeup alarms. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
David Brownell authored
Remove more bogus arch_initcall() logic in mach-omap2/board-xyx.c files. They broke a multi-OMAP build I did, at *RUN TIME* not build time, since it tried to do the i2c init for every board linked in the kernel. Remember, init_machine() entries run at arch_initcall() time; that's where any board-specific init logic should normally go. Any initcalls in the mach-*/*c files should normally be guarded by tests to make sure they only run on the relevant hardware (board, cpu). Better yet, get rid of the initcalls; init_machine() can *explicitly* call the right version of that code, and pass in board-specific config data; and there are hooks that can handle cpu-specific stuff too. A quick glance suggests most of the remaining initcall logic in the mach-omap2 directory is similarly broken... this patch gets rid of one frequently-cloned idiom, it should help. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Peter 'p2' De Schrijver authored
Also add missing u8 data as noted by Felipe Balbi. Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
Clean-up MMC device init: - Initialize devices in mach-omap1/devices.c and mach-omap2/devices.c instead of plat-omap/devices.c - Remove old struct omap_mmc_config, use struct omap_mmc_platform_data instead Note that this removes the second omap-hsmmc controller init for overo. This needs to be fixed properly by changing hsmmc_init() to accept board specific struct omap_mmc_platform_data. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
This is to sync with Russell's commit 7736c09c. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 11 Sep, 2008 8 commits
-
-
Kalle Jokiniemi authored
Smartreflex modules have to be disabled when device enters WFI. Previously only suspend idle path had these calls. By moving the disable/enable calls to omap_sram_idle, all idle paths will be covered. Signed-off-by: Kalle Jokiniemi <ext-kalle.jokiniemi@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
A NAVEEN authored
When git kernel tree is used on a OMAP3EVM board file for touch screen testing, it shows lot of jitter. With this patch the jitter can be reduced. Signed-off-by: Naveen Atmakuri <anaveen@mistralsolutions.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Sergio Aguirre authored
ARM: OMAP: OMAP34XXCAM: Camera Base Address. Adding OMAP 3 Camera registers base address, and Platform Device. Signed-off-by: Sergio Aguirre <saaguirre@ti.com> Signed-off-by: Sameer Venkatraman <sameerv@ti.com> Signed-off-by: Mohit Jalori <mjalori@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
ext Peter 'p2' De Schrijver authored
This patch loads the triton2 (twl4030) with scripts that will cut off VDD1 and VDD2 voltages when SYS_OFF_MODE signal is set. Signed-off-by: Peter 'p2' De Schrijver <peter.de-schrijver@nokia.com> Signed-off-by: Kalle Jokiniemi <ext-kalle.jokiniemi@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Jarkko Lavinen authored
Add sysfs cover_switch with the status of cover. Signed-off-by: Francisco Alecrim <francisco.alecrim@indt.org.br> Signed-off-by: Jarkko Lavinen <jarkko.lavinen@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Francisco Alecrim authored
Add slot_name entry to sysfs. Signed-off-by: Francisco Alecrim <francisco.alecrim@indt.org.br> Acked-by: Anderson Lizardo <anderson.lizardo@indt.org.br> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Jarkko Lavinen authored
Re-organizing some goto at hsmmc probe. Signed-off-by: Francisco Alecrim <francisco.alecrim@indt.org.br> Signed-off-by: Jarkko Lavinen <jarkko.lavinen@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Francisco Alecrim authored
Readable output for IRQ status register Signed-off-by: Francisco Alecrim <francisco.alecrim@indt.org.br> Acked-by: Anderson Lizardo <anderson.lizardo@indt.org.br> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
- 10 Sep, 2008 12 commits
-
-
Högander Jouni authored
Do not try to call board specific suspend / resume functions if there is no such. Signed-off-by: Jouni Högander <jouni.hogander@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Madhusudhan Chikkature authored
ARM: OMAP3: Enable 4-bit support for HSMMC. This patch provides the fix to enable 4-bit support for HSMMC. Signed-off-by: Madhusudhan Chikkature<madhu.cr@ti.com> Signed-off-by: purushotam<purushotam@ti.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
David Brownell authored
Minor cleanups to omap 2430/34xx/35x musb_hdrc init: - num_eps is 16; here, each one is bidirectional - use DMA_32BIT_MASK to prevent confusion/errors - initialize root port power to reflect 100 mA limit This still hard-wires some board-specific data, since there are no hooks through which different boards can provide the right data to the init code. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Acked-by: Felipe Balbi <felipe.balbi@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Paul Walmsley authored
csi2_96m_fck no longer should attempt to init its clockdomain pointer; the clock framework now does this by default. Applies on top of the "Update powerdomains and clockdomains" series sent earlier. Verified on 3430SDP ES2. Signed-off-by: Paul Walmsley <paul@pwsan.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Koen Kooi authored
This seems to be the right naming and allows using vanilla gcc. See also: http://sourceware.org/ml/binutils/2006-12/msg00149.htmlSigned-off-by: Koen Kooi <k.kooi@student.utwente.nl> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
Now we have Catalin's cache patch applied, which should eventually hit mainline at some point. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Catalin Marinas authored
Show the cache type of ARMv7 CPUs Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
-
Jason Marini authored
The i2c driver contains a while loop that has no timeout. If i2c is in a funky state and OMAP_I2C_CON_STT remains asserted, the kernel hangs. Insert the standard i2c timeout into the loop. Signed-off-by: Jason P Marini <jason.marini@gmail.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
arun c authored
The gfx_plane doesn't support scaling. Signed-off-by: Arun C <arunedarath@mistralsolutions.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
stanley.miao authored
Prune off a empty line. Fix omapfb's problem on OMAP3430sdp. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Arun KS authored
Signed-off-by: Arun KS <arunks@mistralsolutions.com> Acked-by: Jarkko Nikula <jarkko.nikula@nokia.com> Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
Merge branches 'master' and 'linus' Conflicts: arch/arm/mach-omap1/mcbsp.c arch/arm/mach-omap2/mcbsp.c arch/arm/plat-omap/include/mach/mcbsp.h arch/arm/plat-omap/mcbsp.c
-
- 09 Sep, 2008 11 commits
-
-
Linus Torvalds authored
-
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6Linus Torvalds authored
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6: ipv6: Fix OOPS in ip6_dst_lookup_tail(). ipsec: Restore larval states and socket policies in dump [Bluetooth] Reject L2CAP connections on an insecure ACL link [Bluetooth] Enforce correct authentication requirements [Bluetooth] Fix reference counting during ACL config stage
-
git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6Linus Torvalds authored
* git://git.kernel.org/pub/scm/linux/kernel/git/davem/sparc-2.6: sparc64: Disable timer interrupts in fixup_irqs().
-
Neil Horman authored
This fixes kernel bugzilla 11469: "TUN with 1024 neighbours: ip6_dst_lookup_tail NULL crash" dst->neighbour is not necessarily hooked up at this point in the processing path, so blindly dereferencing it is the wrong thing to do. This NULL check exists in other similar paths and this case was just an oversight. Also fix the completely wrong and confusing indentation here while we're at it. Based upon a patch by Evgeniy Polyakov. Signed-off-by: Neil Horman <nhorman@tuxdriver.com> Signed-off-by: David S. Miller <davem@davemloft.net>
-
Linus Torvalds authored
Merge branch 'timers-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip * 'timers-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip: clockevents: remove WARN_ON which was used to gather information
-
Tony Lindgren authored
This is to be in sync with Russell's commit 7c7095aa. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
This is to be in sync with Russell's commit 0062f104. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Tony Lindgren authored
This is to be in sync with Russell's patch 690b5a13. Signed-off-by: Tony Lindgren <tony@atomide.com>
-
Thomas Gleixner authored
The issue of the endless reprogramming loop due to a too small min_delta_ns was fixed with the previous updates of the clock events code, but we had no information about the spread of this problem. I added a WARN_ON to get automated information via kerneloops.org and to get some direct reports, which allowed me to analyse the affected machines. The WARN_ON has served its purpose and would be annoying for a release kernel. Remove it and just keep the information about the increase of the min_delta_ns value. Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
-
Linus Torvalds authored
Merge branch 'x86-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip * 'x86-fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip: x86: fix memmap=exactmap boot argument x86: disable static NOPLs on 32 bits xen: fix 2.6.27-rc5 xen balloon driver warnings
-
Prarit Bhargava authored
When using kdump modifying the e820 map is yielding strange results. For example starting with BIOS-provided physical RAM map: BIOS-e820: 0000000000000100 - 0000000000093400 (usable) BIOS-e820: 0000000000093400 - 00000000000a0000 (reserved) BIOS-e820: 0000000000100000 - 000000003fee0000 (usable) BIOS-e820: 000000003fee0000 - 000000003fef3000 (ACPI data) BIOS-e820: 000000003fef3000 - 000000003ff80000 (ACPI NVS) BIOS-e820: 000000003ff80000 - 0000000040000000 (reserved) BIOS-e820: 00000000e0000000 - 00000000f0000000 (reserved) BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved) BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) BIOS-e820: 00000000ff000000 - 0000000100000000 (reserved) and booting with args memmap=exactmap memmap=640K@0K memmap=5228K@16384K memmap=125188K@22252K memmap=76K#1047424K memmap=564K#1047500K resulted in: user-defined physical RAM map: user: 0000000000000000 - 0000000000093400 (usable) user: 0000000000093400 - 00000000000a0000 (reserved) user: 0000000000100000 - 000000003fee0000 (usable) user: 000000003fee0000 - 000000003fef3000 (ACPI data) user: 000000003fef3000 - 000000003ff80000 (ACPI NVS) user: 000000003ff80000 - 0000000040000000 (reserved) user: 00000000e0000000 - 00000000f0000000 (reserved) user: 00000000fec00000 - 00000000fec10000 (reserved) user: 00000000fee00000 - 00000000fee01000 (reserved) user: 00000000ff000000 - 0000000100000000 (reserved) But should have resulted in: user-defined physical RAM map: user: 0000000000000000 - 00000000000a0000 (usable) user: 0000000001000000 - 000000000151b000 (usable) user: 00000000015bb000 - 0000000008ffc000 (usable) user: 000000003fee0000 - 000000003ff80000 (ACPI data) This is happening because of an improper usage of strcmp() in the e820 parsing code. The strcmp() always returns !0 and never resets the value for e820.nr_map and returns an incorrect user-defined map. This patch fixes the problem. Signed-off-by: Prarit Bhargava <prarit@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
-